How to replace internal disk in V880 which is under veritas control to increase space
Recently I had a task to replace disk in veritas, I had 72gb FC drive and I needed to replace it with 146gb FC drive to gain some additional space in my V880 server. Server has 6 internal disks. I cannot just pull disk out of V880, I have to use luxadm to offline it.
First step is to identify the Enclosure in your V880 server, to accomplish this task I need to run luxadm probe
# luxadm probe
Found Enclosure:
SUNWGS INT FCBPL Name:FCloop Node WWN:50800200001b1fc8 Logical Path:/dev/es/ses0
#
In our case it’s called FCloop
Next I want to display all this info back:
# luxadm display FCloop
SUNWGS INT FCBPL
DISK STATUS
SLOT DISKS (Node WWN)
0 On (O.K.) 2000000087142034
1 On (O.K.) 20000000870c4554
2 On (O.K.) 2000000087142680
3 On (O.K.) 2000000087140ed2
4 On (O.K.) 2000000087141820
5 On (O.K.) 20000000871429aa
6 On (Login failed)
7 On (Login failed)
8 On (Login failed)
9 On (Login failed)
10 On (Login failed)
11 On (Login failed)
SUBSYSTEM STATUS
FW Revision:9226 Box ID:0
Node WWN:50800200001b1fc8 Enclosure Name:FCloop
SSC100′s – 0=Base Bkpln, 1=Base LoopB, 2=Exp Bkpln, 3=Exp LoopB
SSC100 #0: O.K.(9226/ FD99)
SSC100 #1: O.K.(9226/ FD99)
SSC100 #2: Not Installed
SSC100 #3: Not Installed
Temperature Sensors – 0 Base, 1 Expansion
0:21ºC
1Not Installed
Default Language is USA English, ASCII
#
# echo | format
Searching for disks…done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100000087142034,0
1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000870c4554,0
2. c1t2d0 <HITACHI-DK32EJ72FSUN72G-2Q09 cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100000087142680,0
3. c1t3d0 <HITACHI-DK32EJ72FSUN72G-2Q09 cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100000087140ed2,0
4. c1t4d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100000087141820,0
5. c1t5d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871429aa,0
Specify disk (enter its number): Specify disk (enter its number):
#
Both luxadm and format does show me the WWN for the drive that I would like to replace 2nd disk which is c1t1d0 and has WWN ending with 870c4554. It is in slot 2 in my V880 server. Now I have two options. Offline it with luxadm and have it failed in veritas, then use vxdiskadm and just chose option 5 in there “Replace a failed or removed disk” or I can chose option 4 under vxdiskadm which is “Remove a disk for replacement”. I think 2nd choice is certainly much safer.
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c1t0d0s2 auto:sliced rootdisk1 rootdg online
c1t1d0s2 auto:sliced rootdisk2 rootdg online
c1t2d0s2 auto:sliced mydisk mydg online
c1t3d0s2 auto:sliced mydisk mydg online
c1t4d0s2 auto:sliced mydisk mydg online
c1t5d0s2 auto:sliced mydisk mydg online
#
Run vxdiskadm option 4 to remove the disk for replacement (in our case it is c1t1d0s2). After running vxdiskadm the output should look similar to this:
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c1t0d0s2 auto:sliced rootdisk1 rootdg online
c1t1d0s2 sliced - - online
- - rootdisk2 rootdg removed was: c1t1d0s2
c1t2d0s2 auto:sliced mydisk mydg online
c1t3d0s2 auto:sliced mydisk mydg online
c1t4d0s2 auto:sliced mydisk mydg online
c1t5d0s2 auto:sliced mydisk mydg online
Put the disk into offline state; # vxdisk offline c1t1d0s2
VxVM is ready for removal of the disk, run the luxadm offline to remove the WWN entries and device links for the failed drive ; # luxadm -e offline /dev/rdsk/c1t1d0s2
Do the luxadm to remove the device. ; #luxadm remove_device /dev/rdsk/c1t1d0s2
check the device file
#devfsadm -C ; # ls -ld /dev/rdsk/ c1t1d0*
Replace the disk physically
Run the devfsadm
# devfsadm
verify with luxadm display
# luxadm display FCloop
label the disk ; use format and label
# vxdctl enable
# vxdisk list ; now I can see my disk.
At this moment I needed to use vxdiskadm option 5 to replace the disk. Did answer yes to the access question.
Check status of syncing disks, it will take a while depending on the amount of data you might have on that disk but you certainly should see progress ; # vxtask list
After completing those steps I did see my disk back and it is now 146gb instead of 73gb, at least that’s what I see space on disk, next step is to grow file system on that disk to max or just to desired space that I would like.
First step is to verify that there is enough space available to grow the volume.
Syntax: vxassist maxgrow <volume-name>
# vxassist maxgrow ora1
Next verify the filesystem type by checking /etc/vfstab
Last grow the filesystem:
Syntax: /usr/lib/vxvm/bin/vxresize -F <filesystem type> -g <diskgroup> <volumename> + <size>
/usr/lib/vxvm/bin/vxresize -F vxfs -g mydg ora1 +16g
So I think this concludes on what I had to do to replace my smaller disk with higher capacity one and all the commands that I had to run for it to expand my space.
