Bug #3339
closedmkdir, touch, rm occasionally do not work as expected
0%
Description
Systems affected:
- 6.3-DEVELOPMENT DragonFly v6.3.0.77.gfe8a9-DEVELOPMENT #4: Mon Mar 14 13:55:50 EET 2022
- 6.5-DEVELOPMENT DragonFly v6.5.0.25.ge49cd-DEVELOPMENT #63: Wed Feb 1 08:24:51 EET 2023
How to reproduce:
- Difficult and indeterministic: sometimes occurs, sometimes not
Problem description:
- mkdir reports the directory exists although it did not. The following command line sequences demonstrate the problem for mkdir. These sequences are un-edited, i.e. no other commands have been issued inbetween.
--- /bin/tcsh ---
user@qcomp:~ % ls -ld somedir
drwxr-xr-x 1 user user 0 Feb 4 09:43 somedir
user@qcomp:~ % rm -rf somedir
recursively remove somedir? y
user@qcomp:~ % ls -ld somedir
ls: somedir: No such file or directory
user@qcomp:~ % mkdir somedir
mkdir: somedir: File exists
user@qcomp:~ % ls -ld somedir
drwxr-xr-x 1 user user 0 Feb 4 09:44 somedir
user@qcomp:~ %
- touch and rm: similarly, touch sometimes does not seem to work.
It seems clear that 'sixfile' did not exist for rm or ls.
For 'twofile', at first it seems to work ok. But then note again later: after L7, 'twofile' should not exist any more, yet it shows up below in 'ls l'. Note the 'twofile' time has changed (9:53 -> 9:57).
--- /bin/sh ---
$ rm twofile
$ ls l twofile 1 user user 0 Feb 4 09:53 twofile
ls: twofile: No such file or directory
$ touch twofile
$ ls -l twofile
-rw-r--r-
$ rm twofile
$
$ touch sixfile
$ rm sixfile
rm: sixfile: No such file or directory
$ ls l sixfile 1 user user 0 Feb 4 09:57 twofile
ls: sixfile: No such file or directory
$ ls -l six*
ls: six*: No such file or directory
$ ls -l
total 316
-rw-r--r-
$ rm twofile
rm: twofile: No such file or directory
$ ls -l twofile
ls: twofile: No such file or directory
$ ls -l
. . . NO twofile here. . .