9 More Discussions You Might Find Interesting
1. HP-UX
Hello all,
So I made a rookie mistake today. I forgot to remove my disk from my disk group, before running the following command:for i in `ioscan -fnN | awk /NO/'{print $3}'`
do
rmsf -H $i
done
I am trying to run the following command, but not having any luck obviously:vxdg -g dgvol1 rmdisk... (0 Replies)
Discussion started by: mrkejames2
0 Replies
2. Solaris
Hello all,
i try to allocate the same LUN to two server (or more in the future)
i use solaris 10, vxvm (vxfs) for data and solaris zones and EMC DMX-4, i try to migrate solaris zones between servers in case of problem.
and this is what i want to do
- affect LUN to srv00124 and srv10155
-... (5 Replies)
Discussion started by: mat_solaris
5 Replies
3. Emergency UNIX and Linux Support
I have VxVM 5.1 running on Solaris-10. I have to increase a application file-system and storage team gave me a lun. After scanning scsi port by cfgadm, I can see them in format output. I labelled it, but I am not able to see them in "vxdisk list".
I already tried commands -->
vxdctl enable... (4 Replies)
Discussion started by: solaris_1977
4 Replies
4. UNIX for Dummies Questions & Answers
how do I know which hdisk from "lsdev -Cc disk" is my LUN on NetApp after zoning from SAN switch?
is it "MPIO other FC SCSI Disk Drive"? (1 Reply)
Discussion started by: malayo
1 Replies
5. Red Hat
Hi,
I have a SAN LUN of 550 GB created as an ext3 partition of the entire lun and need to make the lun and partition larger... 600 GB
# fdisk -l /dev/sdj
Disk /dev/sdj: 590.5 GB, 590558003200 bytes
255 heads, 63 sectors/track, 71797 cylinders
Units = cylinders of 16065 * 512 = 8225280... (3 Replies)
Discussion started by: jamba1
3 Replies
6. AIX
Hi,
I have an iSCSI LUN attached to an AIX 5.3 box. It's initial size is 250GB, I just grew it on the SAN to 300GB, but AIX is not seeing the change. Right now I have some processes going and it's eating up the disk space. I need to grow this lun by atleast 30GB otherwise the process with bomb... (5 Replies)
Discussion started by: bbbngowc
5 Replies
7. Solaris
I have a list of LUN ID, my task is to find if disk has been added or not. How do I do that? I have been searching the forum and not able to find answer.
thanks (4 Replies)
Discussion started by: uuontario
4 Replies
8. Solaris
Previously , i remove the disk by
#vxdg -g testdg -k rmdisk testdg02
But i got error when i -k adddisk
bash-2.03# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 auto:none - - online invalid
c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies
9. Solaris
VxVM:
How to add one more disk into v08 the stripe should change from 7/128 to 8/128
v v08 - ENABLED ACTIVE 8954292224 SELECT v08-01 fsgen
pl v08-01 v08 ENABLED ACTIVE 8954292480 STRIPE 7/128 RW
sd bkpdg35-01 v08-01 bkpdg35 17216 ... (0 Replies)
Discussion started by: geoffry
0 Replies
LEARN ABOUT HPUX
vxbrk_rootmir
vxbrk_rootmir(1M) vxbrk_rootmir(1M)
NAME
vxbrk_rootmir - break off a mirror of a VxVM root disk to create a separate root disk generation
SYNOPSIS
/etc/vx/bin/vxbrk_rootmir [-g diskgroup] [-v] [-b] [-t tasktag] {daname|dmname}
DESCRIPTION
The vxbrk_rootmir command creates a mirror of a Veritas Volume Manager (VxVM) rootable boot disk, breaks the mirror, and then makes the
broken-off mirror into a completely separate root disk that is suitable for booting by itself.
Except the specified target disk, the bootdg should not contain any disks other than valid root mirror disks. A valid root mirror disk
should have mirrors of all volumes in the bootdg. Thus, all disks must be exactly identical in terms of the volumes contained.
The given disk access name, daname, or disk media name, dmname, is first checked to see if it is already a valid root disk mirror. If so,
the mirror is broken off from the current VxVM root disk, and regenerated into a unique VxVM root disk. If the specified disk is not a
valid root disk mirror, and is unused for other purposes, the vxrootmir command is first called to mirror the specified disk from the cur-
rent VxVM root disk. After the mirroring operation is complete, the mirror is then broken off, and regenerated into a unique VxVM root
disk.
OPTIONS
-b Uses the setboot command to set the alternate boot disk to the specified disk. If the -v option is also specified, information is
displayed about the current setboot settings.
-g diskgroup
Specifies the disk group into which the newly broken-off mirror is to be placed. The disk group is created if it does not already
exist. If the disk group already exists, the broken-off mirror is added to it. If this option is not specified, the disk group of
the broken-off mirror is set to the current default disk group. However, the generation number is made different from the default disk
group to prevent the mirror from being automatically imported.
-t tasktag
Marks any tasks that are registered to track the progress of an operation with the specified tag, tasktag. This option is passed to
vxrootmir if it is necessary first to mirror the specified disk that is to be broken off.
-v Displays verbose output, including timestamps for operations that are in progress. This option is passed to vxrootmir if it is neces-
sary first to mirror the specified disk that is to be broken off.
ARGUMENTS
daname Specifies the disk to be used as the broken off mirror by its disk access name (such as c0t2d0).
dmname Specifies the disk to be used as the broken off mirror by its disk media name (such as rootdisk03).
EXAMPLES
This example shows the vxbrk_rootmir command being executed on a disk that already contains a valid root mirror:
/etc/vx/bin/vxbrk_rootmir -g brkdg -vb c4t15d0
VxVM vxbrk_rootmir INFO V-5-2-4023 17:47:
Checking specified disk(s) for presence and type
VxVM vxbrk_rootmir INFO V-5-2-4025 17:47:
DA c4t15d0s2, DM rootdisk06 is a valid root mirror
VxVM vxbrk_rootmir INFO V-5-2-4052 17:47:
Saving configuration data for later restoration
VxVM vxbrk_rootmir INFO V-5-2-4022 17:47:
Breaking off root mirror on DA c4t15d0s2
VxVM vxbrk_rootmir INFO V-5-2-4054 17:47:
Setting broken off mirror on c4t15d0s2 as unique root disk
VxVM vxbrk_rootmir INFO V-5-2-2566 17:47:
Preparing disk c4t15d0s2 as a VxVM root disk
VxVM vxbrk_rootmir INFO V-5-2-4046 17:47:
Patching devnodes, fstab and volboot file in new Root FS
VxVM vxbrk_rootmir INFO V-5-2-4045 17:47:
Patching /stand/bootconf file to contain new root disk
VxVM vxbrk_rootmir INFO V-5-2-2462 17:48:
Current setboot values:
VxVM vxbrk_rootmir INFO V-5-2-4048 17:48:
Primary: 0/0/2/0.2.0
VxVM vxbrk_rootmir INFO V-5-2-4010 17:48:
Alternate: 0/2/1/0.8.0.255.2.5.0
VxVM vxbrk_rootmir INFO V-5-2-4042 17:48:
Making c4t15d0s2 (0/2/1/0.8.0.255.1.15.0) the alternate boot disk
VxVM vxbrk_rootmir INFO V-5-2-4028 17:48:
Disk c4t15d0s2 is now a broken off root disk
The next example shows the command being executed on a disk that does not contain a valid root mirror, and which requires vxrootmir be
called to mirror the root disk first:
/etc/vx/bin/vxbrk_rootmir -g brkdg -vb c5t5d0
VxVM vxbrk_rootmir INFO V-5-2-4023 16:25:
Checking specified disk(s) for presence and type
VxVM vxbrk_rootmir INFO V-5-2-4043 16:25: Mirroring root disk
VxVM vxrootmir INFO V-5-2-2501 16:25:
Gathering information on the current VxVM root configuration
VxVM vxrootmir INFO V-5-2-2441 16:25:
Checking specified disk(s) for usability
VxVM vxrootmir INFO V-5-2-2566 16:25:
Preparing disk c5t5d0 as a VxVM root disk
VxVM vxrootmir INFO V-5-2-3766 16:25:
Disk c5t5d0 is now EFI partitioned disk c5t5d0s2
VxVM vxrootmir INFO V-5-2-2410 16:25:
Adding disk c5t5d0s2 to brkdg as DM rootdisk03
VxVM vxrootmir INFO V-5-2-1646 16:25:
Mirroring all volumes on root disk
VxVM vxrootmir INFO V-5-2-1648 16:25: Mirroring volume standvol
VxVM vxrootmir INFO V-5-2-1648 16:26: Mirroring volume swapvol
VxVM vxrootmir INFO V-5-2-1648 16:30: Mirroring volume rootvol
VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume homevol
VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume tmpvol
VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume usrvol
VxVM vxrootmir INFO V-5-2-1648 16:34: Mirroring volume optvol
VxVM vxrootmir INFO V-5-2-1648 16:36: Mirroring volume varvol
VxVM vxrootmir INFO V-5-2-1616 16:40:
Disk c5t5d0s2 is now a mirrored root disk
VxVM vxbrk_rootmir INFO V-5-2-4052 16:40:
Saving configuration data for later restoration
VxVM vxbrk_rootmir INFO V-5-2-4022 16:40:
Breaking off root mirror on DA c5t5d0s2
VxVM vxbrk_rootmir INFO V-5-2-4054 16:40:
Setting broken off mirror on c5t5d0s2 as unique root disk
VxVM vxbrk_rootmir INFO V-5-2-2566 16:40:
Preparing disk c5t5d0s2 as a VxVM root disk
VxVM vxbrk_rootmir INFO V-5-2-4046 16:41:
Patching devnodes, fstab and volboot file in new Root FS
VxVM vxbrk_rootmir INFO V-5-2-4045 16:41:
Patching /stand/bootconf file to contain new root disk
VxVM vxbrk_rootmir INFO V-5-2-2462 16:41: Current setboot values:
VxVM vxbrk_rootmir INFO V-5-2-4048 16:41:
Primary: 0/0/2/0.2.0
VxVM vxbrk_rootmir INFO V-5-2-4010 16:41:
Alternate: 0/2/1/0.8.0.255.2.0.0
VxVM vxbrk_rootmir INFO V-5-2-4042 16:41:
Making c5t5d0s2 (0/2/1/0.8.0.255.2.5.0) the alternate boot disk
VxVM vxbrk_rootmir INFO V-5-2-4028 16:41:
Disk c5t5d0s2 is now a broken off root disk
SEE ALSO
vxbootsetup(1M), vxdg(1M), vxintro(1M), vxrootmir(1M), vxtask(1M)
VxVM 5.0.31.1 24 Mar 2008 vxbrk_rootmir(1M)