K Richard Pixley <rpixley@xxxxxxxxxxxxxxxxxxx> writes:
> But as a user level facility, I want to be able to snapshot before
> making a change to a tree full of source code and (re)building it all
> over again. I may want to keep my new build, but I may want to flush
> it and return to known good state.
You may want to check out cp --reflink=always (different from cp
--link), which creates copy-on-write copy of the data. It isn't quite as
fast as snapshots to create, but it's still plenty fast and without the
downsides of subvolumes.
--
_____________________________________________________________________
/ __// /__ ____ __ http://www.modeemi.fi/~flux/\ \
/ /_ / // // /\ \/ / \ /
/_/ /_/ \___/ /_/\_\@modeemi.fi \/
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
