From: Gary Wilson (gwilson@plus.net)
Date: Tue Jul 05 2005 - 01:47:18 EDT
Hi all - new to the list so please be gentle :)
I have run into a problem whilst trying to expand a volume on SUN T3
storage.
The basic setup is that we have 2 T3 units, and I have a volume on
the second unit, which I wish to grow using feee space also on the
second unit.
I did a very similar operation back in October with volumes and free
space on the first unit with no problems at all.
The volume expands with no problem, but fsadm always reports a write
error.
# vxresize -o verify -x web2 +500000
UX:vxfs fsadm: ERROR: write failure at block 245616782 : No such device
or address
vxvm:vxresize: ERROR: Problem running fsadm command for volume web2, in
diskgroup rootdg
# vxresize -D -x web2 +50G
vxvm:vxresize: INFO: volume: web2 new_length=587202560 media=
vxvm:vxresize: INFO: usetype: fsgen old_length=482344960
vxvm:vxresize: INFO: devname: /dev/vx/rdsk/rootdg/web2
blkname=/dev/vx/dsk/rootdg/web2
vxvm:vxresize: INFO: devname2: /dev/vx/rdsk/web2
blkname2=/dev/vx/dsk/web2
vxvm:vxresize: INFO: filesystem type: VXFS
vxvm:vxresize: INFO: /dev/vx/rdsk/rootdg/web2 is mounted on /web2
vxvm:vxresize: INFO: VXASSIST_CMD: /usr/sbin/vxassist -g rootdg growto
web2 587202560 2>&1
vxvm:vxresize: INFO: VXASSIST_CMD: volume web2, diskgroup rootdg is
currently 482344960 sectors - size will grow to 587202560 sectors
vxvm:vxresize: INFO: VXFS_FSADM_CMD: /usr/lib/fs/vxfs/fsadm -Fvxfs -r
"/dev/vx/rdsk/rootdg/web2" -b 587202560 "/web2"
vxvm:vxresize: INFO: UX:vxfs fsadm: INFO: /dev/vx/rdsk/rootdg/web2 is
currently 482344960 sectors - size will be increased
UX:vxfs fsadm: ERROR: write failure at block 297795582 : No such device
or address
vxvm:vxresize: ERROR: Problem running fsadm command for volume web2, in
diskgroup rootdg
vxvm:vxresize: INFO: Filesystem grow failed. Volume web2, diskgroup
rootdg will be restored to original size. It is currently 482344960
sectors - size will shrink to 587202560 sectors
vxvm:vxresize: INFO: VXASSIST_CMD: /usr/sbin/vxassist -f -g rootdg
shrinkto web2 482344960 2>&1
vxvm:vxresize: INFO: VXASSIST_CMD: volume web2, diskgroup rootdg
currently 587202560 sectors - size will shrink to 482344960 sectors
Here's the volume in it's original state:
# vxprint -ht web2
Disk group: rootdg
V NAME RVG KSTATE STATE LENGTH READPOL
PREFPLEX UTYPE
PL NAME VOLUME KSTATE STATE LENGTH LAYOUT
NCOL/WID MODE
SD NAME PLEX DISK DISKOFFS LENGTH [COL/]OFF DEVICE
MODE
SV NAME PLEX VOLNAME NVOLLAYR LENGTH [COL/]OFF AM/NM
MODE
DC NAME PARENTVOL LOGVOL
SP NAME SNAPVOL DCO
v web2 - ENABLED ACTIVE 482344960 SELECT -
fsgen
pl web2-01 web2 ENABLED ACTIVE 482349056 CONCAT -
RW
sd t3_tb_thi-01 web2-01 t3_tb_thi 0 482349056 0 c2t3d0
ENA
and here's the spare disk space (from vxdg free):
rootdg t3_tb_thi c2t3d0s2 c2t3d0 482349056 518275072
-
vxdisk list:
# vxdisk list
DEVICE TYPE DISK GROUP STATUS
c1t0d0s2 sliced rootdisk rootdg online nohotuse
c1t1d0s2 sliced rootmirror rootdg online nohotuse
c2t1d0s2 sliced t3_tb_pri rootdg online nohotuse
c2t2d1s2 sliced t3_tb_sec rootdg online nohotuse
c2t3d0s2 sliced t3_tb_thi rootdg online
And format:
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cfe4ef50,0
1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>
/pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cfe4f195,0
2. c2t3d0 <SUN-T300-0201 cyl 34901 alt 2 hd 224 sec 128>
/pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50020f230000b75a,0
3. c2t50020F230000FC5Dd1 <SUN-T300-0201 cyl 34901 alt 2 hd 224
sec 128>
/pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50020f230000fc5d,1
4. c2t50020F230000FC7Cd0 <SUN-T300-0201 cyl 34901 alt 2 hd 224
sec 128>
/pci@8,600000/SUNW,qlc@1/fp@0,0/ssd@w50020f230000fc7c,0
5. c3t3d0 <SUN-T300-0201 cyl 34901 alt 2 hd 224 sec 128>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w50020f230000b75a,0
6. c3t50020F230000FC5Dd1 <SUN-T300-0201 cyl 34901 alt 2 hd 224
sec 128>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w50020f230000fc5d,1
7. c3t50020F230000FC7Cd0 <SUN-T300-0201 cyl 34901 alt 2 hd 224
sec 128>
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w50020f230000fc7c,0
There are no obvious problems in /var/log/syslog or /var/adm/messages
(i.e. no mention of disk problems), and the free space came from a
volume I destroyed this very morning and was previously in use with no
issues. I can create a seperate volume using the free space and put a
filesystem on it with no issues - so the problem is definately with
growing the filesystem, rather than the disk itself at fault -
at least that's how it seems) - also the existing volume on the disk is
also in use with no issues, although it is 94% full (as according to df)
Can anyone suggest what on earth is going on here and what the problem
might be?
Many thanks
Gary Wilson
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:31:03 EDT