Date: Tue, 4 Jan 2005 02:35:52 +0100 From: Erik Trulsson <ertr1013@student.uu.se> To: Gregor Mosheh <stigmata_blackangel@yahoo.com> Cc: freebsd-questions@freebsd.org Subject: Re: 4.8 - / out of space Message-ID: <20050104013552.GA15852@falcon.midgard.homeip.net> In-Reply-To: <20050104010723.34785.qmail@web53801.mail.yahoo.com> References: <AF4C045F-5DE6-11D9-AFE0-000393BB56F2@HiWAAY.net> <20050104010723.34785.qmail@web53801.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 03, 2005 at 05:07:23PM -0800, Gregor Mosheh wrote: > --- David Kelly <dkelly@HiWAAY.net> wrote: > > > Another goof is for root to "write" to an unmounted > > filesystem. Later > > when the filesystem is mounted the written files are > > hidden yet still > > consume space on the fs containing the mount point > > (usually /). > > > Could you explain how this happens (or point me to a > doc)? Do you mean something like "tar cvf > /dev/ad0s1a"? > > Does that cause fs corruption? Would fsck reclaim that > space? > He probably means something like the following: Assume that /tmp exists as a separate filesystem. With /tmp unmounted create a lot of files in the /tmp directory (those file end up on the root filesystem) Mount /tmp. Now the files that were previously created in /tmp are shadowed by the /tmp partition and not seen be ls or du. They do still use space on / though. -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050104013552.GA15852>