Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #261977 > unrolled thread

naming a partition after the fact?

Back to article view | Back to linux.debian.user

Contents

  naming a partition after the fact? gene heskett <gheskett@shentel.net> - 2023-09-29 21:00 +0200
    Re: naming a partition after the fact? gene heskett <gheskett@shentel.net> - 2023-09-29 21:20 +0200
    Re: naming a partition after the fact? Andy Smith <andy@strugglers.net> - 2023-09-29 21:20 +0200
      Re: naming a partition after the fact? gene heskett <gheskett@shentel.net> - 2023-09-29 22:00 +0200
        Re: naming a partition after the fact? Andy Smith <andy@strugglers.net> - 2023-09-29 22:10 +0200
        Re: naming a partition after the fact? Max Nikulin <manikulin@gmail.com> - 2023-09-30 05:40 +0200
          Re: naming a partition after the fact? gene heskett <gheskett@shentel.net> - 2023-09-30 15:40 +0200
      Re: naming a partition after the fact? Michel Verdier <mv524@free.fr> - 2023-09-29 22:20 +0200
        Re: naming a partition after the fact? Andy Smith <andy@strugglers.net> - 2023-09-29 22:40 +0200
          Re: naming a partition after the fact? Michel Verdier <mv524@free.fr> - 2023-09-29 23:20 +0200
          Re: naming a partition after the fact? Stefan Monnier <monnier@iro.umontreal.ca> - 2023-09-30 00:10 +0200
            Re: naming a partition after the fact? Andy Smith <andy@strugglers.net> - 2023-09-30 02:10 +0200
              Re: naming a partition after the fact? gene heskett <gheskett@shentel.net> - 2023-09-30 09:30 +0200
                Re: naming a partition after the fact? Andy Smith <andy@strugglers.net> - 2023-09-30 13:30 +0200
                  Re: naming a partition after the fact? gene heskett <gheskett@shentel.net> - 2023-09-30 16:00 +0200
                    Re: naming a partition after the fact? David Wright <deblis@lionunicorn.co.uk> - 2023-09-30 20:20 +0200
                      Re: naming a partition after the fact? gene heskett <gheskett@shentel.net> - 2023-10-01 01:50 +0200
              Re: naming a partition after the fact? Stefan Monnier <monnier@iro.umontreal.ca> - 2023-09-30 17:20 +0200
                Re: naming a partition after the fact? David Wright <deblis@lionunicorn.co.uk> - 2023-09-30 20:20 +0200
          Re: naming a partition after the fact? David Wright <deblis@lionunicorn.co.uk> - 2023-09-30 05:20 +0200
    Re: naming a partition after the fact? Robert Riding <reriding@xmission.com> - 2023-10-01 09:50 +0200
      Re: naming a partition after the fact? Andy Smith <andy@strugglers.net> - 2023-10-01 11:30 +0200
        Re: naming a partition after the fact? David Wright <deblis@lionunicorn.co.uk> - 2023-10-01 17:40 +0200

Page 1 of 2  [1] 2  Next page →

#261977 — naming a partition after the fact?

Greetings all;

I recall something I haven't used in a decade or more, but we used to 
have a journal something or other that could rename a partition, and I 
need something like it. debian 12 on an rpi4b and while a sudo -E 
gparted brings up gparted on the named device, the "name partition" is 
greyed out in the menu's.  Do we now have something that can LABEL a 
partition on debian arm64's w/o disturbing the data on it?

Tnx all.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [next] | [standalone]

#261978

On 9/29/23 14:50, gene heskett wrote:
> Greetings all;
> 
> I recall something I haven't used in a decade or more, but we used to 
> have a journal something or other that could rename a partition, and I 
> need something like it. debian 12 on an rpi4b and while a sudo -E 
> gparted brings up gparted on the named device, the "name partition" is 
> greyed out in the menu's.  Do we now have something that can LABEL a 
> partition on debian arm64's w/o disturbing the data on it?
> 
Nevermind, I found if it wasn't mounted, I could label it.

> Tnx all.
> 
> Cheers, Gene Heskett.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#261979

Hello,

On Fri, Sep 29, 2023 at 02:50:23PM -0400, gene heskett wrote:
> I recall something I haven't used in a decade or more, but we used to have a
> journal something or other that could rename a partition, and I need
> something like it.

