File system full?

[Oleg Goudovany_1]

Hi, all!
Please help to understand one thing.
When I typed:
#dmesg
I got(part):
Networking memory for fragment reassembly is restricted to 10944512 bytes
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Logical volume 64, 0x4 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 393216
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0 - major is 31, minor is 0x6000; start = 52064, size = 196608 *
entry 1 - major is 31, minor is 0x5000; start = 1909183, size = 131073
* - Device not used
Starting the STREAMS daemons.
B2352B HP-UX (B.10.20) #1: Sun Jun 9 08:03:38 PDT 1996

Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 131072 Kbytes, lockable: 94780 Kbytes, available: 101396 Kbytes

/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full
/: file system full

I check:
#bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 83733 17597 57762 23% /
/dev/vg00/lvol1 47829 13834 29212 32% /stand
/dev/vg00/lvol10 288157 250460 8881 97% /var
/dev/vg00/lvol9 374933 307695 29744 91% /usr
/dev/vg00/lvol8 49861 14036 30838 31% /tmp
/dev/vg00/lvol7 900931 587260 223577 72% /opt
/dev/vg00/lvol6 1602737 693349 749114 48% /home
/dev/vg00/lvol5 99669 11 89691 0% /export

Please tell which file system is full?
OS - HP-UX 10.20
Thanx in advance.
Oleg

[Steve Steel · Accepted solution]

Hi

Messages could be in dmesg for a while

Looks like no more full disk


Check /var/adm/syslog/syslog.log for when message occurred


Steve Steel

[Jeff Schussele]

Hi Oleg,

dmesg is just a small circular buffer with no time stamps. So it's just showing you that at *some* point in the past / was indeed full.
You should be able to find entries for this event in the /var/adm/syslog/syslog.log file that will nail down the date/time it occurred.

Rgds,
Jeff

[twang]

If bdf command show that the filsystem is not full, forget the output of dmesg. because dmesg may show some older system message, check the exact event time in /var/adm/syslog/syslog.log

[Kent Ostby]

It was saying that / is full (the one that is now at 23%).

On the other hand, since you posted a full bdf, you may want to see what has /var at 97%.

/var/adm/crash is where crash dumps go to live so you may want to look in there to see if there are any old crash dumps that you want to delete.

Otherwise you can do:
cd /var
du | sort -nr | head

and it willive you some ideas in /var of what you might want to delete.

Best regards,

Kent M. Ostby