Yep. Dedup is on. A zpool list shows a 1.50x dedup ratio. I was imagining that the large ratio was tied to that particular snapshot.
basie@/root# zpool list pool1 NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT pool1 2.72T 1.55T 1.17T 57% 1.50x ONLINE - So, it is possible to turn dedup off? More importantly, what happens when I try? Thanks -- John On May 15, 2010, at 3:40 PM, Ian Collins wrote: > On 05/16/10 06:52 AM, John Balestrini wrote: >> 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): >> >> > Is dedup enabled on that pool? > > -- > Ian. > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
