`<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Dec 21, 2013 at 3:15 PM, Tobias Oetiker <span dir="ltr"><<a href="mailto:tobi@oetiker.ch" target="_blank">tobi@oetiker.ch</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">a) would it be faster to send/receive the content of the<br>
deduplicated filesystem to a new non deduplicated<br>
and then destroy the entire filesystem (not the pool).<br>
<br></blockquote><div><br></div><div>Destroying the entire dataset directly won't help, if anything, it'll just prolong the agony. If you want a controlled 'deletion', you can zero the current version of it (delete files individually and whatnot), then revert to the previous snapshot, repeat until there are no snapshots. </div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
b) is there a way to monitor progress on the background<br>
destruction?<br>
<br></blockquote><div><br></div><div>zpool get freeing pool will list how much is left. </div></div><div><br></div>-- <br>George-Cristian Bîrzan
</div></div>
`