All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hullen@t-online.de (Helmut Hullen)
To: linux-btrfs@vger.kernel.org
Subject: Re: Option LABEL
Date: 05 Jan 2013 13:44:00 +0100	[thread overview]
Message-ID: <COGoZAXPCXB@helmut.hullen.de> (raw)
In-Reply-To: <201301051236.37875.Martin@lichtvoll.de>

Hallo, Martin,

Du meintest am 05.01.13:

>> No - I don't rely on such an assumption.
>> In the special case I'm just working with I want to use the whole
>> disk only for btrfs.
>>
>> In other cases I work with partitions, and there is just the same
>> problem: at least "blkid" and "findfs" don't work when more than 1
>> device has the same label (p.e. /dev/sda3 and /dev/sdc5).

It seems to be a problem which is related to "blkid".

> Helmut, it has been shown here in the thread, that they *do* work in
> newer versions.

> If they don?t work for you please compare your version with the ones
> that do work and file a bug report for your Linux distribution.

   blkid from util-linux 2.21.2 (libblkid 2.21.0, 25-May-2012
   findfs from the same "util-linux" packet
   kernel 3.6.11

Is that new enough?

-------------------------------------------

Reproducable:
USB stick with 3 btrfs partitions

cold start without stick, logged in as "root"
        blkid           works

Stick inserted:
        blkid           works
        fdisk -l        works

   btrfs device scan    works
        blkid           works

   btrfs-show           works
        blkid           hangs

        blkid /dev/sdb1 works

I don't know who may be responsible for this problem - btrfs or blkid or  
both.



Viele Gruesse!
Helmut

  reply	other threads:[~2013-01-05 12:45 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03 15:14 Option LABEL Helmut Hullen
2013-01-03 16:08 ` Hugo Mills
2013-01-03 16:29   ` Helmut Hullen
2013-01-03 17:01     ` Hugo Mills
2013-01-03 17:43       ` james northrup
2013-01-03 17:57       ` Helmut Hullen
2013-01-03 18:10         ` cwillu
2013-01-03 18:20           ` Helmut Hullen
2013-01-03 19:18             ` Chris Murphy
2013-01-03 19:35               ` Chris Murphy
2013-01-03 20:28                 ` Helmut Hullen
2013-01-03 21:23                   ` Hugo Mills
2013-01-03 21:27                     ` Chris Murphy
2013-01-03 22:07                       ` Helmut Hullen
2013-01-03 21:52                     ` Helmut Hullen
2013-01-06 16:02                       ` Goffredo Baroncelli
2013-01-04 12:11                     ` Helmut Hullen
2013-01-04 20:59                     ` Helmut Hullen
2013-01-04 21:41                       ` Chris Murphy
2013-01-03 19:59               ` Helmut Hullen
2013-01-03 21:17                 ` Chris Murphy
2013-01-04 12:56                   ` Helmut Hullen
2013-01-03 18:33         ` Hugo Mills
2013-01-03 19:08           ` Helmut Hullen
2013-01-03 19:28             ` Hugo Mills
2013-01-03 20:18               ` Helmut Hullen
2013-01-05 11:36                 ` Martin Steigerwald
2013-01-05 12:44                   ` Helmut Hullen [this message]
2013-01-05 19:08                     ` Chris Murphy
2013-01-05 13:15   ` Helmut Hullen
2013-01-05 19:10     ` Chris Murphy
2013-01-05 19:13       ` Hugo Mills
2013-01-05 21:03       ` Helmut Hullen
2013-01-05 21:21         ` 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=COGoZAXPCXB@helmut.hullen.de \
    --to=hullen@t-online.de \
    --cc=helmut@hullen.de \
    --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.