vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)

[Gaurav Verma]

While taking backup of the database server, I hv come across EOT, it ask for 2nd volume, I typed Y, gave a name "backup", but after 2 mins it terminated.
After this I again tried to take offline backup, but after 2hrs the error message "vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)"
is appearing.
my bdf output is:

nokdb:/#bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 516096 515116 960 100% /
/dev/vg00/lvol1 303125 50378 222434 18% /stand
/dev/vg00/lvol6 3072000 2166756 849292 72% /var
/dev/vg00/lvol7 1228800 763661 436095 64% /usr
/dev/vg00/lvol5 204800 21165 172227 11% /tmp
/dev/vg00/lvol4 2252800 993676 1180487 46% /opt
/dev/vg00/nmsopt 3072000 2114040 898135 70% /d/nmsopt
/dev/vgdb01/db01 35508224 8564392 26733368 24% /d/db01
/dev/vgdb/db 138395648 77039280 60877184 56% /d/db
nokdb:/#

[James R. Ferguson · Accepted solution]

Hi:

It is quite possible that instead of specifying a special device file like '/dev/rmt/0m' you mistyped the zero as the letter "o". Thus, you created a regular file in '/dev' named '/dev/rmt/om' thereby filling the root filesystem.

Look for regular (non-special) files in '/dev' -- ones in an 'ls' listing that don't begin wih "c" that are very large.

Secondarily, look for large files or directories in a sorted list like this:

# du -kx / | sort -k1nr | more

Regards!

...JRF...

[Gaurav Verma]

thnx... a lot..

someone logged into my system, and founf the file. thnx for ur support.

Br//
Gaurav