Subject: kern/621: False errors from FFS operations
To: None <gnats-admin@sun-lamp.cs.berkeley.edu>
From: Bob Kemp <rsk@allegory.demon.co.uk>
List: netbsd-bugs
Date: 12/08/1994 16:05:04
>Number: 621
>Category: kern
>Synopsis: False errors from FFS operations
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people (Kernel Bug People)
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Dec 8 16:05:02 1994
>Originator: Bob Kemp
>Organization:
Bob Kemp rsk@allegory.demon.co.uk
>Release: 1.0
>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:
>Audit-Trail:
>Unformatted: