lv and filesystem mismatch

[Jeff Disney]

Hi all,

I am attempting to increase a filesystem to match the logical volume that is mounted on it and I receive the following error:

s fsadm -F vxfs -b 258M /u001/app/oracle/admin/t656b
vxfs fsadm: /dev/vg_oracle_656/rlv_u001_t656b_admin is currently 209920 sectors - size will be increased
vxfs fsadm: write failure at block 4458494 : No such device or address, what do I need to do to correct it? Thanks in advance.

[Marco Santerre · Accepted solution]

Is your file system currently full (100%), cause if it is, you'll need to make a little bit of space before you can use fsadm.

Also I would suggest you actually do the calculation : LVextent X PV Size X 1024
and place that number in the -b part of your fsadm command. That way it'll be more accurate and fsadm won't try to grow it bigger than what it really is

[Elmar P. Kolkman]

Are you sure your lvol is 258 Mb? Normally that is not possible, since LVM extents are 4 Mb and 258 is not dividable by 4!

I think you should use 256 Mb. Look at lvdisplay for the lines with Current LE or LV Size.

[Rita C Workman]

Well I alway use a small 'm'...
fsadm -F vxfs -b m /filesystem

...but just to be curious...Is this on a disk array? and is it by any chance EMC?..cause that failure to write at block makes me wonder..

Rita

[Helen French]

Couple of things:

1) Did you do a lvextend before fsadm. If not, try that 'lvextend -L new_size lvol_name

2) Check if you have required free space to extend the FS

3) Check the file system mount point you gave is right

4) Apply patches.

[Fabio Ettore]

Hi,

what is the exact size of lv?

Please past here
# lvdisplay /dev/vg_oracle_656/lv_u001_t656b_admin

and

# bdf

Anyway Marco is right. Maybe you is trying to extend the filesystem to a wronged size.

Best regards,
Ettore

[Alzhy]

If your filesystem is full, then you will need a few bytes freed before the increase will happen. Other possibilities - is your underlying LVOL really sized appropriately? meaning it is really 258MB as you wanted it?

Check your lvdisplay/vgdisplay output to verify...

Ta!

[Shahul]

Hi,

Just a query, You are getting error after the success message. It means your filesystem is getiing increased? Could you please check up by bdf command.

If it already increased try with fsck. If not increased you may start from lvextend command once again to see real problem.

Good luck
Shahul

[Todd McDaniel_1]

Couple of things...

1) What was the lvextend commmand you used? Can you please post it here? that may give a clue...What was the exact amount you used for the size?

2) I believe the previous posters are right... what is your bdf output say? You may be at >98% used in the filesystem which can prevent you from increasing the mounted filesystem.

[T. M. Louah]

did you extend the logical volume first, try defragmenting using SAM -- or
# fsadm -e -E -d -D filesystem
then :
# fsadm -F vxfs -b 258M filesystem
if that doesnot work :
# umount /mount_point
# lvextend -L Megabytes /dev/vgname/lvolname
# extendfs -F vxfs /dev/vgname/rlvolname
# mount /mount_point
# bdf to verify

Now if all fails,and u ve got a recent bk it might be faster for you to :
# lvremove /dev/vgname/lvolname
# lvcreate -L Megabytes -n lvname /dev/vgname
# newfs -F vxfs /dev/vgname/rlvolname
# mount /dev/vgname/lvolname /mount_point
remember to modify /etc/fstab accordingly

T+

[Jeff Disney]

Thanks to all that responded, the reason it was not extending is that when I tried to extend the filesystem I wasn't using the correct number of the lv size, yesterday I was able to get it to extend properly. Once again I really appreciate all the help I receive in the forums, and to everyone a good day.