.zfs/snapshot: Bad file descriptor
stb at lassitu.de
Tue Mar 3 07:48:15 PST 2009
Am 03.03.2009 um 15:58 schrieb Peter Schuller:
>> well, I have no idea. This issue persists for me over 1.5 years.
>> If you want file a PR with all the stuff. I've mailed couple of times
>> this list with pjd in copy, to no avail.
> Sorry if I'm missing something, but why is this even expected to work?
> If you don't want the .zfs directories, should you not turn off its
> use by setting the appropriate option on the fs?
> What is the expected result of rm -rf:ing the .zfs directory?
No idea (I personally would expect a permission denied or similar,
since it's a virtual dir), but the main issue is that snapshot is no
longer accessible. Trying to ls .zfs you usually get the same error
message Randy posted; cf. my thread here on -fs and on -current from a
couple weeks back.
Interestingly enough, there doesn't seem to be a PR yet, or at least I
can't find it.
My guess is that the automounting code is getting confused sometimes,
and nixes some part of the snapshot vnode while unmounting a snapshot.
This in turn leads to a panic on unmounting the containg ZFS.
Stefan Bethke <stb at lassitu.de> Fon +49 151 14070811
More information about the freebsd-fs