Hi guys,

In the daily run output, the disk status always starts to look a bit strange on one of my machines. I think this starts after about three weeks of uptime.

It never seems to cause any serious problems, but today I decided to find out why this happens. :) I couldn't find any answers on Google (or the list archives, which search function seems to be broken).

df (both in the daily run and manual df -hi) starts showing mountpoints that are not mountpoints. Like var/spool and usr/local. Why these suddenly show up in the df output I'd like to know... :)

The output looks like this:

Disk status:
df: libexec stats possibly stale
df: lib stats possibly stale
df: usr/lib stats possibly stale
df: usr/sbin stats possibly stale
df: usr/share stats possibly stale
df: usr/bin stats possibly stale
df: usr/man stats possibly stale
df: usr/X11R6 stats possibly stale
df: usr/libexec stats possibly stale
df: usr/local/bin stats possibly stale
df: usr/local/lib stats possibly stale
df: var/spool stats possibly stale
df: var/lib stats possibly stale
df: var/run stats possibly stale
df: var/log stats possibly stale
df: jacco stats possibly stale
df: tmp stats possibly stale
df: dev stats possibly stale
df: bin stats possibly stale
df: proc stats possibly stale
Filesystem     1K-blocks     Used     Avail Capacity  Mounted on
/dev/da0s1a       507630    79532    387488    17%    /
devfs                  1        1         0   100%    /dev
/dev/da0s1d       507630    58770    408250    13%    /tmp
/dev/da0s1f     13694960  5729928   6869436    45%    /usr
/dev/da0s1e      1506190  1244500    141196    90%    /var_local
devfs                  1        1         0   100%    /var/named/dev
procfs                 4        4         0   100%    /proc
/libexec          507630    79532    387488    17%    libexec
/lib              507630    79532    387488    17%    lib
/usr/lib        13694960  5729862   6869502    45%    usr/lib
/usr/sbin       13694960  5729862   6869502    45%    usr/sbin
/usr/share      13694960  5729862   6869502    45%    usr/share
/usr/bin        13694960  5729862   6869502    45%    usr/bin
/usr/man        13694960  5729862   6869502    45%    usr/man
/usr/X11R6      13694960  5729862   6869502    45%    usr/X11R6
/usr/libexec    13694960  5729862   6869502    45%    usr/libexec
/usr/local/bin  13694960  5729862   6869502    45%    usr/local/bin
/usr/local/lib  13694960  5729862   6869502    45%    usr/local/lib
/var/spool      83886080  3969332  79916748     5%    var/spool
/var/lib        83886080  3969332  79916748     5%    var/lib
/var/run        83886080  3969332  79916748     5%    var/run
/var/log        83886080  3969332  79916748     5%    var/log
/home/jail    251658240 41213716 210444524    16%     jail
/tmp              507630    30598    436422     7%    tmp
/dev                   1        1         0   100%    dev
/bin              507630    79532    387488    17%    bin
/proc                  4        4         0   100%    proc

Anyone seen this or has any ideas?

I'm thinking maybe some threshold is reached which makes those points show up (inode free% or something else). But I can't seem to find any info on that in the manpages for df or the handbook.

--
F/X Services
Managed Hosting
http://www.fx-services.com | http://www.fxs.se
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to