vxfs fsadm: write failure

[Gino Castoldi_2]

Hi,

Server: HPUX 11.0 OnlineJFS 3.3 Version 4

I am trying to increase the size of one file system after I reduced the size of another file system that are on the same volume group
(vg01). When I tried to increase disk space it failed with this error.

# fsadm -F vxfs -b 4096000 /u01
vxfs fsadm: /dev/vg01/rlvu01 is currently 3145728 sectors - size will be increased
vxfs fsadm: write failure at block 8290302 : No such device or address

10 points to any good answer.
TIA, Gino

[Sridhar Bhaskarla · Accepted solution]

HI Gino,

YOu didn't run 'lvextend' prior to using fsadm. If you didn't then you are not specifying the exact size in fsadm that you used with your lvextend. It is convenient to use 'm' suffix to the size so that there won't be any confusion.

lvextend -L 4096 /dev/vgxx/lvolx
fsadm -b 4096m /u01

-Sri

[A. Clay Stephenson]

Did you do an lvextend BEFORE doing the fsadm -b? Also, fsadm -b will fail if the filesystem is full (or very nearly so).

[James A. Donovan]

Generally, this error means you are trying to extend the file system to a size larger than the underlying logical volume.

Did you run the lvextend command first on the logical volume on which the /u01 file system is placed?

First,
lvextend -L 4000 /dev/vgXX/lvolY

then,

fsadm -F vxfs -b $((4000*1024)) /u01

If you use the $(( )) syntax, then you let the shell do the math for you.

[RAC_1]

First thing. Do you have Online JFS installed? If yes the procedure to reduce the lvol is as follows.

I strongly recommand taking full backup prior to this.

For the lvol where you reduced the size.

fsadm -F vxfs -b "new_size_in_MB" /mount_point

lvreduce -L "size_in_MB" /dev/vgxx/lvolxx

Then check vgdisplay and see if free PE have increased or not?

If the free space is there then you do lvextend and then fsadm.

Anil

[Gino Castoldi_2]

Hi,

Here's what I ran in sequential order:

lvextend -L 1024 /dev/vg01/lvu01
(this was too small an allocation).
lvextend -L 4096 /dev/vg01/lvu01
vgdisplay /dev/vg01
fsadm -F vxfs -b 4096000 /u01

10 points to any good answer.
TIA, Gino

[Gino Castoldi_2]

Hi,

I did successfully reduce the size of a different file system before I tried to increase the size of the file system. There were no errors and a 'bdf' shows the reduced size now.

10 points to any good answer.
TIA, Gino

[Helen French]

After lvreducing the 'other' file system, did you check and make sure that the VG has enough free space? Is that file system is okay and working fine now? Check your VG information from vgdisplay command and then find out if you have enough PE available to increase this LV.

Also, try lvextend first and then fsadm. I would recommend doing backups of both file system prior doing all these.

[Sridhar Bhaskarla]

Hi Gino,

Find if the lvol is actually at 4096MB size by doing 'lvdisplay /dev/vgxx/lvolx'. If so, you should be able to extend.

-Sri

[James A. Donovan]

Just a note, IF the command had worked, you would have shorted yourself of space on your file system. The correct value for your fsadm command is 4194304 (4096*1024=4194304)

lvextend -L 4096 /dev/vg01/lvu01
fsadm -F vxfs -b $((4096*1024)) /u01