From: Erkki Seppala <flux-btrfs@inside.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: syntax for deleting subvolumes?
Date: Thu, 19 Mar 2015 09:18:29 +0200 [thread overview]
Message-ID: <m49y4mtfoai.fsf@coffee.modeemi.fi> (raw)
In-Reply-To: 550A08AC.7070506@graphitesystems.com
K Richard Pixley <rpixley@graphitesystems.com> 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 \/
next prev parent reply other threads:[~2015-03-19 7:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 20:42 syntax for deleting subvolumes? K Richard Pixley
2015-03-18 21:06 ` Chris Murphy
2015-03-18 21:39 ` K Richard Pixley
2015-03-18 21:55 ` Hugo Mills
2015-03-18 23:01 ` K Richard Pixley
2015-03-18 23:33 ` Chris Murphy
2015-03-19 0:47 ` Jeff Mahoney
2015-03-19 2:55 ` Chris Murphy
2015-03-18 22:15 ` Chris Murphy
2015-03-18 23:22 ` K Richard Pixley
2015-03-18 23:50 ` Chris Murphy
2015-03-19 7:18 ` Erkki Seppala [this message]
2015-03-21 3:20 ` Russell Coker
2015-03-19 19:09 ` Chris Murphy
2015-03-20 4:18 ` Duncan
2015-03-21 3:17 ` Russell Coker
2015-03-18 21:09 ` Hugo Mills
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m49y4mtfoai.fsf@coffee.modeemi.fi \
--to=flux-btrfs@inside.org \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.