Date: Thu, 11 Mar 2004 10:03:59 +1100 From: Gregory Bond <gnb@itga.com.au> To: Mark Sergeant <msergeant@snsonline.net> Cc: Manfred Lotz <manfred.lotz@web.de> Subject: Re: unexpected softupdate inconsistency Message-ID: <200403102303.KAA12747@lightning.itga.com.au> In-Reply-To: Your message of Wed, 10 Mar 2004 19:21:30 %2B1000.
next in thread | raw e-mail | index | archive | help
msergeant@snsonline.net said:
> In situations like this it can be useful to use vim on the dir entry
> that is affected and remove the invalid filenames. This has worked for
> me before.
I'm astounded.
Directories are not supposed to be modifiable by user-space processes at all,
only with link/unlink/creat/etc system calls, because the risk of filesystem
corruption is huge. What does vim do here that rm doesn't? And how does it get
around the "cant write(2) directories" ban?
See man open:
[EISDIR] The named file is a directory, and the arguments spec-
ify it is to be opened for writing.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403102303.KAA12747>