From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Subvolumes and isolation
Date: Mon, 14 Apr 2014 11:50:19 +0000 (UTC) [thread overview]
Message-ID: <pan$83f14$2d652951$d4438311$791da6ce@cox.net> (raw)
In-Reply-To: pan.2014.04.14.10.38.45@googlemail.com
Holger Hoffstätte posted on Mon, 14 Apr 2014 10:38:45 +0000 as excerpted:
> So I'm happily using subvolumes and snapshots and was wondering about
> subvolume low-level isolation. Assuming metadata=single, would a corrupt
> metadata block in one subvolume's directory tree affect any other
> subvolumes on the same physical partition, or would the fallout from
> this bad block be contained?
This isn't an authoritative answer, but AFAIK, chunks are /not/ subvolume-
dedicated. In fact, on the wiki, the sysadmin's guide page defines a
snapshot as simply a subvolume that shares its data and metadata with
some other subvolume, using btrfs' COW capabilities. Obviously that
would be rather difficult if subvolumes get dedicated data and metadata
chunks, so...
That is in fact why I prefer entirely separate filesystems instead of
simply subvolumes, and use separate (but identically sized) filesystems
for primary backup as well -- using subvolumes there's only one
filesystem superstructure and if it's damaged... Let's just say I'm not
comfortable with all my data eggs in the same data basket... the one I
might find someday the bottom just dropped out of (particularly since
btrfs isn't fully stable yet)!
Of course the other benefit to multiple small partitions is that scrubs
and balances are that much faster, too! Having a balance or scrub take a
minute or five is considerably different than having it take an hour or
five! =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-04-14 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 10:38 Subvolumes and isolation Holger Hoffstätte
2014-04-14 11:31 ` Hugo Mills
2014-04-14 11:50 ` Duncan [this message]
2014-04-14 12:25 ` Holger Hoffstätte
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='pan$83f14$2d652951$d4438311$791da6ce@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).