From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: "Fajar A. Nugraha" <list@fajar.net>,
Mike Fleetwood <mike.fleetwood@googlemail.com>,
Suman C <schakrava@gmail.com>
Subject: Re: lvm volume like support
Date: Tue, 26 Feb 2013 11:30:31 +0100 [thread overview]
Message-ID: <201302261130.31494.Martin@lichtvoll.de> (raw)
In-Reply-To: <CAG1y0scOg2QGCZdCTkKHBn5xxNh5GGmdXTcS8rOesup4r1JsXQ@mail.gmail.com>
Am Dienstag, 26. Februar 2013 schrieb Fajar A. Nugraha:
> On Tue, Feb 26, 2013 at 11:59 AM, Mike Fleetwood
>
> <mike.fleetwood@googlemail.com> wrote:
> > On 25 February 2013 23:35, Suman C <schakrava@gmail.com> wrote:
> >> Hi,
> >>
> >> I think it would be great if there is a lvm volume or zfs zvol type
> >> support in btrfs.
> >
> > Btrfs already has capabilities to add and remove block devices on the
> > fly. Data can be stripped or mirrored or both. Raid 5/6 is in
> > testing at the moment.
> > https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devic
> > es https://btrfs.wiki.kernel.org/index.php/UseCases#RAID
> >
> > Which specific features do you think btrfs is lacking?
>
> I think he's talking about zvol-like feature.
>
> In zfs, instead of creating a
> filesystem-that-is-accessible-as-a-directory, you can create a zvol
> which behaves just like any other standard block device (e.g. you can
> use it as swap, or create ext4 filesystem on top of it). But it would
> also have most of the benefits that a normal zfs filesystem has, like:
> - thin provisioning (sparse allocation, snapshot & clone)
> - compression
> - integrity check (via checksum)
>
> Typical use cases would be:
> - swap in a pure-zfs system
> - virtualization (xen, kvm, etc)
> - NAS which exports the block device using iscsi/AoE
>
> AFAIK no such feature exist in btrfs yet.
Sounds like the RADOS block device stuff for Ceph.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2013-02-26 10:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 23:35 lvm volume like support Suman C
2013-02-26 0:59 ` Mike Fleetwood
2013-02-26 1:46 ` Fajar A. Nugraha
2013-02-26 5:35 ` Suman C
2013-02-26 5:48 ` Remco Hosman - Yerf-IT
2013-02-26 5:57 ` Roman Mamedov
2013-02-26 6:25 ` Suman C
2013-02-26 6:28 ` Remco Hosman - Yerf IT
2013-02-26 6:37 ` Alex Elsayed
2013-02-26 7:08 ` Dave Chinner
2013-04-19 18:13 ` Andy Grover
2013-02-26 10:30 ` Martin Steigerwald [this message]
2013-02-27 2:23 ` Fajar A. Nugraha
2013-02-27 4:05 ` Roman Mamedov
2013-02-27 8:42 ` Martin Steigerwald
2013-02-27 9:17 ` Roman Mamedov
2013-02-27 8:50 ` Alex Elsayed
2013-02-27 9:57 ` Alex Elsayed
2013-02-27 10:12 ` Alex Elsayed
2013-04-08 12:01 ` David Sterba
2013-04-11 12:29 ` David Sterba
2013-03-02 6:24 ` Marcus Sorensen
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=201302261130.31494.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@fajar.net \
--cc=mike.fleetwood@googlemail.com \
--cc=schakrava@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;
as well as URLs for NNTP newsgroup(s).