From owner-freebsd-questions@FreeBSD.ORG Wed Jul 18 09:36:12 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E1B2716A401 for ; Wed, 18 Jul 2007 09:36:12 +0000 (UTC) (envelope-from viper@fx-services.com) Received: from mamata.fx-services.com (mamata.fx-services.com [217.25.36.100]) by mx1.freebsd.org (Postfix) with ESMTP id 7FD4F13C4B5 for ; Wed, 18 Jul 2007 09:36:12 +0000 (UTC) (envelope-from viper@fx-services.com) Received: from static-213-115-136-12.sme.bredbandsbolaget.se ([213.115.136.12] helo=[10.2.1.78]) by mamata.fx-services.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67 (FreeBSD)) (envelope-from ) id 1IB5NL-000Key-K9 for freebsd-questions@freebsd.org; Wed, 18 Jul 2007 10:59:17 +0200 Message-ID: <469DD664.3000808@fx-services.com> Date: Wed, 18 Jul 2007 10:59:16 +0200 From: Robin Vleij User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Mail is Virus Free, FXS MailGateway X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mamata.fx-services.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [26 6] / [26 6] X-AntiAbuse: Sender Address Domain - fx-services.com X-Source: X-Source-Args: X-Source-Dir: Subject: Strange df output, including non-mounts X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jul 2007 09:36:13 -0000 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