vxfs fsadm: write failure

[Gino Castoldi_2]

Hi,


lvdisplay /dev/vg01/lvu01
--- Logical volumes ---
LV Name /dev/vg01/lvu01
VG Name /dev/vg01
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 3072
Current LE 768
Allocated PE 768
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

10 points to any good answer.
TIA, Gino

[Sridhar Bhaskarla]

Hi Gino,

There you go

LV Size (Mbytes) 3072


Your previous 'lvextend' was not successful or you didn't run. Once the LV is extended, then only you can extend the filesystem on it.


-Sri

[Gino Castoldi_2]

Hi,

I ran it this time and it seems to be successful.

bosov2 / # # fsadm -F vxfs -b 4194304 /u01
bosov2 / #

I didn't see any errors but a 'bdf' shows the same size as before. Should I run the
'fsadm' command again?

/dev/vg01/lvu01 3145728 1898601 1170525 62% /u01

10 points to any good answer.
TIA, Gino

[A. Clay Stephenson]

The correct sequence for this assumming that you want to "shrink" filesystem "A" and extend filesystem "B" using the freed space is:

1) fsadm -b filesystemA using a smaller value
2) lvreduce filesystemA's LVOL
3) lvextend filesystemB's LVOL
4) fsadm -b filesystemB using a larger value

Anything else is simply wrong.

[Sridhar Bhaskarla]

Hi Gino,

You should have seen a message '...size will be increased'.

It doesn't hurt to run fsadm again. Worst the case it is going to error out.

-Sri

PS: You don't need to say '10 points to any good answer'. People here will respond whether you assign points or not.

[pap]

Hi Gino.

I think we are confused here.
Please let us know following.

1. what was the original size of /u01?
2. What will be the final size for this LV?
3. What is the situation now.
4. What commands u ran to accomplish that.?

Thanks,

-Piyush.

[Gino Castoldi_2]

Hi,

I ran 'lvextend' again and it failed most likely because there's not enough allocatable space available.

bosov2 / # lvextend -L 4096 /dev/vg01/lvu01
lvextend: Not enough free physical extents available.
Logical volume "/dev/vg01/lvu01" could not be extended.
Failure possibly caused by strict allocation policy



10 points to any good answer.
TIA, Gino

[pap]

So what's the problem now?

If no space is available in vg, then allocate and try to extend the LV.

Thanks
-pap

[Sridhar Bhaskarla]

Hi,

I believe we are going in rounds and rounds.

1. Your lvextend later was successful.

lvextend -L 4096 /dev/vg01/lvu01

Confirm it first with 'lvdisplay /dev/vg01/lvu01' again.

2. Run fsadm

fsadm -F vxfs -b 4194304 /u01

or

fsadm -F vxfs -b 4096m /u01

You should see a message "... will be increased" there.


-Sri

[Gino Castoldi_2]

Hi,

I used a smaller amount of disk space and I ran those two commands successfully.
I guess the rule here is to check how much
space is available regardless of what has been reduced/extended on a volume group.

lvextend -L 3500 /dev/vg01/lvu01
Logical volume "/dev/vg01/lvu01" has been successfully extended.
Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf

fsadm -F vxfs -b $((3500*1024)) /u01
vxfs fsadm: /dev/vg01/rlvu01 is currently 3145728 sectors - size will be increased
bosov2 / # bdf /u01
Filesystem kbytes used avail %used Mounted on
/dev/vg01/lvu01 3584000 1898714 1581299 55% /u01

10 points to any good answer.
TIA, Gino