On 06/05/2015 18:50, Matthew Ahrens wrote: > After many years, I finally have a potential use case for this, so I'd like to > keep it in. I was thinking of proposing this project at a future hackathon > (This year's OpenZFS DevSummit? Look for an announcement coming soon :-) To > summarize: > > To minimize space used by metadata, and to increase performance, we could > implement "zfs clone --nopromote". Clones created this way would not be > promotable (i.e. "zfs promote <clone>" would give an error). > > In return, the DSL would not need to track (in the deadlists) blocks that were > born before the origin.
Sounds cool! Thanks for the heads-up. > On Wed, May 6, 2015 at 5:27 AM, Andriy Gapon <[email protected] > <mailto:[email protected]>> wrote: > > > DS_FLAG_NOPROMOTE seems to be a read-only flag. That is, it's checked in > two > places, but it is never set. > Is this some left-over that can be cleaned up? > > -- > Andriy Gapon > _______________________________________________ > developer mailing list > [email protected] <mailto:[email protected]> > http://lists.open-zfs.org/mailman/listinfo/developer > > -- Andriy Gapon _______________________________________________ developer mailing list [email protected] http://lists.open-zfs.org/mailman/listinfo/developer
