From: Roman Mamedov <rm@romanrm.ru>
To: Suman C <schakrava@gmail.com>
Cc: "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: Tue, 26 Feb 2013 11:57:04 +0600 [thread overview]
Message-ID: <20130226115704.50102196@natsu> (raw)
In-Reply-To: <CAPF83mvfLrDvBvbP5Oe_R94BM7Lr5pZD=gpnDrr4TquBq88q5Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
On Mon, 25 Feb 2013 21:35:08 -0800
Suman C <schakrava@gmail.com> wrote:
> Yes, zvol like feature where a btrfs subvolume like construct can be
> made available as a LUN/block device. This device can then be used by
> any application that wants a raw block device. iscsi is another
> obvious usecase. Having thin provisioning support would make it pretty
> awesome.
I think what you are missing is that btrfs is a filesystem, not a block device
management mechanism.
For your use case can simply create a snapshot and then make a sparse file
inside of it.
btrfs sub create foobar
dd if=/dev/zero of=foobar/100GB.img bs=1 count=1 seek=100G
If you need this to be a block device, use 'losetup' to make foobar/100GB.img
appear as one (/dev/loopX). But iSCSI/AoE/NBD can export files as well as block
devices, so this is not even necessary.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-02-26 5:57 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 [this message]
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
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=20130226115704.50102196@natsu \
--to=rm@romanrm.ru \
--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 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.