All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Mitchell <george@chinilu.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: umount and findmnt commands not working with btrfs labels ...
Date: Tue, 07 May 2013 07:10:47 -0700	[thread overview]
Message-ID: <51890B67.5040700@chinilu.com> (raw)
In-Reply-To: <20130507094835.GB7086@x2.net.home>

On 05/07/2013 02:48 AM, Karel Zak wrote:
>   Hi George,
>
> On Mon, May 06, 2013 at 03:28:53PM -0700, George Mitchell wrote:
>> [root@localhost ghmitch]# umount LABEL=MAGEIA3BTR-BOOT
>>
>> umount: LABEL=MAGEIA3BTR-BOOT: not found
>   umount --version ?
>
>   It works for me (tested with util-linux 2.22 and 2.23):
>
>    # mkfs.btrfs -L MAGEIA3BTR /dev/sdb1
>    # mkfs.btrfs -L MAGEIA3BTR-FOO /dev/sdb2
>
>    # mount LABEL=MAGEIA3BTR /mnt/test
>    # mount LABEL=MAGEIA3BTR-FOO /mnt/test
>
>    # findmnt LABEL=MAGEIA3BTR
>    TARGET    SOURCE    FSTYPE OPTIONS
>    /mnt/test /dev/sdb1 btrfs  rw,relatime,ssd,space_cache
>
>    # findmnt LABEL=MAGEIA3BTR-FOO
>    TARGET     SOURCE    FSTYPE OPTIONS
>    /mnt/test2 /dev/sdb2 btrfs  rw,relatime,ssd,space_cache
>
>    # umount LABEL=MAGEIA3BTR
>    # umount LABEL=MAGEIA3BTR-FOO
>
>    # lsblk --fs /dev/sdb
>    NAME   FSTYPE LABEL          UUID                                 MOUNTPOINT
>    sdb
>    ├─sdb1 btrfs  MAGEIA3BTR     6dcc3293-ce27-474f-ab31-dd7a8e5bb2da
>    └─sdb2 btrfs  MAGEIA3BTR-FOO f3bb2d57-8b46-40a0-ae76-50d78268d6d9
>
>
> It would be nice to have a simple reproducible scenario rather than a
> lot of mount -l outputs and some egrep tricks :-)
>
> You can also try
>
>    LIBMOUNT_DEBUG=0xffff umount LABEL=MAGEIA3BTR-BOOT
>
> to see more details.
>
>      Karel
>
Thanks, and sorry for including all the garbage.  I just wanted to make 
sure I didn't leave anything out.  The version I have here is 2.22.2.  I 
retested it using the DEBUG statement and it then worked and findmnt now 
works OK as well, so I don't know what was going on.  Something seems to 
have gotten cleaned up somewhere.  Tonight I will retest it on my other 
system that I use for maintainance on the USR partition since it would 
probably be unwise to fiddle with the USR partition with the system 
running.  At that point I will repost letting you know what I find.  - 
George

  reply	other threads:[~2013-05-07 14:10 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 [this message]
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
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=51890B67.5040700@chinilu.com \
    --to=george@chinilu.com \
    --cc=kzak@redhat.com \
    --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 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.