Did you umount /export before running vxresize? The resize code for VxFS is in the kernel module and requires that the file system being resized is mounted, but not having it mounted would cause that stage of vxresize to not happen. If that is the case, you should be able to use fsadm to finish your work.
The volume layout would be useful in debugging this, as would the exact sequence of commands used in the entire process and any messages that were printed. This would help in figuring out how many of your steps worked as intended. You should also be clearer about what you are trying to accomplish. I presume that the order of operations you wanted was something similar to the following: 1) Resize the LUN in the array 2) Get the OS to see the new LUN size 3) Get VxVM to see the new LUN size and increase the available space in the disk group 4) Use the new space in the disk group to increase the size of a volume 5) Grow the file system on that volume to use the increased size These steps don't directly correspond to commands that should be run, but conceptual stages in the process. In particular, vxresize should accomplish both steps 4 and 5. You should also mention what version of Storage Foundation you are using, including any MP, RP, or hotfixes. -----Original Message----- From: veritas-vx-boun...@mailman.eng.auburn.edu [mailto:veritas-vx-boun...@mailman.eng.auburn.edu] On Behalf Of Wilkinson, Alex Sent: Tuesday, May 12, 2009 8:43 PM To: veritas-vx@mailman.eng.auburn.edu Cc: duncan.c...@dsto.defence.gov.au; greg.robin...@dsto.defence.gov.au Subject: [Veritas-vx] vxresize -> but df(1) doesn't see new space ... ? Hi all, I have a LUN that I need to expand via vxresize #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 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 have also tried a "partprobe /dev/sda" which had no effect. As well as rebooted. OS is Centos 5.3 x86_64. Thanks! -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email. _______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx _______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
