linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: LABEL only 1 device
Date: 26 Feb 2012 17:12:00 +0100	[thread overview]
Message-ID: <C3b12r9i1uB@helmut.hullen.de> (raw)
In-Reply-To: <20120226153036.GB18898@carfax.org.uk>

Hallo, Hugo,

Du meintest am 26.02.12:

>> Mounting seems to be no problem, but (p.e.) "delete" doesn't kill
>> the btrfs informations shown with (p.e.) "blkid /dev/sdy1",
>> especially it doesn't delete the label.

>    What do you mean by "delete" here?

   btrfs device delete <device> <path>

>    The label is a *filesystem* label, not a label for the block
> device(s) it lives on, so it doesn't make much sense to talk about
> putting an FS label on only one of the devices that the FS is on.

My (planned) usual work (once a year or so):

        btrfs device add <biggerdevice> <path>
        btrfs filesystem balance <path>
        btrfs device delete <smallerdevice> <path>

And the "devices" are (p.e.) /dev/sdj1, /dev/sdk1 etc. (partitions on a  
device).

Therefor I can see some informations via (p.e.)

        blkid /dev/sdj1

I prefer LABELling the devices/partitions, and then I'd seen that the  
option "-L" makes problems when I use it for more than 1 device/ 
partition.

With other file systems there's no real problem with the same label for  
several partitions - it doesn't work. But btrfs bundles these partitions  
(perhaps sometimes/most times regardless of the labels of the other  
partitions).

Viele Gruesse!
Helmut

  reply	other threads:[~2012-02-26 16:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-26 15:23 LABEL only 1 device Helmut Hullen
2012-02-26 15:30 ` Hugo Mills
2012-02-26 16:12   ` Helmut Hullen [this message]
2012-02-26 16:44     ` Hugo Mills
2012-02-26 16:57       ` Helmut Hullen
2012-02-26 17:14         ` Hugo Mills
2012-02-26 18:11           ` Helmut Hullen
2012-02-27  6:44           ` Helmut Hullen
2012-02-27 10:11             ` Hugo Mills
2012-02-27 10:27               ` Helmut Hullen
2012-02-27 16:48                 ` Duncan
2012-02-27 21:15                   ` Helmut Hullen
2012-02-27 21:23                     ` Hugo Mills
2012-02-27 21:33                     ` Felix Blanke
2012-02-27 21:45                     ` Hugo Mills
2012-02-27 21:59                       ` Helmut Hullen
2012-02-26 18:07       ` Duncan
2012-02-28 22:35         ` Karel Zak
2012-03-01  0:54           ` Duncan
2012-02-27 12:06       ` David Sterba
2012-02-27 12:24         ` Helmut Hullen

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=C3b12r9i1uB@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).