Getting error while issuing fsadm

[jsahibjon]

# fsadm -F vxfs -b 1048330M /ncs/celogs

vxfs fsadm: /dev/vg_celogs/rlv_celogs is currently 663889920 sectors - size will be increased

vxfs fsadm: attempt to resize /dev/vg_celogs/rlv_celogs failed with errno 28

[Pete Randall]

Did you run a re-org first?  Generally a good idea and prevents errors like this.

Oops - just noticed you're increasing, not decreasing.  Disregard.

[donna hofmeister]

according to symantec this can be either a fullness or fragmentation problem.

how up-to-date are you with your vxvm patches?  (and heed what pete said)

[Pete Randall]

Actually Donna's comment got me thinking about again and it could still help to run a re-org to unfragment things.  Might be worth a try.

[jsahibjon]

can u please give me the step by step procedure to extend the filesystem.

[James R. Ferguson]

Hi:

Standard 'errno' 28 equates to "no space left on device".  Check your specificartion of the new size.  Are you sure you 'lvetend'ed your logical volume, first?

Regards!

...JRF...

[Pete Randall]

1.  lvextend

2.  fsadm

[Rohak]

lvextend -L 70000 /dev/MyVG/lvol1
* the syntax is: lvexten -L <new size in Mb> <lvol path> - Now, increase the filesystem:
fsadm -b 70000m /filesystem
* the syntax is: fsadm –b <new size in Mb> <mount point>

lvdisplay

[Steven E. Protter]

Shalom,

You were working without a procedure?

lvextend -L <size in MB> <logical volume name> <disk to use>

Then your fsadm command.

You might want to check your license for Online JFS.

SEP

[Patrick Wallek]

If your filesystem is completely full (o KB free), then the fsadm to extend it can fail.  If possible, move a few files to another filesystem to your usage so you have some free space then try your fsadm command again.