All of lore.kernel.org
 help / color / mirror / Atom feed
* Q: list  btrfs snapshots/subvolumes
@ 2009-12-06 15:37 Adrian von Bidder
  2009-12-07  4:48 ` TARUISI Hiroaki
  0 siblings, 1 reply; 2+ messages in thread
From: Adrian von Bidder @ 2009-12-06 15:37 UTC (permalink / raw)
  To: linux-btrfs

[-- 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 --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Q: list  btrfs snapshots/subvolumes
  2009-12-06 15:37 Q: list btrfs snapshots/subvolumes Adrian von Bidder
@ 2009-12-07  4:48 ` TARUISI Hiroaki
  0 siblings, 0 replies; 2+ messages in thread
From: TARUISI Hiroaki @ 2009-12-07  4:48 UTC (permalink / raw)
  To: avbidder; +Cc: linux-btrfs

> 
> Some questions:
>  * how do I list available snapshots/subvolumes?

As for this question, we will soon be able to list available
snapshots/subvolumes with btrfsctl utility.
But for now, we should count number of BTRFS_ROOT_ITEMs with
btrfs-debug-tree or so.

Regards,
taruisi


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-12-07  4:48 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-12-06 15:37 Q: list btrfs snapshots/subvolumes Adrian von Bidder
2009-12-07  4:48 ` TARUISI Hiroaki

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.