From: Hullen@t-online.de (Helmut Hullen)
To: util-linux@vger.kernel.org
Subject: Re: umount and findmnt commands not working with btrfs labels ...
Date: 09 May 2013 18:59:00 +0200 [thread overview]
Message-ID: <CWYcVs5uCXB@helmut.hullen.de> (raw)
In-Reply-To: <518BC86D.2050702@chinilu.com>
Hallo, George,
Du meintest am 09.05.13:
>> Ah, do you mean btrfs raid? For example:
>>
>> mkfs.btrfs --data raid1 --label FOO /dev/sdd1 /dev/sdd2
>>
>> then the LABEL and UUID is really duplicate.
[...]
> It would be nice if btrfs would just lock all of these partitions out
> and represent them collectively to the broader system as /dev/mntX or
> whatever.
Perhaps you shouldn't use only "blkid" - sometimes I've seen strange
answers (or no answer). I haven't yet found the system behind this
behaviour.
file -s /dev/sdd1
(p.e.) is more reliable.
But for mounting and unmounting I haven't seen any problem:
mount LABEL=FOO /path/to/mountpoint
umount LABEL=FOO
has always worked as expected; for existing devices and mountpoints and
also for nonexisting devices and mountpoints.
By the way: my system doesn't use "udev"; working/addressing with LABEL
works fine also without "udev".
And by another way:
blkid
tells every btrfs disk/partition which is part of the btrfs cluster (in
my installations: all 3 disks) - they have the same UUID but different
UUID_SUBs. No real problem.
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2013-05-09 17:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-06 22:28 umount and findmnt commands not working with btrfs labels George Mitchell
2013-05-07 9:48 ` Karel Zak
2013-05-07 14:10 ` George Mitchell
2013-05-07 14:48 ` George Mitchell
2013-05-09 9:42 ` Karel Zak
2013-05-09 14:06 ` George Mitchell
2013-05-09 18:53 ` Karel Zak
2013-05-09 16:01 ` George Mitchell
2013-05-09 16:59 ` Helmut Hullen [this message]
2013-05-09 19:07 ` Karel Zak
2013-05-09 19:54 ` Roger Leigh
2013-05-10 0:15 ` George Mitchell
2013-05-10 8:28 ` Karel Zak
2013-05-07 15:10 ` George Mitchell
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=CWYcVs5uCXB@helmut.hullen.de \
--to=hullen@t-online.de \
--cc=helmut@hullen.de \
--cc=util-linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox