From owner-freebsd-fs@FreeBSD.ORG Sun Feb 12 11:56:29 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 8093A106564A for ; Sun, 12 Feb 2012 11:56:29 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from mo-p05-ob6.rzone.de (mo-p05-ob6.rzone.de [IPv6:2a01:238:20a:202:53f5::1]) by mx1.freebsd.org (Postfix) with ESMTP id DEB9C8FC19 for ; Sun, 12 Feb 2012 11:56:28 +0000 (UTC) X-RZG-AUTH: :LWIKdA2leu0bPbLmhzXgqn0MTG6qiKEwQRWfNxSw4HzYIwjsnvdDt2oX8drk23mtcWl82a4= X-RZG-CLASS-ID: mo05 Received: from [192.168.179.39] (hmbg-5f761430.pool.mediaWays.net [95.118.20.48]) by smtp.strato.de (fruni mo21) (RZmta 27.6 DYNA|AUTH) with (DHE-RSA-AES128-SHA encrypted) ESMTPA id 603b2fo1CBgKmj for ; Sun, 12 Feb 2012 12:56:26 +0100 (MET) Message-ID: <4F37A8E7.7060102@brockmann-consult.de> Date: Sun, 12 Feb 2012 12:56:23 +0100 From: Peter Maloney User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0) Gecko/20120129 Thunderbird/10.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4F377457.4080807@FreeBSD.org> <20120212084052.GA43095@icarus.home.lan> <4F3789C1.9000903@FreeBSD.org> In-Reply-To: <4F3789C1.9000903@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: ZFS Snapshot problems 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, 12 Feb 2012 11:56:29 -0000 I had a problem where I could not delete, rename, send, etc. a snapshot... , (possibly caused by a kernel panic during a zfs replication). Maybe yours is related. I did not try viewing the contents of my snapshot. If it is related, the solution is: zdb -d poolname | grep % Expect the command to take long, and output should include all your clones you made, plus some "Input/output errors" for some others. Pay attention to the ones with errors, and then delete those, then try to access your snapshot again. Am 12.02.2012 10:43, schrieb Matthew Seaman: > On 12/02/2012 08:40, Jeremy Chadwick wrote: >> Could this be related (somehow) to the below commit? I'm doubting it, >> but... >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/cddl/contrib/opensolaris/cmd/zfs/zfs_main.c > No -- I was seeing the problem on a system compiled before then. This > didn't start in close proximity to doing an upgrade. There was at least > a two week delay. Now, I did try updating to see if that fixed the > trouble, but no joy. > >> I realise you're not destroying a snapshot, but I wonder if an old >> snapshot which was previously destroyed wasn't really destroyed, thus >> resulting in the behaviour you see. As stated, I doubt it, but I >> imagine it depends on how this issue manifests itself. > Actually, I do destroy the snapshots, which works just fine. I tend to > have either 0 or 1 snapshots at any one time. > > Cheers > > Matthew >