From: Chris Murphy <lists@colorremedies.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Virtual Device Support
Date: Sun, 19 May 2013 12:18:19 -0600 [thread overview]
Message-ID: <262CC063-0DB4-45BD-A776-9FD1E8650E7C@colorremedies.com> (raw)
In-Reply-To: <20130519171510.54897415@natsu>
On May 19, 2013, at 5:15 AM, Roman Mamedov <rm@romanrm.ru> wrote:
> On Fri, 10 May 2013 07:03:38 -0700
> George Mitchell <george@chinilu.com> wrote:
>
>> One the things that is frustrating me the most at this point from a user
>> perspective regarding btrfs is the current lack of virtual devices to
>> describe volumes and subvolumes.
>
> From a user perspective btrfs subvolumes have a lot in common with just
> regular directories aka folders, and nothing in common with (block)devices.
> "Describing them with virtual devices" does not seem to make a whole lot of
> sense.
It's not possible to mount regular directories with other file systems. In some ways the btrfs subvolume behaves like a folder. In other ways it acts like a device. If you stat the mount point for btrfs subvolumes, you get a unique device ID for each.
It seems inconsistent that mount and unmount allows a /dev/ designation, but only mount honors label and UUID.
I can mount with mount /dev/disk/by-uuid/xxxxxxx, but if I use umount /dev/disk/by-uuid/xxxxxxxx I get a bogus error:
umount: /dev/disk/by-uuid/xxxxxxxxxx: not mounted
mount /dev/disk/by-uuid will autocomplete/list uuids in that directory, umount will not. So just from a consistency standpoint that seems broken.
Chris Murphy
next prev parent reply other threads:[~2013-05-19 18:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 14:03 Virtual Device Support George Mitchell
2013-05-19 11:04 ` Martin
2013-05-19 14:49 ` George Mitchell
2013-05-19 17:18 ` Martin
[not found] ` <CAHGunUke143r3pj0Piv3AtJrJO1x8Bm+qS5Z+sY1G1EobhMG_w@mail.gmail.com>
2013-05-21 14:26 ` George Mitchell
2013-05-19 11:15 ` Roman Mamedov
2013-05-19 18:18 ` Chris Murphy [this message]
2013-05-19 18:22 ` Chris Murphy
2013-05-21 1:08 ` Duncan
2013-05-21 2:17 ` George Mitchell
2013-05-21 3:59 ` Duncan
2013-05-21 5:21 ` George Mitchell
2013-05-21 12:19 ` Virtual Device Support ("N-way mirror code") Martin
2013-05-23 16:08 ` Martin Steigerwald
2013-05-24 1:41 ` George Mitchell
2013-05-25 11:53 ` Martin Steigerwald
2013-05-24 6:13 ` Duncan
2013-05-25 11:56 ` Martin Steigerwald
2013-05-21 3:37 ` Virtual Device Support Chris Murphy
2013-05-21 12:06 ` Martin
2013-05-22 2:23 ` Chris Murphy
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=262CC063-0DB4-45BD-A776-9FD1E8650E7C@colorremedies.com \
--to=lists@colorremedies.com \
--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 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.