From owner-freebsd-questions@FreeBSD.ORG Thu Aug 15 02:43:51 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 65AC51F0 for ; Thu, 15 Aug 2013 02:43:51 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail05.adl6.internode.on.net (ipmail05.adl6.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:6:5]) by mx1.freebsd.org (Postfix) with ESMTP id ECD942C07 for ; Thu, 15 Aug 2013 02:43:48 +0000 (UTC) Received: from ppp247-71.static.internode.on.net (HELO leader.local) ([203.122.247.71]) by ipmail05.adl6.internode.on.net with ESMTP; 15 Aug 2013 12:13:46 +0930 Message-ID: <520C405A.6000408@ShaneWare.Biz> Date: Thu, 15 Aug 2013 12:13:38 +0930 From: Shane Ambler User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130516 Thunderbird/17.0.6 MIME-Version: 1.0 To: dweimer@dweimer.net Subject: Re: ZFS Snapshots Not able to be accessed under .zfs/snapshot/name References: <22a7343f4573d6faac5aec1d7c9a1135@dweimer.net> In-Reply-To: <22a7343f4573d6faac5aec1d7c9a1135@dweimer.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Aug 2013 02:43:51 -0000 On 14/08/2013 22:57, dweimer wrote: > I have a few systems running on ZFS with a backup script that creates > snapshots, then backs up the .zfs/snapshot/name directory to make sure > open files are not missed. This has been working great but all of the > sudden one of my systems has stopped working. It takes the snapshots > fine, zfs list -t spnapshot shows the snapshots, but if you do an ls > command, on the .zfs/snapshot/ directory it returns not a directory. > > part of the zfs list output: > > NAME USED AVAIL REFER MOUNTPOINT > zroot 4.48G 29.7G 31K none > zroot/ROOT 2.92G 29.7G 31K none > zroot/ROOT/91p5-20130812 2.92G 29.7G 2.92G legacy > zroot/home 144K 29.7G 122K /home > > part of the zfs list -t snapshot output: > > NAME USED AVAIL REFER > MOUNTPOINT > zroot/ROOT/91p5-20130812@91p5-20130812--bsnap 340K - 2.92G - > zroot/home@home--bsnap 22K - 122K - > > ls /.zfs/snapshot/91p5-20130812--bsnap/ > Does work at the right now, since the last reboot, but wasn't always > working, this is my boot environment. > > if I do ls /home/.zfs/snapshot/, result is: > ls: /home/.zfs/snapshot/: Not a directory > > if I do ls /home/.zfs, result is: > ls: snapshot: Bad file descriptor > shares > > I have tried zpool scrub zroot, no errors were found, if I reboot the > system I can get one good backup, then I start having problems. Anyone > else ever ran into this, any suggestions as to a fix? > > System is running FreeBSD 9.1-RELEASE-p5 #1 r253764: Mon Jul 29 15:07:35 > CDT 2013, zpool is running version 28, zfs is running version 5 > I can say I've had this problem. Not certain what fixed it. I do remember I decided to stop snapshoting if I couldn't access them and deleted existing snapshots. I later restarted the machine before I went back for another look and they were working. So my guess is a restart without existing snapshots may be the key. Now if only we could find out what started the issue so we can stop it happening again.