Date: Fri, 01 Oct 2010 08:15:13 +1000 From: Danny Carroll <fbsd@dannysplace.net> To: freebsd-fs@freebsd.org Subject: Re: Fwd: Strange ZFS problem, filesystem claims to be full when clearly not full Message-ID: <4CA50BF1.60503@dannysplace.net> In-Reply-To: <AANLkTimsSpP4nCE18H%2BQJCS1iKqw-wmoUdCc1OdU1tM2@mail.gmail.com> References: <4CA45444.6070002@dannysplace.net> <201009301438.o8UEckoY019473@lurza.secnetix.de> <20100930144845.GA19926@icarus.home.lan> <4CA4B12B.7050307@icyb.net.ua> <AANLkTinHoxX4MfVCEB2rrdcS1ubwQp%2Bc37uP2BcP2Crm@mail.gmail.com> <AANLkTimsSpP4nCE18H%2BQJCS1iKqw-wmoUdCc1OdU1tM2@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/10/2010 3:08 AM, Torbjorn Kristoffersen wrote: > > If the process causing this is gone, or is working correctly (seeing > that the fs is no longer growing, I hope), > can dead unlinked files still remain, is there a way to purge them? I can't remember exactly what happens and it's probably different for each flavour of unix and *nux. If a file is deleted, then the directory entry for the inode is de-linked. If it's the last link to that inode then usually that inode is freed. But when a process holds a handle to a file when it's deleted, then the reclaim does not happen AFAIK until *after* the file handle is closed. <speculation> I wonder what happens when, if a file handle is opened for writing, someone else comes along and truncates the file. Perhaps a the seek position of the open handle is reset to 0, or perhaps (not likely) a write operation after truncation would result in an error. </speculation> -D
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CA50BF1.60503>