From: Kaspar Schleiser <kaspar@schleiser.de>
To: Hubert Kario <hka@qbs.com.pl>
Cc: Freddie Cash <fjwcash@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Synching a Backup Server
Date: Tue, 25 Jan 2011 18:29:35 +0100 [thread overview]
Message-ID: <4D3F087F.20905@schleiser.de> (raw)
In-Reply-To: <201101221455.45968.hka@qbs.com.pl>
On 01/22/2011 02:55 PM, Hubert Kario wrote:
>> It looks like ZFS, Btrfs, and LVM should work in similar manners, but
>> the overloaded terminology (pool, volume, sub-volume, filesystem are
>> different in all three) and new terminology that's only in Btrfs is
>> confusing.
>
> With btrfs you need to have *a* filesystem, once you have it, you can add and
> remove disks/partitions from it, no need to use 'mkfs.btrfs', just 'btrfs'.
That's just a design decision, right? There's no need for a "default" or
"root" subvolume.
It should be rather easy to change btrfs so that you first have to
create a "storage pool" which combines disks for btrfs, and on top of
that you can create "filesystems" which are just subvolumes.
The creation of a "storage pool" could be very similar to the current
mkfs, just without the creation of a root subvolume.
A new, simpler mkfs would then just create a subvolume on top of the
"storage pool" that can be mounted.
Regards,
Kaspar
next prev parent reply other threads:[~2011-01-25 17:29 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 17:35 Synching a Backup Server Carl Cook
2011-01-06 19:16 ` Freddie Cash
2011-01-06 19:34 ` Marcin Kuk
[not found] ` <AANLkTik-rhXAHW18id4WMMtdqXkicvzTZ47+2r6YMuY0@mail.gmail.com>
2011-01-06 19:47 ` Freddie Cash
2011-01-06 20:07 ` C Anthony Risinger
2011-01-06 20:13 ` Freddie Cash
2011-01-06 20:21 ` C Anthony Risinger
2011-01-06 21:06 ` Gordan Bobic
2011-01-06 21:39 ` Freddie Cash
2011-01-06 21:44 ` Carl Cook
2011-01-06 21:53 ` Gordan Bobic
2011-01-06 21:58 ` Freddie Cash
2011-01-06 22:26 ` Carl Cook
2011-01-06 22:29 ` Gordan Bobic
2011-01-06 23:07 ` Carl Cook
2011-01-07 16:14 ` Hubert Kario
2011-01-06 23:15 ` Fajar A. Nugraha
2011-01-06 21:42 ` Carl Cook
2011-01-06 21:52 ` Freddie Cash
2011-01-07 16:20 ` Hubert Kario
2011-01-09 11:46 ` Alan Chandler
2011-01-09 13:54 ` Fajar A. Nugraha
2011-01-09 15:32 ` Alan Chandler
2011-01-09 17:59 ` Freddie Cash
2011-01-09 18:30 ` Hugo Mills
2011-01-09 20:57 ` Alan Chandler
2011-01-09 22:01 ` Hugo Mills
2011-01-09 23:32 ` Alan Chandler
2011-01-11 22:25 ` Hugo Mills
2011-01-10 2:22 ` Fajar A. Nugraha
2011-01-11 22:41 ` Hugo Mills
2011-01-21 19:28 ` Freddie Cash
2011-01-22 13:45 ` Hugo Mills
2011-01-24 17:45 ` Freddie Cash
2011-01-22 13:55 ` Hubert Kario
2011-01-25 17:29 ` Kaspar Schleiser [this message]
2011-01-25 17:43 ` Hubert Kario
2011-01-25 17:59 ` Freddie Cash
2011-01-25 18:36 ` Hubert Kario
2011-01-10 13:14 ` Hubert Kario
2011-01-06 20:12 ` Fajar A. Nugraha
2011-01-06 21:43 ` Carl Cook
2011-01-06 21:43 ` Goffredo Baroncelli
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=4D3F087F.20905@schleiser.de \
--to=kaspar@schleiser.de \
--cc=fjwcash@gmail.com \
--cc=hka@qbs.com.pl \
--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).