public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: "yanhai zhu" <zhu.yanhai@gmail.com>
Cc: Roland <devzero@web.de>, "Yan Zheng" <ukernel@gmail.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: multiple device usage
Date: Mon, 29 Dec 2008 11:49:19 +0100	[thread overview]
Message-ID: <20081229114919.59f7114d.skraw@ithnet.com> (raw)
In-Reply-To: <977a2be20812280526y10eb4646i18cdc17c3af072f3@mail.gmail.com>

On Sun, 28 Dec 2008 21:26:11 +0800
"yanhai zhu" <zhu.yanhai@gmail.com> wrote:

> > so i can do btrfs-vol -r /dev/sdb while it`s being mounted, pull the disk ,
> > replace it with a bigger one, rescan-scsi-bus, mkfs.btrfs the new disk and
>                                                  ~~~~~~~~~~~~~~~~~~~~~~~
>                                                 This step will fail, you will
> get a "/dev/sdb is mounted" by mkfs.btrfs, but for other slots it's ok.

Really, what average-joe-user needs btrfs for his not-always-mounted
data-partition? Why shouldn't he just use any other fs for that?
All users needing _uptime_ of their fs cannot simply unmount and wait hours
for some cool feature to (hopefully) complete (without failures).
Why does nobody talk about the real world? What's the use of features that
cannot complete their job in users' lifetime due to everybody filling up TBs
of data on their harddisks. How long does it really take to replace a full 300
GB hd with a 800 GB in a multi volume btrfs ?
Please play with real amounts of data and judge for yourself the use of
offline-fs-features.
The times of classical PC use are gone, today people have just about
everything on their hds, music collection, dvd collection, mails, documents of
all kinds, sourcecode trees, name-one. 500 GB hds are very cheap. A _new_ fs
not able to cope with these new usage-patterns is in fact _useless_.

Regards,
Stephan


 
> > then re-add - all while mount telling me, that /dev/sdb is still in use !?
> 
> 2008/12/27 Roland <devzero@web.de>:
> >>> i have some difficulty in understanding multi-device handling in depth.
> >>>
> >>> as
> >>> http://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices
> >>> tells,
> >>>
> >>> btrfs can span over multiple devices at the same time. (great feature,
> >>> btw !)
> >>>
> >>> ok then:
> >>>
> >>> mkfs.btrfs -m single -d single  /dev/sdb /dev/sdc - creates a btrfs
> >>> spanning
> >>> over /dev/sdb and sdc
> >>>
> >>> mount /dev/sdb /btrfs - mounts it
> >>>
> >>> btrfs-vol -b /btrfs - does a rebalancing of all data and metadata
> >>>
> >>> btrfs-vol -r /dev/sdc - removes one of the volumes and redistributes any
> >>> extends in use on sdc to sdb (killer feature!!!)
> >>>
> >>> but what if i want to remove /dev/sdb ? (as that one is in use for the
> >>> mount)
> >>>
> >>
> >> Devices in btrfs are equal, so you can do this. The only glitch is
> >> /proc/mounts and mount(8) get confused.
> >
> > so i can do btrfs-vol -r /dev/sdb while it`s being mounted, pull the disk ,
> > replace it with a bigger one, rescan-scsi-bus, mkfs.btrfs the new disk and
> > then re-add - all while mount telling me, that /dev/sdb is still in use !?
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> 
> 
> 
> -- 
> Regards,
> Zhu Yanhai
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


  reply	other threads:[~2008-12-29 10:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-26 23:15 multiple device usage devzero
2008-12-27  2:44 ` Yan Zheng
2008-12-27 14:12   ` Roland
2008-12-28 13:26     ` yanhai zhu
2008-12-29 10:49       ` Stephan von Krawczynski [this message]
2008-12-29 12:31       ` Roland
2008-12-29 12:35         ` Yan Zheng
2008-12-30 21:43           ` Chris Mason
2008-12-27  6:45 ` Chris Samuel
2008-12-29 11:32   ` Chris Samuel
2008-12-29 12:33     ` Yan Zheng
2008-12-29 12:52       ` Chris Samuel
2008-12-29 15:16         ` Yan Zheng
2008-12-30 21:25           ` Chris Mason
2009-01-01  1:02             ` Chris Samuel

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=20081229114919.59f7114d.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=devzero@web.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=ukernel@gmail.com \
    --cc=zhu.yanhai@gmail.com \
    /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