zfs error - snapshot: Bad file descriptor

Mike Tancsa mike at sentex.net
Tue Jul 26 20:18:56 UTC 2011


I googled around for an answer to this, but other than reboot, I never found any other strategies.

On my backup server (RELENG_8 from Jun 20th, AMD64 8G of RAM), I have one big pool

# zpool status -v
  pool: zbackup1
 state: ONLINE
 scan: scrub repaired 0 in 11h11m with 0 errors on Mon Jul 25 19:51:11 2011
config:

        NAME        STATE     READ WRITE CKSUM
        zbackup1    ONLINE       0     0     0
          raidz1-0  ONLINE       0     0     0
            ada5    ONLINE       0     0     0
            ada7    ONLINE       0     0     0
            ada4    ONLINE       0     0     0
            ada6    ONLINE       0     0     0
          raidz1-1  ONLINE       0     0     0
            ada0    ONLINE       0     0     0
            ada1    ONLINE       0     0     0
            ada2    ONLINE       0     0     0
            ada3    ONLINE       0     0     0

errors: No known data errors

and a number of file systems


zbackup1                         5241690240 2248788502 2992901738    43%    /zbackup1
zbackup1/archive                 2992901771         33 2992901738     0%    /zbackup1/archive
zbackup1/cust1                   3254254853  261353115 2992901738     8%    /zbackup1/cust1


When I would change to /zbackup1/cust1/.zfs

and do a
ls -l 

# ls -l
ls: snapshot: Bad file descriptor
total 4
dr-xr-xr-x   4 root  wheel  -  4 Mar  4 08:43 .
drwxr-xr-x  21 root  wheel  - 21 Jun 29 11:46 ..
dr-xr-xr-x   2 root  wheel  -  2 Mar  4 08:43 shares


snapshot was set to visible

zbackup1/cust1               snapdir               visible                            inherited from zbackup1

And I could even list them in zfs get all

zbackup1/cust1 at 20110715       type                  snapshot                           -
zbackup1/cust1 at 20110715       creation              Fri Jul 15  8:10 2011              -
zbackup1/cust1 at 20110715       used                  7.41G                              -


But I could never change to the directory and do an ls -l, let along get files


I ran a full scrub, but it did not help.  I did a reboot and all worked after that.  

# ls -l
total 4
dr-xr-xr-x   4 root  wheel  -  4 Mar  4 08:43 .
drwxr-xr-x  21 root  wheel  - 21 Jun 29 11:46 ..
dr-xr-xr-x   2 root  wheel  -  2 Mar  4 08:43 shares
dr-xr-xr-x   5 root  wheel  -  5 Jul 26 12:11 snapshot
# cd snapshot/
# ls -l
total 6
dr-xr-xr-x   5 root  wheel  -  5 Jul 26 12:11 .
dr-xr-xr-x   4 root  wheel  -  4 Mar  4 08:43 ..
drwxr-xr-x  20 root  wheel  - 21 Jun 29 11:46 20110715
drwxr-xr-x  20 root  wheel  - 21 Jun 29 11:46 20110722
drwxr-xr-x  20 root  wheel  - 21 Jun 29 11:46 test


In the future, are there any other things I can do to fix the issue short of rebooting ?

	---Mike



-- 
-------------------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, mike at sentex.net
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada   http://www.tancsa.com/


More information about the freebsd-fs mailing list