Is there any reason why new version of cfdisk on os 13.2 does not show anymore the partition label?
This is very sad. Is there an other partitioning tool which will show the labels?
The other problem is that if you have an old disk with an extended fs and it is not using the whole disk you cannot
create a new logical partition which until os 13.1 this was no problem…
A very bad incompatibility
And last but not least if you create partitions with cfdisk they are bad aligned for old systems …
Old cfdisk comes from util-linux 2.21 and new one from util-linx-2.25…
You tell a lot, but you show nothing. People want to see the commands and the output you get so they can make their own conclusions. so please show us the computer facts by copy/paste of prompt, command, output and next prompt and do so between CODE tags (the # button in the tool bar of the post editor).
BTW, I changed the title of the thread you correct your openSUSE version from 13.3 to 13.2.
2.25 changed the layout considerably from the old versions. It’s supposed to be a “user friendly basic partitioning utility”, so they must’ve felt that things like labels on a Linux system are meaningless.
Since cfdisk is maintained by some RedHat guys, you should opt to send them your feedback.
Wau
I thinsk we going to win now if you think this is user friendly …
Disk: /dev/sdb
Size: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Label: dos, identifier: 0x24a43ff0
Device Boot Start End Sectors Size Id Type
>> /dev/sdb1 2048 10487807 10485760 5G 83 Linux
/dev/sdb2 10487808 115345407 104857600 50G 7 HPFS/NTFS/exFAT
/dev/sdb3 115345408 1953525167 1838179760 876.5G 5 Extended
├─/dev/sdb5 115347456 136318975 20971520 10G 83 Linux
├─/dev/sdb6 136321024 209721343 73400320 35G 83 Linux
├─/dev/sdb7 209723392 272637951 62914560 30G 83 Linux
├─/dev/sdb8 272640000 377497599 104857600 50G 83 Linux
├─/dev/sdb9 377499648 587214847 209715200 100G 83 Linux
├─/dev/sdb10 587216896 629159935 41943040 20G 83 Linux
├─/dev/sdb11 629161984 734019583 104857600 50G 83 Linux
├─/dev/sdb12 734021632 943736831 209715200 100G 83 Linux
├─/dev/sdb13 943738880 1572884479 629145600 300G 83 Linux
├─/dev/sdb14 1572886528 1887459327 314572800 150G 83 Linux
└─/dev/sdb15 1887459391 1953525167 66065777 31.5G 83 Linux
This was before this version and thans god that old binary works on the new system…
cfdisk (util-linux 2.21.2)
Disk Drive: /dev/sdb
Size: 1000204886016 bytes, 1000.2 GB
Heads: 255 Sectors per Track: 63 Cylinders: 121601
Name Flags Part Type FS Type [Label] Size (MB)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Primary Free Space 1.05 *
sdb1 Primary ext4 [Boot] 5368.71 *
sdb2 Primary ntfs [Data] 53687.10 *
sdb5 NC Logical swap [Swap] 10738.47 *
sdb6 NC Logical ext4 [OS_12_3] 37582.02 *
sdb7 NC Logical ext4 [UsrLocal] 32213.31 *
sdb8 NC Logical ext4 [Home] 53688.14 *
sdb9 NC Logical ext4 [UsrLocalScratch] 107375.24 *
sdb10 NC Logical ext4 [Shared] 21475.89 *
sdb11 NC Logical crypto_LUKS 53688.14 *
sdb12 NC Logical crypto_LUKS 107375.24 *
sdb13 NC Logical ext4 [Multimedia] 322123.60 *
sdb14 NC Logical ext4 [VirtualBox] 161062.33 *
sdb15 Logical ext4 [OS_13_2] 33825.72 *
Only to show you the difference I know you are not the author, noe the maintainer 
I don’t want to hear the cry of a person who deleted the wrong partition if you have about 20 partitions on a server…
This layout is my laptop not server …
Greetings
I think it is because they wanted to make it really, really simple - what cfdisk is meant to be.
My quote was from their man page;
Note that cfdisk provides basic partitioning functionality with a user-friendly interface. If you need advanced features, use fdisk(8) instead.
I guess they wanted to make it really basic and simple.
They might be interested in feedback, send them a mail. The maintainer is listed in the man page at the very bottom.
If cfdisk was the only partitioner around you may have a good excuse for a rant. But there are so many other from dead simple to super complex. A tool for every need. You can use fdisk which is old school or gparted a nice GUI
fdisk suffers from same. No labels are printed…
Make things as simple as possible, but not simpler 
Will post a feedback…
No, fdisk is a pure partitioning tool. It does not touch (read nor write) inside partitions, it only creates/changes the partition table (and the extensions of it in the extended partition).
The labels you are talking about are Volume Labels. They are inside the partition and are part of the structure that is occupying the partitions. In general there are file systems there. Thus a Volume Label is part of the file system. And it depends on the file system type if, how and where it resides inside the file system. You set it with tools specific for the file system (like mke2fs at creation of an ext2/3/4 file system, or tune2fs for changing an existing one). And any program that wants to read (or change) such a label must have “knowledge” about every single file system type regarding where that label is stored.
There are higher level programs (often with a GUI) that combine partitioning and file system management in one (like YaST > System > Partitioning). These tools ar generally known as partitioning tools, but they can do much more then just partitioning and this wording is confusing. These tools generally know how to label (and read the label) of the file system types they can manage.
Apparently (see posts above) the developers of cfdisk decided that it should be a pure partitioning tool like fdisk.
This functionality is back post 2.26:
commit dda7fe12acff6613f23c67de15905848b7521767
Author: Ondrej Oprala <ooprala@redhat.com>
Date: Fri Feb 20 09:41:19 2015 +0100
cfdisk: provide extra partinfo with "x"
The new 'extra' info provides:
* filesystem information from libblkid (TYPE, UUID, LABEL)
This feature is based on libblkid ability to probe specified area
on the device. It allows to probe for filesystems although the
partition devices (e.g. /dev/sda2) does not exist. For example from
disk image:
# cfdisk /home/archive/fs-images/disk.img
* additional information from libfdisk (partition UUID, Name, ...)
* mount information from libmount (from fstab or mountinfo)