Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Mar 2015 15:30:28 -0600
From:      Mattias Lindgren <mlindgren@runelind.net>
To:        freebsd-bugs@freebsd.org
Subject:   Schroedingers files. Both there and not there.
Message-ID:  <3D6E6D4313774D30AE2F4C7BB7AC2156@runelind.net>

next in thread | raw e-mail | index | archive | help
I=E2=80=99ve been having some issues over the past few months that I=E2=80=
=99m finally getting around to troubleshooting. I=E2=80=99m running =46re=
eBSD 10.1-p5 with Z=46S.  My nightly emails have been giving me output li=
ke:

Checking setuid files and devices:
find: /usr/include/dev/an=5Fbak/if=5Faironet=5Fieee.h: No such file or di=
rectory

Checking negative group permissions:
find: /usr/include/dev/an=5Fbak/if=5Faironet=5Fieee.h: No such file or di=
rectory
The reason for it being called an=5Fbak is that the original file used to=
 have the same errors, so I moved that directory and extracted a known go=
od version of if=5Faironet=5Fieee.h. However now I=E2=80=99d just like to=
 clean out the bad file. =20
If I do an rm -rf on the file, it kicks me back to the command prompt lik=
e everything worked successfully, however if I ls that directory, it stil=
l shows up:
=24 ls /usr/include/dev/an=5Fbak/ if=5Faironet=5Fieee.h =24 sudo rm -rf /=
usr/include/dev/an=5Fbak/if=5Faironet=5Fieee.h =24 ls /usr/include/dev/an=
=5Fbak/ if=5Faironet=5Fieee.h
However, ls -al shows a different output:
=24 ls -al /usr/include/dev/an=5Fbak/ ls: if=5Faironet=5Fieee.h: No such =
file or directory total 17 drwxr-xr-x 2 root wheel 3 Dec 21 20:32 . drwxr=
-xr-x 31 root wheel 31 Mar 16 15:26 ..
I can move the an=5Fbak folder to a different name within the same pool. =
However I cannot move that folder to a different zfs pool. I can not move=
 just the file, either within the same pool or to a different pool.
This is only one of the files that is giving me the problem, the daily ou=
tput also lists a few others, but they all exhibit the same behavior.
I tried sending the zfs dataset to another pool, and it exhibited the sam=
e problem. A scrub has not revealed any issues. =20
Thanks,
Mattias






Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D6E6D4313774D30AE2F4C7BB7AC2156>