|
|
Sponsored Content
Operating Systems
Solaris
Ldom OS on SAN based zfs volume
Post 302335469 by fugitive on Sunday 19th of July 2009 12:58:58 PM
07-19-2009
|
|
10 More Discussions You Might Find Interesting
1. Linux
Dear Srs,
I have a Linux server (linux01) booting from SAN with a volume in a Nexsan SATAbeast storage array (san01). The disk/volume has four ext3 partitions, total size is near to 400GB, but only 20-30GB are in use.
I need to move this disk/volume to another Nexsan SATAbeast storage array... (0 Replies)
Discussion started by: Santi
0 Replies
2. Red Hat
Hi,
We have 200GB SAN volume mounted on Redhat EL 5. which is working fine. As my SAN supports dynamic resizing of volumes, i unmounted the volume and resized the SAN Volume to 300 GB successfully. Then i mounted again but it shows 200GB only but data is intact.
Now, my requirement is to let... (3 Replies)
Discussion started by: prvnrk
3 Replies
3. AIX
Hello all. I have a perplexing problem
I have an AIX 5.1 system on an EMC SAN.
This system had been on a CX400 SAN for several years. The system was migrated to a CX700 just over a week ago. The migration consisted of utilizing on of the HBAs in the system and connecting to both SANs
... (9 Replies)
Discussion started by: mhenryj
9 Replies
4. Solaris
Is there any way i can mount a zfs volume using snapshot or some other means ? (2 Replies)
Discussion started by: fugitive
2 Replies
5. Solaris
Hi, I need to expand a ZFS volume from 500GB to 800GB. I'd like to ask your help to confirm the following procedure:
Can I do it on the fly without bothering the users working on this volume?
Thank you in advance! (6 Replies)
Discussion started by: aixlover
6 Replies
6. Solaris
I have viewed a few previous posts regarding this, but none of them quite described or worked with my issue.
I am out of local disk space on my LDOM Manager but still have plenty of SAN vCPU and Memory available so I am trying to install a new LDOM OS on SAN.
I have exposed the SAN to the... (0 Replies)
Discussion started by: MobileGSP
0 Replies
7. Solaris
Apologies if this is the wrong forum..
I have some LDOMs running on a Sparc server. I copied the disk0 file from one chassis over to another, stopped the ldom on the source system and started it on the 2nd one. All fine. Shut it down and flipped back. We then did a fair bit of work on the... (4 Replies)
Discussion started by: tommyq
4 Replies
8. Red Hat
I have an IBM blade running RHEL 5.4 server, connected to two Hitachi SANs using common fibre cards & Brocade switches. It has two volume groups made from old SAN LUNs. The old SAN needs to be retired so we allocated LUNs from the new SAN, discovered the LUNs as multipath disks (4 paths) and grew... (4 Replies)
Discussion started by: rbatte1
4 Replies
9. Solaris
Hi all,
I'm using Solaris 11.3.
HBA port connected to SAN disk 3T.
AVAILABLE DISK SELECTIONS:
0. c0t600A0B800033696A0000214B571938F1d0 <SUN-CSM200_R-0760 cyl 44556 alt 2 hd 255 sec 189>
/scsi_vhci/ssd@g600a0b800033696a0000214b571938f1
1. c2t3C58620E0C565100d0... (1 Reply)
Discussion started by: manhte1
1 Replies
10. Solaris
Generally, this is what we do:-
On primary, export 2 LUNs (add-vdsdev).
On primary, assign these disks to the ldom in question (add-vdisk).
On ldom, created mirrored zpool from these two disks.
On one server (which is older) we have:-
On primary, create mirrored zpool from the two LUNs.... (4 Replies)
Discussion started by: psychocandy
4 Replies
LEARN ABOUT SUSE
sysdef
sysdef(1M) System Administration Commands sysdef(1M) NAME
sysdef - output system definition SYNOPSIS
/usr/sbin/sysdef [-i] [-n namelist] /usr/sbin/sysdef [-h] [-d] [-i] [-D] DESCRIPTION
The sysdef utility outputs the current system definition in tabular form. It lists all hardware devices, as well as pseudo devices, system devices, loadable modules, and the values of selected kernel tunable parameters. It generates the output by analyzing the named bootable operating system file (namelist) and extracting the configuration information from it. The default system namelist is /dev/kmem. OPTIONS
-i Prints the configuration information from /dev/kmem. This is the default and only needs to be specified if the configura- tion information from both /dev/kmem and the system file specified with the "-n namelist" option is needed. -nnamelist Specifies a namelist other than the default (/dev/kmem). The namelist specified must be a valid bootable operating system. -h Prints the identifier of the current host in hexadecimal. This numeric value is unique across all Sun hosts. -d The output includes the configuration of system peripherals formatted as a device tree. -D For each system peripheral in the device tree, display the name of the device driver used to manage the peripheral. EXAMPLES
Example 1: Sample output format The following example displays the format of the sysdef -d output: example% sysdef -d Node 'SUNW,Ultra-5_10', unit #-1 Node 'packages', unit #-1 (no driver) Node 'terminal-emulator', unit #-1 (no driver) Node 'deblocker', unit #-1 (no driver) Node 'obp-tftp', unit #-1 (no driver) Node 'disk-label', unit #-1 (no driver) Node 'SUNW,builtin-drivers', unit #-1 (no driver) Node 'sun-keyboard', unit #-1 (no driver) Node 'ufs-file-system', unit #-1 (no driver) Node 'chosen', unit #-1 (no driver) Node 'openprom', unit #-1 (no driver) Node 'client-services', unit #-1 (no driver) Node 'options', unit #0 Node 'aliases', unit #-1 (no driver) Node 'memory', unit #-1 (no driver) Node 'virtual-memory', unit #-1 (no driver) Node 'pci', unit #0 Node 'pci', unit #0 Node 'ebus', unit #0 Node 'auxio', unit #-1 (no driver) Node 'power', unit #0 Node 'SUNW,pll', unit #-1 (no driver) Node 'se', unit #0 (no driver) Node 'su', unit #0 Node 'su', unit #1 Node 'ecpp', unit #-1 (no driver) Node 'fdthree', unit #0 Node 'eeprom', unit #-1 (no driver) Node 'flashprom', unit #-1 (no driver) Node 'SUNW,CS4231', unit #0 (no driver) Node 'network', unit #0 Node 'SUNW,m64B', unit #0 Node 'ide', unit #0 Node 'disk', unit #-1 (no driver) Node 'cdrom', unit #-1 (no driver) Node 'sd', unit #1 Node 'dad', unit #1 Node 'pci', unit #-1 (no driver) Node 'SUNW,UltraSPARC-IIi', unit #-1 (no driver) Node 'pseudo', unit #0 [output truncated] FILES
/dev/kmem default operating system image ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
hostid(1), prtconf(1M), nlist(3ELF), attributes(5) SunOS 5.10 4 Oct 2004 sysdef(1M)