3

I want to modify its label, as I've been able to beforehand:

Screenshot

However, when I attempt to, it fails:

Backend:    pmsfdiskbackendplugin (1)

Set label for partition ‘/dev/nvme3n1p1’ from "s2ve9g" to "{ Name: Microsoft Reserved, Identifier: SXSWLI } #.img"
Job: Set the file system label on partition ‘/dev/nvme3n1p1’ to "{ Name: Microsoft Reserved, Identifier: SXSWLI } #.img"
Command: btrfs filesystem label /dev/nvme3n1p1 { Name: Microsoft Reserved, Identifier: SXSWLI } #.img
Set the file system label on partition ‘/dev/nvme3n1p1’ to "{ Name: Microsoft Reserved, Identifier: SXSWLI } #.img": Error
Set label for partition ‘/dev/nvme3n1p1’ from "s2ve9g" to "{ Name: Microsoft Reserved, Identifier: SXSWLI } #.img": Error

Were it not configurable, the aforedepicted kde-partitionmanager-25.04.2-1.fc42 would usually disable the field, like the undermentioned example's "Flags", etcetera:

Screenshot

I have no intention to rename its partition name, because it's predefined, and I see no information online about whether that's safe. In fact, all I've located is answers.microsoft.com/en-us/windows/forum/all/renaming-system-reserved-partition/d86489b9-4c4a-4a75-925f-f567dbf4dfaf, which is nigh useless. However, I'll be glad to hear whether I can. superuser.com/a/1099292 explains the difference between the label and partition name.

Environment

lsblk -f returns:

NAME       FSTYPE FSVER LABEL  UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
nvme3n1p1  btrfs        s2ve9g 17c0335b-73c9-45b1-aabe-f62a6e633d98
RokeJulianLockhart
  • 887

1 Answers1

3

"Label" is filesystem-specific; for a partition containing Btrfs it would be stored in the Btrfs header (superblock), and so on.

It's the field that Windows displays in e.g. 'Computer' for recognized volumes, but – because it is filesystem-specific – unless you've installed the WinBtrfs driver, Windows won't even be able to read it in the first place.

Either way, Windows does not care about the specific value of the filesystem label; not even for boot purposes. (Though I think Win95/98 might have cared?)

It can be used from within Linux as LABEL= or /dev/disk/by-label/, but mostly in manual configuration (I don't think I've seen OS installers use it in /etc/fstab or anywhere, and either way they shouldn't; the filesystem UUID or partition GUID are preferred).

"Partition Name" is stored as part of the GPT partition table entry, common to all partition types. It is specifically meant to be a user-modifiable "human-readable name" field.

It is not used nor displayed by Windows, though it sets default names for new partitions.

It can be used from within Linux as PARTLABEL= or /dev/disk/by-partlabel/, but generally only in manual configuration when the system admin really wants to – not something that an installer ought to set up.

Half of the "Flags" are a lie invented by GParted (and it seems that KDE Partition Manager gets them from libparted). The 'boot' flag, for example, is not stored as an actual flag in a GPT partition table – instead it sets a specific value for the "Partition type GUID" field (which is not directly shown by the program).

"Partition type GUID" (not shown by your program) is how Windows actually distinguishes its "reserved space" partition, its "OS/user data" partitions, and other types.

grawity
  • 501,077