Date: Tue, 23 Aug 2005 19:48:56 +0100 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: Garrett Cooper <youshi10@u.washington.edu> Cc: freebsd-questions@freebsd.org Subject: Re: what is stuck here?! Message-ID: <430B6F98.3090103@dial.pipex.com> In-Reply-To: <4BD07DF6-78CD-489E-B1CA-4133D12A9126@u.washington.edu> References: <20050823104057.A7FCA4BEAD@ws1-1.us4.outblaze.com> <20050823083301.B20562@shared10.hosting.flyingcroc.net> <4BD07DF6-78CD-489E-B1CA-4133D12A9126@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Garrett Cooper wrote: > On Tue, 23 Aug 2005, Fafa Hafiz Krantz wrote: > >>> how come *nothing* happens when i rm -rf directory/? >>> it just won't move ... >>> >>> top from another terminal tells me: >>> 55272 root 116 0 14396K 13768K RUN 0:27 36.13% 35.40% rm >>> >>> what? the directory/ only contains a .maildir/, a .muttrc and an >>> empty directory >>> it's not an immutable flag that has been set, >>> chflags -R nouchg directory/ stands equally still to rm -rf >>> >> >> hello! >> >> Do you have any open filehandles as well in that directory? I >> could see this as being a problem if a program is keeping one or >> more files open in a directory and in fact the program is blocking >> rm -rf from completing its task. However, I've never seen Unix do >> this before; this would instead be a problem inherent of Windows. > > -Garrett > BSD has never done that. You can safely remove open files and the reference in the filesystem will disappear, but the underlying blocks won't disappear until the last open file reference has been closed i.e. the programs accessing the file continue working. --Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?430B6F98.3090103>