Probably, but adding a label to a *filesystem* is easy, so will
that suit your needs? "man e2label" for ext* filesystems.

If not, what are you actually trying to achieve with partition
names? I can't think what use they have ever been to me in several
decades.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [next] | [standalone]

#261982

On 9/29/23 15:17, Andy Smith wrote:
> Hello,
> 
> On Fri, Sep 29, 2023 at 02:50:23PM -0400, gene heskett wrote:
>> I recall something I haven't used in a decade or more, but we used to have a
>> journal something or other that could rename a partition, and I need
>> something like it.
> 
> Probably, but adding a label to a *filesystem* is easy, so will
> that suit your needs? "man e2label" for ext* filesystems.
> 
That is what I couldn't remember Andy, thanks.

> If not, what are you actually trying to achieve with partition
> names? I can't think what use they have ever been to me in several
> decades.

Non volatility. Partition names are permanent until changed, or the 
drive upchucks.  blkid's are quite a bit more volatile and have bitten 
me several times in now long past history. I think they have gotten more 
stable since around wheezy, but... A matter of trust.

Thanks Andy

> Thanks,
> Andy
> 

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#261983

Hello,

On Fri, Sep 29, 2023 at 03:54:40PM -0400, gene heskett wrote:
> On 9/29/23 15:17, Andy Smith wrote:
> > If not, what are you actually trying to achieve with partition
> > names? I can't think what use they have ever been to me in several
> > decades.
> 
> Non volatility. Partition names are permanent until changed, or the drive
> upchucks.  blkid's are quite a bit more volatile and have bitten me several
> times in now long past history. I think they have gotten more stable since
> around wheezy, but... A matter of trust.

So nothing that isn't also gained by filesystem label or UUID, which
are what I've tended to use instead of partition names.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [next] | [standalone]

#261994

On 30/09/2023 02:54, gene heskett wrote:
> On 9/29/23 15:17, Andy Smith wrote:
>> Probably, but adding a label to a *filesystem* is easy, so will
>> that suit your needs? "man e2label" for ext* filesystems.
>>
> That is what I couldn't remember Andy, thanks.

In the case of GPT, partitions may have names that are independent of 
filesystem labels. It is similar to partition UUID and filesystem UUID.

>> If not, what are you actually trying to achieve with partition
>> names? I can't think what use they have ever been to me in several
>> decades.
> 
> Non volatility. Partition names are permanent until changed, or the 
> drive upchucks.  blkid's are quite a bit more volatile and have bitten 
> me several times in now long past history.

Unless you figure out what you did wrong file system (or partition) 
UUIDs, you may be bitten by partition (or file system labels) more 
severely. Some variants:
- Blindly clone a disk without further steps to assign new UUIDs and 
accidentally plug both disks, so system may pick partition from any of 
them. E.g. sgdisk has -G, --randomize-guids (filesystem IDs are not 
affected however, so need to be changed separately)
- Random number generator is not properly initialized, so assigned UUIDs 
are not random (no real time clock, lack of entropy inside a VM or 
inside a container).

[toc] | [prev] | [next] | [standalone]

#262005

On 9/29/23 23:31, Max Nikulin wrote:
> On 30/09/2023 02:54, gene heskett wrote:
>> On 9/29/23 15:17, Andy Smith wrote:
>>> Probably, but adding a label to a *filesystem* is easy, so will
>>> that suit your needs? "man e2label" for ext* filesystems.
>>>
>> That is what I couldn't remember Andy, thanks.
> 
> In the case of GPT, partitions may have names that are independent of 
> filesystem labels. It is similar to partition UUID and filesystem UUID.
> 
>>> If not, what are you actually trying to achieve with partition
>>> names? I can't think what use they have ever been to me in several
>>> decades.
>>
>> Non volatility. Partition names are permanent until changed, or the 
>> drive upchucks.  blkid's are quite a bit more volatile and have bitten 
>> me several times in now long past history.
> 
> Unless you figure out what you did wrong file system (or partition) 
> UUIDs, you may be bitten by partition (or file system labels) more 
> severely. Some variants:

> - Blindly clone a disk without further steps to assign new UUIDs and 
> accidentally plug both disks, so system may pick partition from any of 
> them. E.g. sgdisk has -G, --randomize-guids (filesystem IDs are not 
> affected however, so need to be changed separately)

That, while possible, is highly unlikely here as I have only one rpi4b. 
And I don't have a habit of moving drives around.

