Howdy All, I've a bit of a strange problem here. I have a filesystem with one snapshot that simply refuses to be destroyed. The snapshots just prior to it and just after it were destroyed without problem. While running the zfs destroy command on this particular snapshot, the server becomes more-or-less hung. It's pingable but will not open a new shell (local or via ssh) however existing shells will occasionally provide some interaction, but at an obscenely slow rate, if at all. Also, since this snapshot is unusually large in size so I've allowed the server to chew on it over night without success.
It set up as a 3-disk raidz configuration. Here's a abbreviated listing of it (the pool1/st...@20100421.0800 snapshot is the one that is misbehaving): ba...@~$ zfs list -t filesystem,snapshot -r pool1/Staff NAME USED AVAIL REFER MOUNTPOINT pool1/Staff 741G 760G 44.6K /export/Staff pool1/st...@20100421.0800 366G - 366G - pool1/st...@zfs-auto-snap:daily-2010-05-02-21:57 0 - 44.6K - pool1/st...@zfs-auto-snap:monthly-2010-05-02-21:58 0 - 44.6K - pool1/st...@zfs-auto-snap:daily-2010-05-03-00:00 0 - 44.6K - . . (Lines Removed) . pool1/st...@archive_1.20100514.2218 0 - 44.6K - pool1/st...@zfs-auto-snap:daily-2010-05-15-00:00 0 - 44.6K - Has anyone seen this type of problem? Any ideas? Thanks, -- John _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
