Karel Zak posted on Tue, 28 Feb 2012 23:35:57 +0100 as excerpted:
On Sun, Feb 26, 2012 at 06:07:31PM +, Duncan wrote:
Unfortunately, since gpt is reasonably new in terms of filesystem and
partitioning tools, there isn't really anything (mount, etc) that makes
/use/ of that label yet,
On Sun, Feb 26, 2012 at 06:07:31PM +, Duncan wrote:
Unfortunately, since gpt is reasonably new in terms of filesystem and
partitioning tools, there isn't really anything (mount, etc) that makes
/use/ of that label yet,
udev exports GPT labels and uuids by symlinks, see
ls
On Mon, Feb 27, 2012 at 07:44:00AM +0100, Helmut Hullen wrote:
Hallo, Hugo,
Du meintest am 26.02.12:
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.
The safest way may be
Hallo, Hugo,
Du meintest am 27.02.12:
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.
The safest way may be deleting this option ... it seems to work as
expected only when I create
On Sun, Feb 26, 2012 at 04:44:00PM +, Hugo Mills wrote:
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
Hallo, David,
Du meintest am 27.02.12:
[deleting btrfs partition]
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
Helmut Hullen posted on Mon, 27 Feb 2012 11:27:00 +0100 as excerpted:
Du meintest am 27.02.12:
mkfs.btrfs creates a new filesystem. The -L option sets the label
for the newly-created FS.
The safest way may be deleting this option ... it seems to work as
expected only when I create a
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).
On Mon, Feb 27, 2012 at 10:15:00PM +0100, Helmut Hullen wrote:
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
Hi Helmut,
are you sure that 'mkfs.ext2/3/4 -L label /dev/xxx' doesn't create a
new fs?
Afaik to change a label of a given (ext2/3/4) filesystem you should use
tune2fs.
I don't have a linux system available right now but this is what I would
expect and what would make a lot more sense
On Mon, Feb 27, 2012 at 10:15:00PM +0100, Helmut Hullen wrote:
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
Hallo, Hugo,
Du meintest am 27.02.12:
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).
OK, I have just tried this out. It does set the filesystem
Hallo, linux-btrfs,
maybe it's a big error using the commmand
mkfs.btrfs -L xyz /dev/sdx1 /dev/sdy1 /dev/sdz1
(and so labelling many partitions) because each device/partition gets
the same label.
Mounting seems to be no problem, but (p.e.) delete doesn't kill the
btrfs informations shown
On Sun, Feb 26, 2012 at 04:23:00PM +0100, Helmut Hullen wrote:
Hallo, linux-btrfs,
maybe it's a big error using the commmand
mkfs.btrfs -L xyz /dev/sdx1 /dev/sdy1 /dev/sdz1
(and so labelling many partitions) because each device/partition gets
the same label.
Mounting seems to be
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
On Sun, Feb 26, 2012 at 05:12:00PM +0100, Helmut Hullen wrote:
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
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
Hugo Mills posted on Sun, 26 Feb 2012 16:44:00 + as excerpted:
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.
As far as I know, you can't label partitions or devices. Labels are
a
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
Hallo, Hugo,
Du meintest am 26.02.12:
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.
The safest way may be deleting this option ... it seems to work as
expected only when I create a
20 matches
Mail list logo