> - Random number generator is not properly initialized, so assigned UUIDs 
> are not random (no real time clock, lack of entropy inside a VM or 
> inside a container).

This last s/b valid for rpi's as they have no hdwe clock, and many of 
the 3d printer drivers run inside a python venv whose isolation 
completeness seems to be suspect. It is a good way to hide python diffs 
though.

For instance and going off-topic, I'm getting bogus status data from 
klipper running on bananapi-m5's unless I exit the firefox running on 
this maschine and then restart it on a per print basis. I blame that on 
firefoxes/linux's caching though. Linux's caching is something else, If 
I make a mod to an openscad file, then resave the .3mf, I have to use 
cura's search from root of filesystem in order to be assured I actually 
get the new file and not the old, supposedly overwritten version. Then I 
have to do the same thing in mc by rescanning the directory before I 
copy the newly sliced gcode to the printer over an sshfs mount.

cura apparently uses inotify, but mc does not despite its being the 
swiss army knife of file utils. And using kde plasma here, it gets in 
the way and screws the moose by hiding the small "are you sure" 
requestor completely behind the main requestor showing where the file 
will be written to, so you have to figure out how move immovable stuff 
off it before you see it. Maddening BS but that's KDE and Ingo K. 
doesn't herd his cats all that well. KDE should not be "getting in the 
way" but it does.

All of which is not germain to this swap vs u-sd card battle.

on arm64, its seems the man pages blindly reference each other w/o 
adequately doing so in the case of swaps. Assuming a PARTLABEL has been 
applied the rest of the fstab line starting with:
PARTLABEL=partname	none	swap
with a -o priority of 1000 would look like?
Since I know the /dev/name of the partition, I've found
swapon/swapoff /dev/name
works but by PARTLABEL as above is opaque.

 From the zram0 name for swap by default, I'm assuming that is stolen 
from the limited dram the pi has, which seems a bit circular, so once 
this PARTLABEL is working, how do I delete that zram0 since it is not 
included in fstab?

Thanks Andy. Take care & stay well.

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#261984

On 2023-09-29, Andy Smith wrote:

> If not, what are you actually trying to achieve with partition
> names? I can't think what use they have ever been to me in several
> decades.

I use label to mount different USB devices with one fstab entry.

[toc] | [prev] | [next] | [standalone]

#261985

Hi Michel,

On Fri, Sep 29, 2023 at 10:14:59PM +0200, Michel Verdier wrote:
> On 2023-09-29, Andy Smith wrote:
> > If not, what are you actually trying to achieve with partition
> > names? I can't think what use they have ever been to me in several
> > decades.
> 
> I use label to mount different USB devices with one fstab entry.

Isn't that just a filesystem label not a partition label?

If you do mean a partition label, can you elaborate as to what the
use case is and why a filesystem label doesn't work for it? I'm sure
there must be one, it's just I haven't personally encountered it.

(That's what I was asking Gene, which Gene now seems to have
clarified that he meant filesystem label)

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [next] | [standalone]

#261987

On 2023-09-29, Andy Smith wrote:

> Isn't that just a filesystem label not a partition label?

Yes you're right I use fs label.

> If you do mean a partition label, can you elaborate as to what the
> use case is and why a filesystem label doesn't work for it? I'm sure
> there must be one, it's just I haven't personally encountered it.

Perhaps for doing the same but with crypt partition ? In this case I
suppose the fs label is not readable without decrypting partition.

[toc] | [prev] | [next] | [standalone]

#261990

> If you do mean a partition label, can you elaborate as to what the
> use case is and why a filesystem label doesn't work for it? I'm sure

FWIW, I use "partition" labels (more specifically LVM names) because
they have the advantage of working the same no matter what the partition
holds, so I don't need to remember which command to use for
which filesystem.


        Stefan

[toc] | [prev] | [next] | [standalone]

#261991

Hello,

On Fri, Sep 29, 2023 at 06:01:09PM -0400, Stefan Monnier wrote:
> > If you do mean a partition label, can you elaborate as to what the
> > use case is and why a filesystem label doesn't work for it? I'm sure
> 
> FWIW, I use "partition" labels (more specifically LVM names) because
> they have the advantage of working the same no matter what the partition
> holds, so I don't need to remember which command to use for
> which filesystem.

