From owner-freebsd-fs@FreeBSD.ORG Sun Jun 10 07:00:43 2012 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 67AAD106564A for ; Sun, 10 Jun 2012 07:00:43 +0000 (UTC) (envelope-from patpro@patpro.net) Received: from rack.patpro.net (rack.patpro.net [193.30.227.216]) by mx1.freebsd.org (Postfix) with ESMTP id F1FA78FC16 for ; Sun, 10 Jun 2012 07:00:42 +0000 (UTC) Received: from rack.patpro.net (localhost [127.0.0.1]) by rack.patpro.net (Postfix) with ESMTP id 4C52C1CC020 for ; Sun, 10 Jun 2012 08:53:11 +0200 (CEST) X-Virus-Scanned: amavisd-new at patpro.net Received: from amavis-at-patpro.net ([127.0.0.1]) by rack.patpro.net (rack.patpro.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YK_ncZEK3hmP for ; Sun, 10 Jun 2012 08:53:09 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by rack.patpro.net (Postfix) with ESMTP for ; Sun, 10 Jun 2012 08:53:09 +0200 (CEST) From: Patrick Proniewski Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Sun, 10 Jun 2012 08:53:08 +0200 Message-Id: <9A54A14B-7DA4-48AD-8198-63A8572D3DB3@patpro.net> To: freebsd-fs@freebsd.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [zfs] need help with a bug (PR 156781) 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: Sun, 10 Jun 2012 07:00:43 -0000 Hello, I'm running various FreeBSD 8 amd64 servers, and some of them use ZFS = extensively. Unfortunately, I'm hit by the bug "PR 156781" = (). After an undetermined uptime, the affected server will lose the ability = to list some of its .zfs/.snappshot: ls -l .zfs ls: snapshot: Bad file descriptor It doesn't look critical at this point, because snapshots still work = (creation/deletion), but you won't be able to access them via cd = .zfs/snapshot/... In fact, it is critical. If you try to unmount the affected ZFS volume, = your shell will freeze, and you have to reconnect in a new one. And more = importantly, the whole OS will freeze when you issue a reboot, meaning = it will never reboot until someone pushes the power button of the box. It's a very nasty bug when your box is 400 km away in a data center, and = you need to ask your hosting provider to push that button. I would be happy if the PR 156781 could be modified so that it says its = Severity is critical, and it affects both FreeBSD 8.1-RELEASE-p5 amd64, = FreeBSD 8.2-RELEASE-p3 amd64, and FreeBSD 8.2-STABLE sparc64 (ie. not = just FreeBSD 8.2-STABLE sparc64). And I would be very very happy, if someone could fix this bug, it's = unfortunately way out of my reach :/ FreeBSD si 8.2-RELEASE-p3 FreeBSD 8.2-RELEASE-p3 #0: Tue Sep 27 = 18:45:57 UTC 2011 =20 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC = amd64 $ grep ZFS /var/run/dmesg.boot ZFS filesystem version 4 ZFS storage pool version 15 $ zpool upgrade -a This system is currently running ZFS pool version 15. All pools are formatted using this version. $ zfs upgrade -a 0 filesystems upgraded 265 filesystems already at this version and=20 FreeBSD rack.patpro.net 8.1-RELEASE-p5 FreeBSD 8.1-RELEASE-p5 = #0: Tue Sep 27 16:49:00 UTC 2011 =20 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC = amd64 $ grep ZFS /var/run/dmesg.boot=20 ZFS filesystem version 3 ZFS storage pool version 14 $ zpool upgrade -a This system is currently running ZFS pool version 14. All pools are formatted using this version. $ zfs upgrade -ra 0 filesystems upgraded 19 filesystems already at this version regards, patpro (I'm subscribed to the digest, fell free to Cc. me)=