Bug 197625 - Block devices that do not have partitions are not treated properly
Summary: Block devices that do not have partitions are not treated properly
Status: RESOLVED LATER
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (show other bugs)
Version: 1.0.0-BETA3
Platform: Debian unstable Linux
: NOR wishlist
Target Milestone: ---
Assignee: Volker Lanz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-23 17:42 UTC by George Kiagiadakis
Modified: 2016-02-22 15:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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.