From: Adrian von Bidder <avbidder@fortytwo.ch>
To: linux-btrfs@vger.kernel.org
Subject: Q: list btrfs snapshots/subvolumes
Date: Sun, 6 Dec 2009 16:37:49 +0100 [thread overview]
Message-ID: <200912061637.50131@fortytwo.ch> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 2106 bytes --]
Heyho!
I'm currently (once more) trying to experiment with btrfs, especially since
the ENOSPC handling and "delete snapshots/subvolumes" make it look extremely
appealing now.
Some questions:
* how do I list available snapshots/subvolumes?
* assuming a disk has failed: just to be sure:
"btrfs-vol -r missing" will remove the missing device. Not sure: will it
also replicate the missing copies of my (raid1) data and metadata? Given that
it takes ages (ok, just running a few minutes now ;-) to run on this system,
I'd assume so. Or is a separate "btrfs-vol -b" necessary?
* "subvolume" and "snapshot" is technically the same, except that a subvolume
is created empty and a snapshot is a cow copy of an existing tree. Handling
these two is the same once they're created?
Ok, that's what I can think of right now. Eagerly waiting for "set default
subvolume to be mounted" to be written... :-)
I just did a few tests with a 4 x 450G raid 1 btrfs volume: adding some 5G of
small files, remove a disk (didn't pull it out, but shut down the system
first), remove failing disk, re-add a disk. So far it seems to work just
fine. Just a curiosity: it seems to distribute all data between only two of
the disks, the other two stay empty. Is that desired behaviour? Wouldn't it
be more efficient to distribute data across all disks?
(everything with 2.6.32-rc8. Filesystem was created with btrfs-tools 0.19.)
cheers
-- vbi
(((
P.S.: since recovery after disk failure is a tense moment where I don't want
to have to hunt around for the answer ...:
--- a/btrfs-vol.c
+++ b/btrfs-vol.c
@@ -53,6 +53,8 @@ static void print_usage(void)
fprintf(stderr, "\t-a device add one device\n");
fprintf(stderr, "\t-b balance chunks across all devices\n");
fprintf(stderr, "\t-r device remove one device\n");
+ fprintf(stderr, "\t use 'missing' as device name "
+ "to remove a failed device\n");
exit(1);
}
)))
--
featured link: Debian Bookmark Collection - http://bookmarks.debian.net/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 389 bytes --]
next reply other threads:[~2009-12-06 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 15:37 Adrian von Bidder [this message]
2009-12-07 4:48 ` Q: list btrfs snapshots/subvolumes TARUISI Hiroaki
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=200912061637.50131@fortytwo.ch \
--to=avbidder@fortytwo.ch \
--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