NetBSD Problem Report #621

From gnats  Thu Dec  8 15:58:05 1994
Received: from pain.lcs.mit.edu (pain.lcs.mit.edu [128.52.46.239]) by sun-lamp.cs.berkeley.edu (8.6.9/8.6.9) with ESMTP id PAA22771 for <gnats-bugs@sun-lamp.cs.berkeley.edu>; Thu, 8 Dec 1994 15:58:04 -0800
Message-Id: <199412082328.XAA00715@allegory>
Date: Thu, 8 Dec 1994 23:28:41 GMT
From: Bob Kemp <rsk@allegory.demon.co.uk>
Reply-To: rsk@allegory.demon.co.uk
To: gnats-bugs@netbsd.org
Subject: False errors from FFS operations
X-Send-Pr-Version: 3.2

>Number:         621
>Category:       kern
>Synopsis:       False errors from FFS operations
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Dec 08 16:05:02 +0000 1994
>Closed-Date:    Tue Dec 27 20:37:20 +0000 1994
>Last-Modified:  
>Originator:     Bob Kemp
>Release:        1.0
>Organization:
Bob Kemp		rsk@allegory.demon.co.uk
>Environment:
System: NetBSD allegory 1.0 NetBSD 1.0 (ALLEGORY) #0: Fri Dec 9 03:18:13 GMT 1994 root@allegory:/users/sys/compile/ALLEGORY i386


>Description:

	% mkdir testit
	% cd testit
	% mkdir x x/z y z z/a
	% mv x/z .
	mv: rename x/z to ./z: Directory not empty
	% mv x/z y
	mv: rename x/z to y/z: Invalid argument

	The first error (not empty) is correct but the second is not.
	The directory y has just been created and is empty, so there is
	no reason for the rename to fail.  Attempting to rename x/z to
	x/zz also fails.  Previously, leaving it alone for a while seemed
	to "fix" it but I can't repeat that now (impatience?).

	I know little about the kernel level but could it be that the
	inode for x/z is not unlocked after the original error?

	It makes no difference whether the filesystem is level 0 or level 2.

>How-To-Repeat:
	see description


>Fix:
	The first rename erroneously leaves the IN_RENAME flag set, causing
	the second rename to fail.  Waiting long enough should cause the
	inode to eventually be rotated out.  Next time it's referenced, the
	temporary flags will be reset, so the problem will appear to go
	away.  The proper solution is to force IN_RENAME clear when a
	rename of a directory fails.  - mycroft

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: mycroft 
State-Changed-When: Tue Dec 27 12:37:20 PST 1994 
State-Changed-Why:  
Fixed. 
>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.