Fsadm problems during fs resize

[Anders Blomkvist]

I want to resize my /var fs from 295 PE's to 370 PE's but when I run fsadm after extending the LV I get the following error:
fsadm: cannot shrink /dev/vg00/rlvol8 - upgraded fs - inodes are currently in use.

The fsadm command I use is:
fsadm -F vxfs -b 378880 /var
and the original 295 PE's translate to 302080 blocks. Why does fsadm think I am resizing the fs?

[Anders Blomkvist]

EDIT: Why does fsadm think I am reducing the fs?

[Chris Wilshaw]

When extending filesystems, I usually go for

extendfs -F vxfs /dev/vgxx/rlvolyy

I've never had any problems with that approach.

[Anders Blomkvist]

Yes but I need to resize the fs online. Extendfs requires me to umount the fs which is a bit troublesome when it comes to /var

[Robert-Jan Goossens · Accepted solution]

Anders,

could you check your MB size

# lvdisplay -v /dev/vg00/lvol8 | grep Size

fsadm -F vxfs -b no_of_MB*1024 /var

Robert-Jan.

[Anders Blomkvist]

It worked! I got this message from fsadm:
fsadm: /dev/vg00/rlvol8 is currently 1208320 sectors - size will be increased

From bdf I can see that the filesystem now spans over all 370 PEs. Why is this? I thought that the blocks specified with the -b option in fsadm is calculated by PE*1024 and this is how I've done it in the past. Is this wrong - should I calculate the blocks as Size*1024 instead?

[Robert-Jan Goossens]

Hi Anders,

going to give you link to a discussion about the option of fsadm, take a look at remarks made by Rita and Darrel.

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x5fc4c8ecad09d6118ff40090279cd0f9,00.html

Kind regards,

Robert-Jan.