Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 2
    Promoting a clone just switches which is considered the parent and which is considered the child. It remains impossible to destroy the snapshot in between because the original parent is now a child of the snapshot, which is now a child of the promoted clone. On top of that, it is still unnecessarily creating dataset-like constructs where I was just looking to replicate files within the dataset. Commented Jun 26, 2012 at 18:05
  • Additionally, on a pool with dedup enabled, I have to disagree with the conclusion on compression slowdown. Copying from a dataset with compression enabled to a dataset with compression enabled, speeds rarely exceeded 5Mb/sec. If one dataset or the other has compression disabled, speeds jump to 10-15Mb/sec on average. With both sides compression disabled, I'm seeing 20Mb/sec easily with spikes higher than that (probably because portions are hitting the dedup table in ram instead of pulling from slower media). Commented Jun 26, 2012 at 18:09
  • 2
    I updated my answer with regard to the cloning. As for compression/encryption/dedup, the slowdowns are more caused by updating the DDT than they are compression or encryption. In my experience the impact of compression and encryption have always been negligible. I guess YMMV. Commented Jun 26, 2012 at 18:43