On 01/27/10 04:39 AM, erik.ableson wrote:
On 27 janv. 2010, at 12:10, Georg S. Duck wrote:
Hi,
I was suffering for weeks from the following problem:
a zfs dataset contained an automatic snapshot (monthly) that used 2.8 TB of
data. The dataset was deprecated, so I chose to destroy it after I had deleted
some files; eventually it was completely blank besides the snapshot that still
locked 2.8 TB on the pool.
'zfs destroy -r pool/dataset'
hung the machine within seconds to be completely unresponsive. No respective
messages could be found in logs. The issue was reproducible.
The same happened for
'zfs destroy pool/data...@snapshot'
Thus, the conclusion was that the snapshot was indeed the problem.
For info, I have exactly the same situation here with a snapshot that cannot be
deleted that results in the same symptoms. Total freeze, even on the console.
Server responds to pings, but that's it. All iSCSI, NFS and ssh connections are
cut. Currently running b130.
I'll try the workaround once I get some spare space to migrate the contents.
Erik
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
This sounds like yet another instance of
6910767 deleting large holey objects hangs other I/Os
I have a module based on 130 that includes this fix if you would like to try it.
-tim
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
