linux-btrfs.vger.kernel.org archive mirror
 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 14:15:00 +0100	[thread overview]
Message-ID: <COGohh5PCXB@helmut.hullen.de> (raw)
In-Reply-To: <20130103160853.GA19051@carfax.org.uk>

Hallo, Hugo,

Du meintest am 03.01.13:

>> My usual way:
>>
>>         mkfs.btrfs -d raid0 -m raid1 /dev/sdb /dev/sdc /dev/sdd ...
>>
>> One call for some devices.
>> Wenn I add the option "-L mylabel" then each device gets the same
>> label, and therefore some other programs can't find the (one) device
>> with the defined label.

[...]

>> Especially
>>
>>      blkid
>>      findfs LABEL=mylabel
>>
>> don't work.

>    How do you mean, "don't work"?

Seems to be a problem which is invoked by "btrfs-show".

Working with an USB stick (3 btrfs partitions, labelled), working as  
"root", kernel 3.6.11

cold start
inserting the stick

        btrfs device scan       ok
        btrfs fi show           ok
        blkid                   ok

cold start
inserting the stick

        btrfs device scan       ok
        blkid                   ok
        btrfs-show              ok (?)
        blkid                   hangs

Maybe the simpliest way is to delete "btrfs-show".

Viele Gruesse!
Helmut

  parent reply	other threads:[~2013-01-05 13:19 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
2013-01-05 19:08                     ` Chris Murphy
2013-01-05 13:15   ` Helmut Hullen [this message]
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=COGohh5PCXB@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).