From: CACook@quantum-sci.com
To: linux-btrfs@vger.kernel.org
Subject: Re: How Snapshots Inter-relate?
Date: Fri, 22 Apr 2011 08:03:20 -0700 [thread overview]
Message-ID: <201104220803.20552.CACook@quantum-sci.com> (raw)
In-Reply-To: <1303411647.25281.2.camel@ayu>
On Thursday 21 April, 2011 11:47:25 Calvin Walton wrote:
> You have nothing to worry about. You can delete any snapshot on btrfs
> without losing data from any other snapshot. Each snapshot is completely
> independent.
>
> This works because data which is shared between multiple snapshots is
> reference counted, and won't be deleted until you remove the last
> snapshot that references that data.
Wow. Awesome job, BTRFS team.
Would it be good practice to say, once a year, do a completely new fresh snapshot?
next prev parent reply other threads:[~2011-04-22 15:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 17:17 How Snapshots Inter-relate? CACook
2011-04-21 18:47 ` Calvin Walton
2011-04-22 15:03 ` CACook [this message]
2011-04-22 15:30 ` Fajar A. Nugraha
2011-04-22 15:39 ` Helmut Hullen
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=201104220803.20552.CACook@quantum-sci.com \
--to=cacook@quantum-sci.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).