From: Andy Grover <agrover@redhat.com>
To: Suman C <schakrava@gmail.com>
Cc: Roman Mamedov <rm@romanrm.ru>,
"Fajar A. Nugraha" <list@fajar.net>,
Mike Fleetwood <mike.fleetwood@googlemail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: lvm volume like support
Date: Fri, 19 Apr 2013 11:13:21 -0700 [thread overview]
Message-ID: <51718941.2010800@redhat.com> (raw)
In-Reply-To: <CAPF83mv2qVqE5HnXVr9P8JHqs4+DKjt0hWaR8UG6Kk4reyPsAw@mail.gmail.com>
On 02/25/2013 10:25 PM, Suman C wrote:
> Thanks for the sparse file idea, I am actually using that solution
> already. I am not sure if its the best way, however.
(Sorry to respond to such an old thread.)
Hi Suman,
I think zvol-like functionality would be very nice for btrfs to have. It
would be more natural to manage btrvols than looped-back files I think,
and removing those sw layers may also increase performance, but who
knows by how much. It would let btrfs really act as "just" the LVM, if
desired.
Do we have any sense for how much work adding this would be?
Regards -- Andy
p.s. some interesting stuff on zvols
http://pthree.org/2012/12/21/zfs-administration-part-xiv-zvols/
next prev parent reply other threads:[~2013-04-19 18:13 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 [this message]
2013-02-26 10:30 ` Martin Steigerwald
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=51718941.2010800@redhat.com \
--to=agrover@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@fajar.net \
--cc=mike.fleetwood@googlemail.com \
--cc=rm@romanrm.ru \
--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).