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 19:11:00 +0100	[thread overview]
Message-ID: <C3b1KRsi1uB@helmut.hullen.de> (raw)
In-Reply-To: <20120226171419.GD18898@carfax.org.uk>

Hallo, Hugo,

Du meintest am 26.02.12:

>>> 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 ...

>    No, it won't -- the first superblock on btrfs is at 64k into the
> device. Most filesystems do something similar, because there's other
> things that occasionally put metadata in the first part of the
> device, so it avoids having the FS's superblock overwritten
> accidentally.

Ok - but deleting the first 100 kByte or the first 1 MByte does reach?
Last times I'd run a job which deleted all (but that's nasty for disks  
with much more than 100 GByte ...)

>>         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.

>    That's because you've just destroyed part of the original
> filesystem that was on /dev/sd[klm]1 and created a new single-device
> filesystem on /dev/sdk1.

>    mkfs.btrfs creates a new filesystem. The -L option sets the label
> for the newly-created FS. It *cannot* be used to change the label of
> an existing FS. If you want to do that, use "btrfs filesystem label".

Hmmmm - I'll try ...

Thank you!

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

Label: 'SCSI'  uuid: 8e287956-d73f-46cb-8938-b00315c596c6
	Total devices 1 FS bytes used 92.00KB
	devid    1 size 136.73GB used 2.04GB path /dev/sdj1

Label: 'Scsi'  uuid: b59caf71-1a38-47cc-bad3-c2d87357c971
	Total devices 3 FS bytes used 9.09GB
	devid    2 size 136.73GB used 4.01GB path /dev/sdl1
	devid    3 size 68.37GB used 5.01GB path /dev/sdm1
	devid    1 size 16.96GB used 5.02GB path /dev/sdk1

Btrfs Btrfs v0.19

looks good ...


Viele Gruesse!
Helmut

  reply	other threads:[~2012-02-26 18:11 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
2012-02-26 17:14         ` Hugo Mills
2012-02-26 18:11           ` Helmut Hullen [this message]
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=C3b1KRsi1uB@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).