Finally, it's been destroyed! Last night I turned dedup off and sent the destroy command and simply let it run over night. Also, I let zpool iostat 30 run as well. It showed no activity for the first 6-1/2 hours and then a flurry of activity for 13-minutes. That snapshot is finally gone and the system seems to be behaving now.
Thanks for all your help! John On May 16, 2010, at 2:46 AM, Roy Sigurd Karlsbakk wrote: > ----- "Roy Sigurd Karlsbakk" <r...@karlsbakk.net> skrev: > >> ----- "John Balestrini" <j...@balestrini.net> skrev: >> >>> 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? >> >> # zfs set dedup=off pool1 >> >> This will not dedup your data, though, unless you do something like >> copying all the files again, since dedup is done on write. Some seems >> to be fixed in 135, and it was said here on the list that all known >> bugs should be fixed before the next release (see my thread 'dedup >> status') > > I meant, this will not de-dedup the deduped data... > > roy > -- > Roy Sigurd Karlsbakk > (+47) 97542685 > r...@karlsbakk.net > http://blogg.karlsbakk.net/ > -- > I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det > er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av > idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og > relevante synonymer på norsk. > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
