ZFS Snapshot problems
Peter Maloney
peter.maloney at brockmann-consult.de
Sun Feb 12 11:56:29 UTC 2012
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
>
More information about the freebsd-fs
mailing list