From owner-freebsd-stable@FreeBSD.ORG Mon Mar 21 11:41:38 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CC1B106566B for ; Mon, 21 Mar 2011 11:41:38 +0000 (UTC) (envelope-from O.Seibert@cs.ru.nl) Received: from rustug.science.ru.nl (rustug.science.ru.nl [131.174.16.158]) by mx1.freebsd.org (Postfix) with ESMTP id 04B268FC15 for ; Mon, 21 Mar 2011 11:41:36 +0000 (UTC) Received: from kookpunt.science.ru.nl (kookpunt.science.ru.nl [131.174.30.61]) by rustug.science.ru.nl (8.13.7/5.31) with ESMTP id p2LBNSqY009026 for ; Mon, 21 Mar 2011 12:23:28 +0100 (MET) Received: from twoquid.cs.ru.nl (twoquid.cs.ru.nl [131.174.142.38]) by kookpunt.science.ru.nl (8.13.7/5.31) with ESMTP id p2LBNMAM008839; Mon, 21 Mar 2011 12:23:22 +0100 (MET) Received: by twoquid.cs.ru.nl (Postfix, from userid 4100) id 52EA12E048; Mon, 21 Mar 2011 12:23:22 +0100 (CET) Date: Mon, 21 Mar 2011 12:23:22 +0100 From: Olaf Seibert To: freebsd-stable@freebsd.org Message-ID: <20110321112322.GA6733@twoquid.cs.ru.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.19 (2009-01-05) X-Spam-Score: -1.799 () ALL_TRUSTED,BAYES_50 X-Scanned-By: MIMEDefang 2.63 on 131.174.30.61 Subject: .zfs directory: snapshot: Bad file descriptor X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2011 11:41:38 -0000 On my production system (still 8.1, I haven't had time yet to upgrade to 8.2) I have a ZFS. Nightly I make snapshots of each filesystem in it. Suddenly, one of the file systems has no snapshots any more: $ ls -l /tank/vol-fourquid-1/.zfs ls: snapshot: Bad file descriptor total 0 $ ls -l /tank/vol-fourquid-1/.zfs/snapshot ls: /tank/vol-fourquid-1/.zfs/snapshot: Bad file descriptor Snapshots in other file systems seem ok, for example: $ ls -l /home/local/.zfs total 0 dr-xr-xr-x 9 root wheel 9 Oct 21 2009 snapshot/ $ ls -l /home/local/.zfs/snapshot/ total 32 drwxr-xr-x 48 root vb 48 Apr 19 2010 friday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 monday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 saturday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 sunday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 thursday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 tuesday/ drwxr-xr-x 48 root vb 48 Apr 19 2010 wednesday/ zpool status thinks all is ok: $ zpool status pool: tank state: ONLINE status: The pool is formatted using an older on-disk format. The pool can still be used, but some features are unavailable. action: Upgrade the pool using 'zpool upgrade'. Once this is done, the pool will no longer be accessible on older software versions. scrub: none requested config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 raidz2 ONLINE 0 0 0 da0 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 0 da4 ONLINE 0 0 0 da5 ONLINE 0 0 0 errors: No known data errors How worried should I be about corruption anyway, say if I unmount and remount the affected file system? -Olaf. --