From owner-freebsd-current  Sun Nov 25 15: 7:30 2001
Delivered-To: freebsd-current@freebsd.org
Received: from noos.fr (r178m112.cybercable.tm.fr [195.132.178.112])
	by hub.freebsd.org (Postfix) with ESMTP id D9BF837B405
	for <current@FreeBSD.org>; Sun, 25 Nov 2001 15:07:23 -0800 (PST)
Received: (from mux@localhost)
	by noos.fr (8.11.6/8.11.4) id fAPN7M307220;
	Mon, 26 Nov 2001 00:07:22 +0100 (CET)
	(envelope-from mux)
Date: Mon, 26 Nov 2001 00:07:22 +0100
From: Maxime Henrion <mux@qualys.com>
To: current@FreeBSD.org
Cc: David Wolfskill <david@catwhisker.org>
Subject: Re: df -l broken
Message-ID: <20011126000722.B280@nebula.noos.fr>
References: <200111252141.fAPLf1639599@trantor.xs4all.nl> <200111252256.fAPMubV20382@bunrab.catwhisker.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200111252256.fAPMubV20382@bunrab.catwhisker.org>
User-Agent: Mutt/1.3.23i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

David Wolfskill wrote:
> >Date: Sun, 25 Nov 2001 22:41:01 +0100
> >From: Paul van der Zwan <paulz@trantor.xs4all.nl>
> 
> >I noticed the -l option of the df command is broken....
> 
> That differs from my experience:
> 
> d141[1] df -l
> Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
> /dev/ad0s3a    158783    93919    52162    64%    /
> devfs               1        1        0   100%    /dev
> /dev/ad0s1a    158767    65260    80806    45%    /S1
> /dev/ad0s1e   1871095  1059572   661836    62%    /S1/usr
> /dev/ad0s2a    158767   103945    42121    71%    /S2
> /dev/ad0s2e   1871095   804588   916820    47%    /S2/usr
> /dev/ad0s3e   1870751  1172006   549085    68%    /usr
> /dev/ad0s3g   1016303    58597   876402     6%    /var
> /dev/ad0s3h  10277074  5916668  3538241    63%    /common
> procfs              4        4        0   100%    /proc
> /dev/md10c     520140       24   478508     0%    /tmp
[...]

If my patch is exact, then the bug should manifest itself only if there
are no network filesystems mounted.  Do you have any network fs mounted
on your box ?

Thanks,
Maxime Henrion
-- 
Don't be fooled by cheap finnish imitations ; BSD is the One True Code

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message