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: 04 Jan 2013 13:56:00 +0100	[thread overview]
Message-ID: <COClHr99CXB@helmut.hullen.de> (raw)
In-Reply-To: <14FFD425-4B7D-4523-AEAF-527A6B72DCB4@colorremedies.com>

Hallo, Chris,

Du meintest am 03.01.13:

>>> MBR has no mechanism for labeling the disk itself or the
>>> partitions. So /dev/sda cannot have a label or a name.

>> Sure?

> Yes. MBR itself has no place holder to encode a disk name or
> partition name. http://en.wikipedia.org/wiki/Master_boot_record

I've just played a bit ...

   btrfs-show

tells

**
** WARNING: this program is considered deprecated
** Please consider to switch to the btrfs utility
**
Label: USBmm  uuid: 43ad1782-5d1c-4211-9333-506bcfdbc3a5
	Total devices 1 FS bytes used 28.00KB
	devid    1 size 3.78GB used 423.50MB path /dev/sdb

Label: mylabel  uuid: e9716633-49f1-44a0-a3b4-90ba9736a540
	Total devices 3 FS bytes used 28.00KB
	devid    2 size 1.00GB used 110.38MB path /dev/sdb2
	devid    1 size 1.00GB used 275.94MB path /dev/sdb1
	devid    3 size 1.00GB used 263.94MB path /dev/sdb3

Btrfs Btrfs v0.19

# ----------------------------------------

The "USBmm" entry remains from

   mkfs.btrfs -d raid0 -m raid1 -L USBmm /dev/sdb

Then I run "fdisk /dev/sdb" and created 4 partitions on "/dev/sdb"  
without previous overwriting it with zeros.

And then

   mkfs.btrfs -d raid0 -m raid1 -L mylabel /dev/sdb1 /dev/sdb2 /dev/sdb3

Inspecting the first sectors of "/dev/sdb" shows the string "USBmm" at  
the beginning of the second 64-kByte block (0x10120 ... 0x1012f).

The "mylabel" entries are somewhere after the first 128 kByte.

Viele Gruesse!
Helmut

  reply	other threads:[~2013-01-04 12:56 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 [this message]
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
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=COClHr99CXB@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.