Date: Tue, 8 May 2007 11:40:57 -0500 From: "illoai@gmail.com" <illoai@gmail.com> To: "Peter Jeremy" <peterjeremy@optushome.com.au> Cc: freebsd-stable@freebsd.org, Hanatsu Tori <hanatsu.tori@gmail.com> Subject: Re: Incorrect df -k output?? Message-ID: <d7195cff0705080940g65df9f92n50d694caaf80e683@mail.gmail.com> In-Reply-To: <20070508103852.GE838@turion.vk2pj.dyndns.org> References: <68517de70705080204i144ad5e5m39eaafee823805f3@mail.gmail.com> <20070508103852.GE838@turion.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 08/05/07, Peter Jeremy <peterjeremy@optushome.com.au> wrote: > On 2007-May-08 13:04:55 +0400, Hanatsu Tori <hanatsu.tori@gmail.com> wrote: > >xxxxx# df -k > >Filesystem 1K-blocks Used Avail Capacity Mounted on > >/dev/ad4s1a 76866422 51507978 19209132 73% / > >devfs 1 1 0 100% /dev > >*/dev/ad6s1d 77879478 75006042 -3356922 105% /usr/home/ftp/pub/ARCHIEVE* > > > > > >xxxxx# du -sk /usr/home/ftp/pub/ARCHIEVE > >*75006042 /usr/home/ftp/pub/ARCHIEVE* > > df reports 75006042KB used and du reports 75006042KB used. Where is > the problem? > > >xxxxx# df -h > >Filesystem Size Used Avail Capacity Mounted on > >/dev/ad0s1a 496M 36M 420M 8% / > >devfs 1.0K 1.0K 0B 100% /dev > >/dev/ad0s1d 1.9G 425M 1.4G 23% /tmp > >/dev/ad0s1f 136G 70G 55G 56% /usr > >*/dev/ad0s1e 3.9G 3.6G -21M 101% /var > >*/dev/ad2s1d 144G 25G 108G 19% /hd2 > >procfs 4.0K 4.0K 0B 100% /proc > > > >xxxxx# du -sh /var > >*202M /var* > > This is a bit less obvious - there does appear 3.4GB missing. UFS witholds a certain amount of space. See man 8 tunefs for details. You can, of course, tunefs -m 0, which will slow down writes quite enough. There was a thread some time back (last year? two years ago?) where a well intentioned fellow rather verbosely (at least with regard to this mailing list) went through the entire process of trying to get those last few blocks available. As i recall, in the end he concluded that the naysayers were in fact correct. Your "missing" blocks are necessary for filesystem performance and the overage above (which itself probably well diagnosed in other messages) while obviously not fatal to your system was likely dragging performance down fairly significantly, at least on that filesystem. -- --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d7195cff0705080940g65df9f92n50d694caaf80e683>