/dev/root file system full from dmsg command

[tay thiang hui henry]

When doing a dmsg command on a L3000 server, I encountered the following errors below.
Please advise what I should do to resolve this ?

/dev/root file system full (1 block extent)
msgcnt 169 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 171 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 173 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 175 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 177 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 179 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 181 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 183 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 185 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 187 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 189 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 191 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 193 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 195 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 197 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 199 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 201 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 203 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 205 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 207 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)
msgcnt 209 vxfs: mesg 001: vx_nospace - /dev/root file system full (1 block extent)

[V.Tamilvanan · Accepted solution]

Hi,
Your root FS is full . check for any core and unwanted files and clean it.

[twang]

To find the big files:
# find / -xdev -size +10000000c -exec ll {} \;
You may find some core dump files, then remove them.

[john korterman]

Hi,

first you should check if there is a problem. The message is of course that the root dir. is full, but it could be an old message, as the messages in the dmesg uffer are only removed at boot.
Does a bdf show that your root filesystem is full?

regards,
John K.

[Hari Kumar]

first see what files are large, whethre they are useful or not
#du -x |sort -n
Check your mnttab , if corrupted move it
#mv /etc/mnttab /etc/mnttab.old
then do this
#mount -a
and find also what is mounted on \ and preventive care is make user root to be logged in its /home/root for its default home
And last check for /dev files also for their sizes like /dev/rmt/0m e.t.c for their misuse

Have A Nice Day

[Naveej.K.A]

Check the space on the root file system. and make sure you delete the unused files.

This could be an old message also which is still there in dmesg buffer

[tay thiang hui henry]

Hi,
bdf command show that the filsystem is not full ...,
/dev/vg00/lvol3 188416 51810 128123 29% /
/dev/vg00/lvol1 111637 48001 52472 48% /stand
/dev/vg00/lvol8 2097152 266618 1716789 13% /var
/dev/vg00/lvol7 2097152 1335060 714515 65% /usr
/dev/vg00/lvol6 1048576 457518 554158 45% /tmp
/dev/vg01/lvol3 12582912 7853146 4584026 63% /sc_var
/dev/vg01/lvol1 2097152 460268 1534584 23% /sc_opt
/dev/vg01/lvol2 2097152 236466 1744454 12% /sc_etc
/dev/vg00/lvol5 2097152 1419788 635080 69% /opt
/dev/vg00/lvol4 1048576 42321 943451 4% /home

[Balakumar M]

Hi,
change the directory to the "/", list all the files by "ll" command, check weather any unwanted large files or core file under the root ( apart from the mounted directory). Move the large file under root to some other mount point or remove those files ( if its not required).

-Bala

[aparna challagulla]

hi henry,

we had a similar problem few weeks back.these are the few of the solutions that i got from this forum itself.

1. check the root filesystem using bdf
2. remove any core files is any

find / -type f -name core -print -exec file{}\;

3. check for large files and directories in / and remove/move all unwanted/old/unrealted files from the root filesystem.

4. to prevent core files from occuring, put this into /etc/profile -
ulimit -Sc 0

5. see whether there are any links on the mounted volumes which are pointing back to the root

find / exec ll {} \; | grep ' -'

HTH
aparna

[aparna challagulla]

hi henry,

just saw ur post. since / is not really full i guess ur problem is solved

bye
aparna

[john korterman]

Hi again,
since your root file system is not full, there is no current problem. But as mentioned, the buffer holding dmesg messages is only emtied at reboot. The messages mean that at a certain time since last reboot your root filesystem was full, but it does not say when. So it is a matter of getting used to dmesg.

regards,
John K.

[Suresh Patoria]

Hi,

What the /var/adm/syslog/syslog.log file out put

pls put the syslog.log file output

and i am suggesting pls check the file system Consistency using the fsck command


Thanx

[tay thiang hui henry]

Hi all,

Thanks for the informations received ....,