From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 13 Jan 2012 15:08:34 +0100 From: tlaronde@polynum.com To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20120113140834.GA849@polynum.com> References: <20120113113026.GA419@polynum.com> <20120113133836.GA484@polynum.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Subject: Re: [9fans] fossil pb: FOUND! Topicbox-Message-UUID: 5a2510f4-ead7-11e9-9d60-3106f5b1d025 On Fri, Jan 13, 2012 at 08:59:32AM -0500, erik quanstrom wrote: > > But the surprise is that it was _not_ hidden. It _was_ here under /dist > > ... but apparently not added to the summary made by du(1)? Does du(1) > > "know" that some dir are mount point taking (normally) no real space, > > and skipping them? Because this means one can add whatever files in > > there and fill fossil with du(1) ignoring all... > > > > On a side note, the print from du(1) is not accurate with the "-h" flag: > > > > term% du -sh / > > 347.8285G / > > > > I have megabytes, not gigabytes. > > i think your / has mounts and binds that are confusing du. you > need to remount your root file system someplace free of mounts > or binds on top, e.g.: > > ; mount /srv/boot /n/boot; cd /n/boot > ; du -s .>[2=] > 4049232 . > ; du -sh .>[2=] > 3.861649G . > ; hoc > 4049232 / 1024 / 1024 > 3.86164855957 Do you spot only the 347.8285G? or altogether the /dist/plan9.iso that was not seen? Because, for the gigabytes, it is just a format error, since without the option it reports correctly 350Mb. Since your test is with gigabytes, the G suffix is correct. But it may be simply (I didn't look at the source) that for Megabytes, it prints a G suffix too... -- Thierry Laronde http://www.kergis.com/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C