From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: Re: LABEL only 1 device
Date: 27 Feb 2012 22:15:00 +0100 [thread overview]
Message-ID: <C3f4teQD1uB@helmut.hullen.de> (raw)
In-Reply-To: <pan.2012.02.27.16.48.34@cox.net>
Hallo, Duncan,
Du meintest am 27.02.12:
>>> I've said this several times: Your expectations are wrong. You
>>> don't label partitions.
>> Yes - now I know.
>> But I'm afraid other people also expect wrong - when I use
>> mkfs.ext[234] then this option works (in another way than with
>> "mkfs.btrfs").
> AFAIK, it works in the same way... that is, it labels the, in that
> case, ext2/3/4 filesystem, in this case (mkfs.btrfs), btrfs
> filesystem.
> From the manpages:
> mkfs.btrfs (aka mkbtrfs):
> -L, --label name
> Specify a label for the filesystem.
> mkfs.ext2/3/4 (aka mke2fs):
> -L new-volume-label
> Set the volume label for the filesystem to
> new-volume-label. The maximum length of the
> volume label is 16 bytes.
But there's a small difference:
mke2fs -L MyLabel /dev/sdn4
only sets/changes the label (ok - it tests the type of the partition and
refuses labeling if the type doesn't fit).
mkfs.btrfs -L MyLabel /dev/sdn4
not only sets/changes the label but also (re-)creates a btrfs
filesystem, using the default parameters.
I had to learn this difference ...
Viele Gruesse!
Helmut
next prev parent reply other threads:[~2012-02-27 21:15 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
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 [this message]
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=C3f4teQD1uB@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).