Sorry, being familiar both with partition labels, and LVM, I don't
know what an "LVM name" is in relation to a partition label. Can you
elaborate?

In my understanding, an LVM name is just the name of an LVM device
like /dev/vgname/lvname whereas a partition label specifically is an
attribute of a GPT partition entry:

    https://gparted.org/display-doc.php?name=help-manual#gparted-name-partition

So in my understanding, these things are not equivalent concepts.

As evidenced by this thread lots of people confuse partition
names/labels for filesystem labels, even though they are distinct
things, which was why I asked Gene if he really meant a partition
label when he wrote that.

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [next] | [standalone]

#261998

On 9/29/23 20:05, Andy Smith wrote:
> Hello,
> 
> On Fri, Sep 29, 2023 at 06:01:09PM -0400, Stefan Monnier wrote:
>>> If you do mean a partition label, can you elaborate as to what the
>>> use case is and why a filesystem label doesn't work for it? I'm sure
>>
>> FWIW, I use "partition" labels (more specifically LVM names) because
>> they have the advantage of working the same no matter what the partition
>> holds, so I don't need to remember which command to use for
>> which filesystem.
> 
> Sorry, being familiar both with partition labels, and LVM, I don't
> know what an "LVM name" is in relation to a partition label. Can you
> elaborate?
> 
> In my understanding, an LVM name is just the name of an LVM device
> like /dev/vgname/lvname whereas a partition label specifically is an
> attribute of a GPT partition entry:
> 
>      https://gparted.org/display-doc.php?name=help-manual#gparted-name-partition
> 
> So in my understanding, these things are not equivalent concepts.
> 
> As evidenced by this thread lots of people confuse partition
> names/labels for filesystem labels, even though they are distinct
> things, which was why I asked Gene if he really meant a partition
> label when he wrote that.
> 
Yes I did Andy.
> Thanks,
> Andy
> 

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#262000

Hello,

On Sat, Sep 30, 2023 at 03:28:09AM -0400, gene heskett wrote:
> On 9/29/23 20:05, Andy Smith wrote:
> > As evidenced by this thread lots of people confuse partition
> > names/labels for filesystem labels, even though they are distinct
> > things, which was why I asked Gene if he really meant a partition
> > label when he wrote that.
> > 
> Yes I did Andy.

In your earlier reply you said you actually meant filesystem label,
and that your query was answered with e2label (which works with
filesystem labels on ext* filesystems).

So no, when you previously said "partition label" you actually meant
"filesystem lanel".

Thanks,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

[toc] | [prev] | [next] | [standalone]

#262006

On 9/30/23 07:27, Andy Smith wrote:
> Hello,
> 
> On Sat, Sep 30, 2023 at 03:28:09AM -0400, gene heskett wrote:
>> On 9/29/23 20:05, Andy Smith wrote:
>>> As evidenced by this thread lots of people confuse partition
>>> names/labels for filesystem labels, even though they are distinct
>>> things, which was why I asked Gene if he really meant a partition
>>> label when he wrote that.
>>>
>> Yes I did Andy.
> 
> In your earlier reply you said you actually meant filesystem label,
> and that your query was answered with e2label (which works with
> filesystem labels on ext* filesystems).
> 
> So no, when you previously said "partition label" you actually meant
> "filesystem lanel".
> 
I assume you meant "label", Andy ;o)

Which leads to a question:

I used gparted to apply the labels.
And I could only apply then if the partition was not mounted.

So what is the proper definition of such a label that gparted applies? 
filesystem or partition?

Its seems to point (to me anyway) as two different methods, and 
therefore is in different locations in the medium. If so, how is the 
difference determined?

Inquiring minds and all that nonsense... ;o)>


> Thanks,
> Andy
> 

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#262017

On Sat 30 Sep 2023 at 09:51:35 (-0400), gene heskett wrote:
> On 9/30/23 07:27, Andy Smith wrote:
> > On Sat, Sep 30, 2023 at 03:28:09AM -0400, gene heskett wrote:
> > > On 9/29/23 20:05, Andy Smith wrote:
> > > > As evidenced by this thread lots of people confuse partition
> > > > names/labels for filesystem labels, even though they are distinct
> > > > things, which was why I asked Gene if he really meant a partition
> > > > label when he wrote that.
> > > > 
> > > Yes I did Andy.
> > 
> > In your earlier reply you said you actually meant filesystem label,
> > and that your query was answered with e2label (which works with
> > filesystem labels on ext* filesystems).
> > 
> > So no, when you previously said "partition label" you actually meant
> > "filesystem lanel".
> > 
> I assume you meant "label", Andy ;o)
> 
> Which leads to a question:
> 
> I used gparted to apply the labels.
> And I could only apply then if the partition was not mounted.
> 
> So what is the proper definition of such a label that gparted applies?
> filesystem or partition?
> 
> Its seems to point (to me anyway) as two different methods, and
> therefore is in different locations in the medium. If so, how is the
> difference determined?

