Bug 197625

Summary: Block devices that do not have partitions are not treated properly
Product: [Applications] partitionmanager Reporter: George Kiagiadakis <mail>
Component: generalAssignee: Volker Lanz <vl>
Status: RESOLVED LATER    
Severity: wishlist CC: andrius
Priority: NOR    
Version First Reported In: 1.0.0-BETA3   
Target Milestone: ---   
Platform: Debian unstable   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description George Kiagiadakis 2009-06-23 17:42:39 UTC 
Hi,
I am an LVM user and I have several LVM block devices on /dev/mapper/. I use most of them without a partition table inside them, so they just contain a filesystem and nothing more. Partitionmanager displays all of them in the list of devices, but in the main widget it treats the devices as if they had partitions, so it appends the number 1 to the name of the device, which results in an unknown device. For example, /dev/mapper/gkserver-home is displayed as /dev/mapper/gkserver-home1. As a result, all operations on this filesystem are impossible. For some reason it is able to detect correctly the filesystem, but not the label (for example, on ext3 the label takes the name "/sbin/e2label: No such file or directory while trying to open /dev/mapper/gkserver-home1 Couldn't find valid filesystem superblock.")

Note: This happens with all versions I have tried, including beta3.
Comment 1 Andrius Štikonas 2016-02-22 15:19:59 UTC 
LVM (RAID, etc) block devices are not supported now. Hopefully at some point we will implement support but there is already another wishlist bug for that.