From: Tsutomu Itoh <t-itoh@jp.fujitsu.com>
To: Randy Barlow <randy@electronsweatshop.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Sparse files and block devices
Date: Mon, 08 Aug 2011 15:13:40 +0900 [thread overview]
Message-ID: <4E3F7E94.30900@jp.fujitsu.com> (raw)
In-Reply-To: <4E3F7A4D.50702@electronsweatshop.com>
(2011/08/08 14:55), Randy Barlow wrote:
> I started playing with btrfs last night, and I must say that I am very
> excited! I do have one question so far. Since I was learning, I created
> a sparse file, and then used mkfs to get a btrfs filesystem. I
> entertained myself with that for a while, and then decided that I wanted
> to try out the multi device support. I found that the device add command
> requires the device to be a block device, and wouldn't accept another
> sparse file that I had created. Is there a workaround, or is that just
> the way it is?
I think that you can use 'losetup' command for this end.
-Tsutomu
>
> I ended up just making a logical volume to get the second block device.
>
> Thanks for making such a cool fs!
prev parent reply other threads:[~2011-08-08 6:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 5:55 Sparse files and block devices Randy Barlow
2011-08-08 6:13 ` Tsutomu Itoh [this message]
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=4E3F7E94.30900@jp.fujitsu.com \
--to=t-itoh@jp.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=randy@electronsweatshop.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