Partitions on GPT disks have Names≡Labels and UUIDs, sometimes
referred to as PARTLABELs and PARTUUIDs.

Filesystems have their own Labels and UUIDs, but what they're called
may vary by the type of filesystem, and also by the programs you're
using to manipulate or list them.

But you also seem to use the names of those programs (like blkid) or
their functionality (like gparted's) to refer to all these properties,
which might be why you get them mixed up.

You can see all the Names and Labels on your filesystems by typing:

  $ ls -lR /dev/disk/

where the partitions are under /dev/disk/by-partlabel and
/dev/disk/by-partuuid, and the filesystems under /dev/disk/by-label
and /dev/disk/by-uuid. These symlinks point to the kernel's device
names.

Note that filesystem LABELs on encrypted ext filesystems won't be
seen unless they're unlocked, though the UUIDs are.

BTW the inability of gparted to apply partition labels while their
filesystems are mounted is self-inflicted. (Presumably, the fields
are 'greyed out'.) They can be written/changed, but you may be left
in a confusing state where the kernel and various programs are using
different values, which may or may not matter. Rebooting will solve
this, or you can run partprobe or kpartx, neither of which have I tried.
(I'm not advising this, of course.)

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#262023

On 9/30/23 14:16, David Wright wrote:
> On Sat 30 Sep 2023 at 09:51:35 (-0400), gene heskett wrote:
>> On 9/30/23 07:27, Andy Smith wrote:
>>> On Sat, Sep 30, 2023 at 03:28:09AM -0400, gene heskett wrote:
>>>> On 9/29/23 20:05, Andy Smith wrote:
>>>>> As evidenced by this thread lots of people confuse partition
>>>>> names/labels for filesystem labels, even though they are distinct
>>>>> things, which was why I asked Gene if he really meant a partition
>>>>> label when he wrote that.
>>>>>
>>>> Yes I did Andy.
>>>
>>> In your earlier reply you said you actually meant filesystem label,
>>> and that your query was answered with e2label (which works with
>>> filesystem labels on ext* filesystems).
>>>
>>> So no, when you previously said "partition label" you actually meant
>>> "filesystem lanel".
>>>
>> I assume you meant "label", Andy ;o)
>>
>> Which leads to a question:
>>
>> I used gparted to apply the labels.
>> And I could only apply then if the partition was not mounted.
>>
>> So what is the proper definition of such a label that gparted applies?
>> filesystem or partition?
>>
>> Its seems to point (to me anyway) as two different methods, and
>> therefore is in different locations in the medium. If so, how is the
>> difference determined?
> 
> Partitions on GPT disks have Names≡Labels and UUIDs, sometimes
> referred to as PARTLABELs and PARTUUIDs.
> 
> Filesystems have their own Labels and UUIDs, but what they're called
> may vary by the type of filesystem, and also by the programs you're
> using to manipulate or list them.
> 
> But you also seem to use the names of those programs (like blkid) or
> their functionality (like gparted's) to refer to all these properties,
> which might be why you get them mixed up.
> 
> You can see all the Names and Labels on your filesystems by typing:
> 
>    $ ls -lR /dev/disk/
> 
> where the partitions are under /dev/disk/by-partlabel and
> /dev/disk/by-partuuid, and the filesystems under /dev/disk/by-label
> and /dev/disk/by-uuid. These symlinks point to the kernel's device
> names.
> 
> Note that filesystem LABELs on encrypted ext filesystems won't be
> seen unless they're unlocked, though the UUIDs are.
> 
> BTW the inability of gparted to apply partition labels while their
> filesystems are mounted is self-inflicted. (Presumably, the fields
> are 'greyed out'.) They can be written/changed, but you may be left
> in a confusing state where the kernel and various programs are using
> different values, which may or may not matter. Rebooting will solve
> this, or you can run partprobe or kpartx, neither of which have I tried.
> (I'm not advising this, of course.)
> 
> Cheers,
> David.

Very informative David, thank you.  Take care & stay well.
> .

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

[toc] | [prev] | [next] | [standalone]

#262008

>> > If you do mean a partition label, can you elaborate as to what the
>> > use case is and why a filesystem label doesn't work for it? I'm sure
>> 
>> FWIW, I use "partition" labels (more specifically LVM names) because
>> they have the advantage of working the same no matter what the partition
>> holds, so I don't need to remember which command to use for
>> which filesystem.
>
> Sorry, being familiar both with partition labels, and LVM, I don't
> know what an "LVM name" is in relation to a partition label. Can you
> elaborate?
>
> In my understanding, an LVM name is just the name of an LVM device
> like /dev/vgname/lvname whereas a partition label specifically is an
> attribute of a GPT partition entry:

That's right.  LVM volumes are named, always (not even sure if you cn
keep them anonymous), so in this sense it's a bit different from
partition names since partitions usually are left unnamed (I don't
think MBR partitions can even have names).

But other than that, an LVM volume name is just "an attribute of an LVM
volume entry" the same way a partition label is "an attribute of
a GPT partition entry".

> So in my understanding, these things are not equivalent concepts.

I usually give my whole drive to LVM and then split it into LVM volumes,
just like other people give their whole drives to GPT and then split
them into GPT partitions.  Then giving names to those things works
pretty much the same way and with very similar meaning.

> As evidenced by this thread lots of people confuse partition
> names/labels for filesystem labels, even though they are distinct
> things, which was why I asked Gene if he really meant a partition
> label when he wrote that.

Yes, filesystem labels are a different beast because they're stored
inside the partition.  The allowed format of that label, where it's
stored within the data, and hence how to read/write it is different for
every filesystem, so it's a big mess.  You can't even apply a filesystem
label to a partition that doesn't hold a filesystem, for example.

AFAIK filesystem labels are ugly hacks introduced to workaround the
fact that the MBR partition-table format did not allow giving names to
the partitions themselves.  Nowadays you don't need these ugly hacks
because LVM and GPT fixed the original problem.


        Stefan

[toc] | [prev] | [next] | [standalone]

#262019

On Sat 30 Sep 2023 at 11:13:36 (-0400), Stefan Monnier wrote:

> Yes, filesystem labels are a different beast because they're stored
> inside the partition.  The allowed format of that label, where it's
> stored within the data, and hence how to read/write it is different for
> every filesystem, so it's a big mess.  You can't even apply a filesystem
> label to a partition that doesn't hold a filesystem, for example.

Well, no, by definition. But, FTR, you can apply LABELs and UUIDs to
linux swap partitions even though they don't contain filesystems.
You just don't call then /filesystem/ LABELs and UUIDs.

Swap LABELs were very useful if you shared swap partitions between
different linux installations. When the debian-installer formats the
shared swap, you can immediately restore its LABEL. The new
installation will refer to the swap by its UUID until you get round to
updating the /etc/fstab, but should you reboot to one of the other
installations, their reference to swap by LABEL will still work.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#261993

On Fri 29 Sep 2023 at 20:32:23 (+0000), Andy Smith wrote:
> On Fri, Sep 29, 2023 at 10:14:59PM +0200, Michel Verdier wrote:
> > On 2023-09-29, Andy Smith wrote:
> > > If not, what are you actually trying to achieve with partition
> > > names? I can't think what use they have ever been to me in several
> > > decades.
> > 
> > I use label to mount different USB devices with one fstab entry.
> 
> Isn't that just a filesystem label not a partition label?
> 
> If you do mean a partition label, can you elaborate as to what the
> use case is and why a filesystem label doesn't work for it? I'm sure
> there must be one, it's just I haven't personally encountered it.

As well as the aforementioned case of finding encrypted partitions to
unlock, the d-i installer's partitioner displays PARTLABELs when set.

I've never got around to testing whether devices like cameras can
handle GPT SD cards, and whether PARTLABELs are more robust than
filesystem LABELs when a device suddenly decides to reformat the card.

As for the name, I think "Partition Name" is the commonest term,
though, as here, I usually write PARTLABEL because it seems the most
distinguishable from a filesystem LABEL. (See man fstab and man mount.)

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | linux.debian.user

csiph-web