error message msgcnt 85 mesg 001: V-2-1: vx_nospace

[Scott Lindstrom_2]

We have a file system that went up to 95% full yesterday and have been asked to double it in size.

/dev/vg27/lvol12 4194304 2724901 1404501 66% /filesystem

I doubled the lvol with no problem:

LV Name /dev/vg27/lvol12
VG Name /dev/vg27
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 8192
Current LE 512
Allocated PE 512
Stripes 0
Stripe Size (Kbytes) 0
Bad block NONE
Allocation strict
IO Timeout (Seconds) default

But when I try to increase the file system itself I get the messagge in the subject line.

We run "fsadm -F vxfs -b $((512*16*1024)) /filesystem" which calcs out to:
fsadm -F vxfs -b 8388608 /filesystem

vxfs: msgct 90 mesg 001: V-2-1:vx_nosace - /dev/vg27/lol12 fle yste fl (26 loc extent)

The message is better seen in syslog or dmesg:

vxfs: NOTICE: msgcnt 85 mesg 001: V-2-1: vx_nospace - /dev/vg27/lvol12 file system full (1024 block extent)
vxfs: NOTICE: msgcnt 87 mesg 001: V-2-1: vx_nospace - /dev/vg27/lvol12 file system full (1024 block extent)
vxfs: NOTICE: msgcnt 89 mesg 001: V-2-1: vx_nospace - /dev/vg27/lvol12 file system full (256 block extent)

(Three tries)
I am at a loss here; I don't find any similar hits here

[Alzhy]

Maybe at the time you adjusted the filesystem size the filesystem has no space available (fully 100% used)?

VxFS filesystem expansion requires a few KB free on the filesystem.

[Scott Lindstrom_2]

I seen that problem when the file system is 100% full but it's only 66% full now. So I don't think we the 'deleted open file' problem that sometimes causes problems.

[Alzhy]

Give us:

fstyp -v /dev/vg27/lvol12

[Scott Lindstrom_2]

#fstyp -v /dev/vg27/lvol12
vxfs
version: 6
f_bsize: 8192
f_frsize: 1024
f_blocks: 4194304
f_bfree: 1466107
f_bavail: 1374476
f_files: 1041068
f_ffree: 366524
f_favail: 366524
f_fsid: 1076297740
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 16
f_fsindex: 9
f_size: 4194304

[Alzhy]

Hmm..

Your Block size is 8KB. Shouldn't "-b" take on block values (sector size)? - which means your -b should be 1048576?

I am unsure though... IIRC, I recall I was even able to use -b values like 8G etc....

[Scott Lindstrom_2]

I found some entries here asking that same question but it seems that everyone agrees the f_frsize does not change how you do the calc.

Almost all of the rest of our file systems are like this:

f_bsize: 8192
f_frsize: 8192

and we use '*1024' in the calc.

This file system is:

f_bsize: 8192
f_frsize: 1024

which is unusual for us but I don't know how that figures into the problem.

[rajesh_32]

Try simple things :)

fsadm -F vxfs -b 8192M /filesystem