From owner-freebsd-fs@FreeBSD.ORG Tue Mar 3 15:48:14 2009 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E290F10656E7 for ; Tue, 3 Mar 2009 15:48:14 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.freebsd.org (Postfix) with ESMTP id 7B9218FC20 for ; Tue, 3 Mar 2009 15:48:14 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from localhost by koef.zs64.net (8.14.3/8.14.3) with ESMTP id n23FmBFg082166 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 3 Mar 2009 16:48:12 +0100 (CET) (envelope-from stb@lassitu.de) (authenticated as stb) Message-Id: <307EA4FE-5053-4D8F-B45F-6711FCDCF467@lassitu.de> From: Stefan Bethke To: Peter Schuller In-Reply-To: <20090303145814.GB76327@hyperion.scode.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Tue, 3 Mar 2009 16:48:11 +0100 References: <59adc1a0903022207s34028ed4n8d93c935da47b14b@mail.gmail.com> <59adc1a0903030116o60af7d86v60aee1c2e22cc6e1@mail.gmail.com> <20090303145814.GB76327@hyperion.scode.org> X-Mailer: Apple Mail (2.930.3) Cc: Randy Bush , freebsd-fs@freebsd.org Subject: Re: .zfs/snapshot: Bad file descriptor X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Mar 2009 15:48:15 -0000 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 Fon +49 151 14070811