On Wed, May 13, 2009 at 11:42:43AM +0800, Wilkinson, Alex wrote: > Hi all, > > I have a LUN that I need to expand via vxresize
vxresize expands volumes and filesystems, not LUNs. Do you have a volume that is on a LUN that you already expanded? > #df -h . > Filesystem Size Used Avail Use% Mounted on > /dev/vx/dsk/RDL_DG/VOL01 > 17T 8.7G 16T 1% /export > > I found the exact free space available via: > > #vxdg -g RDL_DG free > > And then successfully did a resize via: > > #/etc/vx/bin/vxresize -g RDL_DG -F vxfs VOL01 +12502704 > > All looked good (from vxresize's prespective). > > However, parted(1) can see the expanded space but the partition table will not > allow me change its label: > > #parted /dev/sda > GNU Parted 1.8.1 > Using /dev/sda > Welcome to GNU Parted! Type 'help' to view a list of commands. > (parted) p What is the relationship between /dev/sda and VOL01? Maybe you can show the output of vxprint -ht VOL01? I'm beginning to think that VOL01 is built on top of /dev/sda and you're trying to get VxVM to see the enlarged LUN? > Model: DGC RAID 5 (scsi) > Disk /dev/sda: 23.6TB > Sector size (logical/physical): 512B/512B > Partition Table: gpt > > Number Start End Size File system Name Flags > 1 131kB 33.8MB 33.7MB > 2 33.8MB 17.7TB 17.7TB > > (parted) resize 2 17.7tb 23.6tb > Error: Could not detect file system > (parted) > > As you can see parted(1) does detect that /dev/sda is 23.6TB. > > df(1) does not see the new expanded 23.6TB but rather the old 17.7TB. > > Can anyone suggest why a vxresize would work perfectly fine yet tools such > as df(1) cannot "see" the new space on the expanded LUN ? I think neither the volume nor the filesystem has been expanded because VxVM doesn't notice when LUNs change size. What version of VxVM do you have? -- Darren _______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
