Bug 2012568

Summary: pmount fails to mount exfat partitions
Product: [Fedora] Fedora Reporter: Alexander Gromnitsky <alexander.gromnitsky>
Component: pmountAssignee: Pavel Alexeev <pahan>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: hobbes1069, pahan, zonexpertconsulting
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pmount-0.9.23-22.fc34 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-25 19:36:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
add exfat support for pmount none

Description Alexander Gromnitsky 2021-10-10 10:34:10 UTC
Created attachment 1831442 [details]
add exfat support for pmount

Description of problem:

the list of supported fs is hard-coded in pmount, with no exfat in the list

How reproducible:

always

Steps to Reproduce:
1. format a flash drive in Windows as 'exfat'
2. run `pmount /dev/sdb1` in Fedora

Actual results:

$ pmount /dev/sdb1
NTFS signature is missing.
Failed to mount '/dev/sdb1': Invalid argument
The device '/dev/sdb1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
NTFS signature is missing.
Failed to mount '/dev/sdb1': Invalid argument
The device '/dev/sdb1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

Expected results:

a successful mount in /media/sdb1

Additional info:

see the attachment for a patch

Comment 1 Andrew Bauer 2021-10-12 13:59:55 UTC
I am not the admin maintainer for this package, but I think I have commit access to the Fedora branches.

For completeness, is this where you got the patch from?
https://bugs.launchpad.net/ubuntu/+source/pmount/+bug/1524523

Comment 2 Fedora Update System 2021-10-12 15:11:57 UTC
FEDORA-2021-70559dc02c has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-70559dc02c

Comment 4 Fedora Update System 2021-10-12 23:44:23 UTC
FEDORA-2021-70559dc02c has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-70559dc02c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-70559dc02c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2021-10-20 19:23:02 UTC
FEDORA-2021-70559dc02c has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 6 Alexander Gromnitsky 2022-07-06 13:42:34 UTC
this should be modified to reflect the changes in kernel > 5.4 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=907fa893258ba6076f5fff32900a461decb9e8c5), otherwise no exfat mounting will occur

the new patch was tested on f36:

diff --git a/pmount.exfat.patch b/pmount.exfat.patch
index 90abf5d..296c51b 100644
--- a/pmount.exfat.patch
+++ b/pmount.exfat.patch
@@ -4,7 +4,7 @@
      { "iso9660", "nosuid,nodev,user", 1, NULL, ",iocharset=%s" },
      { "vfat", "nosuid,nodev,user,quiet,shortname=mixed", 1, "077", 
        ",iocharset=%s",",fmask=%04o,dmask=%04o"},
-+    { "exfat", "nosuid,nodev,user,quiet,nonempty", 1, "077", ",iocharset=%s",",fmask=%04o,dmask=%04o"},
++    { "exfat", "nosuid,nodev,user", 1, "077", ",iocharset=%s",",fmask=%04o,dmask=%04o"},
      { "hfsplus", "nosuid,nodev,user", 1, NULL, 0 },
      { "hfs", "nosuid,nodev,user", 1, "077", NULL, 
        ",file_umask=%04o,dir_umask=%04o"},
diff --git a/pmount.spec b/pmount.spec
index eb96712..f59584d 100644
--- a/pmount.spec
+++ b/pmount.spec
@@ -1,5 +1,4 @@
 %global _hardened_build 1
-%define download_dir 3310
 
 Name:           pmount
 Version:        0.9.23
@@ -8,9 +7,9 @@ Summary:        Enable normal user mount
 
 # realpath.c is GPLv2+. Others are GPL+;
 License:        GPLv2+
-URL:            http://pmount.alioth.debian.org/
+URL:            https://wiki.debian.org/pmount
 # BEWARE: The number in the url determines the content, ahs to be updated each time.
-Source0:        http://alioth.debian.org/frs/download.php/%{download_dir}/%{name}-%{version}.tar.bz2
+Source0:        https://deb.debian.org/debian/pool/main/p/pmount/pmount_%{version}.orig.tar.bz2
 # don't set the setuid bits during make install
 Patch0:         pmount-0.9.17-nosetuid.patch
 # Add exfat support

Comment 7 Ben Cotton 2023-04-25 18:27:17 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 8 Ludek Smid 2023-05-25 19:36:47 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.