Date: Tue, 3 Mar 2009 16:48:11 +0100 From: Stefan Bethke <stb@lassitu.de> To: Peter Schuller <peter.schuller@infidyne.com> Cc: Randy Bush <randy@psg.com>, freebsd-fs@freebsd.org Subject: Re: .zfs/snapshot: Bad file descriptor Message-ID: <307EA4FE-5053-4D8F-B45F-6711FCDCF467@lassitu.de> In-Reply-To: <20090303145814.GB76327@hyperion.scode.org> References: <m2hc2bb8q0.wl%randy@psg.com> <59adc1a0903022207s34028ed4n8d93c935da47b14b@mail.gmail.com> <m23advas98.wl%randy@psg.com> <59adc1a0903030116o60af7d86v60aee1c2e22cc6e1@mail.gmail.com> <20090303145814.GB76327@hyperion.scode.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 -- Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?307EA4FE-5053-4D8F-B45F-6711FCDCF467>