From owner-freebsd-stable@FreeBSD.ORG  Wed Mar 10 15:04:06 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 12F4216A4CE
	for <freebsd-stable@freebsd.org>;
	Wed, 10 Mar 2004 15:04:06 -0800 (PST)
Received: from ns1.itga.com.au (ns1.itga.com.au [202.53.40.214])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B81EB43D3F
	for <freebsd-stable@freebsd.org>;
	Wed, 10 Mar 2004 15:04:04 -0800 (PST)	(envelope-from gnb@itga.com.au)
Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20])
	by ns1.itga.com.au (8.12.9/8.12.9) with ESMTP id i2AN41R5034189;
	Thu, 11 Mar 2004 10:04:01 +1100 (EST)
	(envelope-from gnb@itga.com.au)
Received: from lightning.itga.com.au (localhost [127.0.0.1])
	by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id KAA12747;
	Thu, 11 Mar 2004 10:03:59 +1100 (EST)
Message-Id: <200403102303.KAA12747@lightning.itga.com.au>
X-Mailer: exmh version 2.4 05/15/2001 with nmh-1.0.4
From: Gregory Bond <gnb@itga.com.au>
To: Mark Sergeant <msergeant@snsonline.net>
In-reply-to: Your message of Wed, 10 Mar 2004 19:21:30 +1000.
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 11 Mar 2004 10:03:59 +1100
Sender: gnb@itga.com.au
cc: freebsd-stable@freebsd.org
cc: Manfred Lotz <manfred.lotz@web.de>
Subject: Re: unexpected softupdate inconsistency 
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Mar 2004 23:04:06 -0000


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.