From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: LABEL only 1 device
Date: 26 Feb 2012 17:57:00 +0100 [thread overview]
Message-ID: <C3b1BrAT1uB@helmut.hullen.de> (raw)
In-Reply-To: <20120226164400.GC18898@carfax.org.uk>
Hallo, Hugo,
Du meintest am 26.02.12:
>> My (planned) usual work (once a year or so):
>>
>> btrfs device add <biggerdevice> <path>
>> btrfs filesystem balance <path>
>> btrfs device delete <smallerdevice> <path>
> OK, the real problem you're seeing is that when btrfs removes a
> device from the filesystem, that device is not modified in any way.
> This means that the old superblock is left behind on it, containing
> the FS label information. What you need to do is, immediately after
> removing a device from the FS, zero the first part of the partition
> with dd and /dev/zero.
Ok - I'll try again (not today ...).
If I remember correct in early times deleting only the first block of
the partition didn't reach ...
My last try with "delete" let me believe that btrfs had deleted the
"critical" informations; I had tested it with "blkid". But looking into
the first sector of the partition may be more reliable.
>> 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.
[...]
> I say again, partitions are not labelled. *Filesystems* are
> labelled. I think that with a GPT you can refer to the disk itself
> and its partitions by a UUID each, but I'm not 100% certain.
My last try:
mkfs.btrfs -d raid0 -m raid1 /dev/sdk1 /dev/sdl1 /dev/sdm1
mkfs.btrfs -L SCSI /dev/sdk1
seemed to work.
mount LABEL=SCSI /mnt/btr
worked as expected, the bundle of 3 partitions was mounted. And only "/
dev/sdk1" got this label, no other partition.
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2012-02-26 16:57 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
2012-02-26 16:44 ` Hugo Mills
2012-02-26 16:57 ` Helmut Hullen [this message]
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=C3b1BrAT1uB@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).