Bug 1371755 - KDE-PartitionManager fails to Check File System because it gets auto-mounted
Summary: KDE-PartitionManager fails to Check File System because it gets auto-mounted
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-partitionmanager
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mattia Verga
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-31 02:55 UTC by bob
Modified: 2017-07-15 08:48 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-07-15 08:48:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
KDE Software Compilation 368175 0 None None None 2016-09-03 07:26:49 UTC

Description bob 2016-08-31 02:55:23 UTC
Description of problem:

Using KDE partition manager to create partition and format entire drive as single partition using ext4.  (these are the default values).  The procedure involves selecting two tasks to be performed: erasing the existing partition and then creating the new one.  Upon clicking "Apply" everything goes as expected, including creation of the partition, but the file system verification step fails.

Specifically, after creating the partition and setting the file partition label, the next task is to check the file system using the following command:

e2fsck -f -y -v /dev/sda1

The e2fsck FAILS, issuing a "/dev/sda1 already mounted" error.

This event occurs because the Device Notifier pop-up in KDE has recogized the volume as available, and auto-mounts it, before partition-manager is able to finish it's task.


Version-Release number of selected component (if applicable):

F24 new install.


How reproducible:

Every time that I try to use KDE-partitionmanager to format a new drive.

Steps to Reproduce:
1. Select new drive with no file system
2. Select default values to install a non-encrypted ext4 file system.
3. Apply selection

Actual results:

fsck step fails because system auto-mounts the drive before fsck is initiated.

Expected results:

system should not auto-mount drive before kde-pm has finished it's task.

Additional info:

KDE Partition Manager: SMART Status Report
Date: 	8/30/16 9:45 PM
Program version: 	2.2.0
Backend: 	pmlibpartedbackendplugin (1)
KDE Frameworks version: 	5.22.0
Machine: 	Linux colossus.346net 4.6.6-300.fc24.x86_64 #1 SMP Wed Aug 10 21:07:35 UTC 2016 x86_64

Create a new partition (3.64 TiB, ext4) on ‘/dev/sda’
Job: Create new partition on device ‘/dev/sda’
Create new partition ‘/dev/sda1’: Success
Job: Create file system ‘ext4’ on partition ‘/dev/sda1’
Command: mkfs.ext4 -qF /dev/sda1
Create file system ‘ext4’ on partition ‘/dev/sda1’: Success
Job: Set the file system label on partition ‘/dev/sda1’ to "backup-02"
Command: e2label /dev/sda1 backup-02
Set the file system label on partition ‘/dev/sda1’ to "backup-02": Success
Job: Check file system on partition ‘/dev/sda1’
Command: e2fsck -f -y -v /dev/sda1

e2fsck 1.42.13 (17-May-2015)
/dev/sda1 is mounted.
e2fsck: Cannot continue, aborting.



Check file system on partition ‘/dev/sda1’: Error
Create a new partition (3.64 TiB, ext4) on ‘/dev/sda’: Error

Comment 1 Mattia Verga 2016-09-02 11:53:57 UTC
Can you please check if you have "Enable automatic mounting of removable media" selected in KDE System Settings -> Removable devices?

Comment 2 bob 2016-09-02 19:16:43 UTC
Yes it is checked.  I have changed none of these settings from their default values.  No devices are overridden.

Comment 3 Mattia Verga 2017-07-15 08:48:40 UTC
This is now fixed in kpmcore 3.1.1 / kde-partitionmanager 3.1.0 available in rawhide (F27)


Note You need to log in before you can comment on or make changes to this bug.