OnlineJFS, fsadm error RC# 28, explanation needed

[Ralph Grothe]

Hello fellow sysadmins,

I have the ubiquitious filesystem space filled up syndrom.
Lucky us I thought, since we have OnlineJFS on this box.
So I did what I usually do in such circumstances, i.e. looking for free PEs in the VG, lvextending, fsextending by fsadm.
All worked, except for the last step, which had always worked so far.
Instead fsadm returned error code 28.
But see the short protocol below:

# bdf /usr/sap/Z01
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol11 409600 409600 0 100% /usr/sap/Z01
# lvextend -L 800 /dev/vg00/lvol11
# lvdisplay /dev/vg00/lvol11
--- Logical volumes ---
LV Name /dev/vg00/lvol11
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 800
Current LE 200
Allocated PE 200
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

# fsadm -b `echo 800*1024|bc` /usr/sap/Z01
fsadm: /etc/default/fs is used for determining the file system type
fsadm: /dev/vg00/rlvol11 is currently 409600 sectors - size will be increased
fsadm: attempt to resize /dev/vg00/rlvol11 failed with errno 28


Can anyone tell me what RC No 28 relates to?
I haven't found an explanation in the manpage of fsadm_vxfs. :-(
What can I do to get my filesystem extended while the DB is up (production system, no downtime possible)?

TIA
Ralph

[Carsten Krege · Accepted solution]

The error 28 is a standard unix error and can be found in /usr/include/sys/errno.h. It is ENOSPC (no space left on device).

I suggest you try one of the following:

1) free up a little space in the filesystem
2) try to defragment the filesystem

A fragmentation report can be obtained by

# fsadm -D -E

The actual defragmentation can be done by

# fsadm -D -d -E -e

Carsten

[Alex Glennie]

I think this is a known issue : CR# JAGad08500

Online JFS filesystems cannot be extended if the filesystem is completely full (100%).

[Balakumar M]

Hi,
Error 28 in fsadm is mean the filesystem is 100% full. You can try this,
Clear up the some files, make it to 97% or less then that, and then try with fsadm. If its not work then you need to restart the system and bring the system to single user mode run extendfs. Because it /usr montpoint, you can not umont the mont point.

Bala,

[Ralph Grothe]

Thank you all,

this was a very quick remedy indeed,
faster than the HP support hotline here in Germany ;-)
A defragmentation run wasn't even necessary.
It fully sufficed to temporarily move a file out of the filesystem.
Please, no more replies.
The problem has been, thanks to the already posted hints, solved, and I will not assign anymore points in this matter.