Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2058506 - Nothing pulls in ntfs-3g anymore...
Summary: Nothing pulls in ntfs-3g anymore...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: udisks2
Version: 35
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: CockpitTest
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-25 07:37 UTC by Marius Vollmer
Modified: 2022-08-24 09:26 UTC (History)
5 users (show)

Fixed In Version: udisks2-2.9.4-4.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-26 15:09:12 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Marius Vollmer 2022-02-25 07:37:15 UTC 
Description of problem:

Our CI images are missing ntfs-3g, and consequently mounting NTFS filesystems no longer work.  Ntfsprogs is still installed and thus UDisks2 reports that it can format NTFS filesystems, but what good is that if you can't mount them?

There is bug 2001755 which was about ntfs-3g not being installable. That has been fixed and I can install ntfs-3g just fine.  This report here is about figuring out who would be responsible for pulling it in.

I have no good answers myself, I just observe that ntfs-3g used to be installed and Cockpit could mount the NTFS filesystems that it creates, and now it is no longer installed.

UDisks2 requires ntfsprogs. Should it maybe also require ntfs-3g?

I'd say from Cockpits point of view, listing a filesystem in the "Format" dialog means that it can be both created _and_ mounted.  Should UDisks2 maybe add a "CanMount" function?

Version-Release number of selected component (if applicable):
udisks2-2.9.4-1.fc35.x86_64
ntfsprogs-2021.8.22-2.fc35.x86_64
ntfs-3g-2021.8.22-2.fc35.x86_64

How reproducible:
Always
Comment 1 Tomáš Bžatek 2022-03-03 16:42:49 UTC 
Yes, I think udisks should require ntfs-3g as it's a preferred way of mounting ntfs filesystems. I've added explicit Requires.

While ntfs3 support is a known issue upstream, there's a non-trivial amount of work needed to support all of its specifics. I expect we could get rid of ntfs-3g sometime in Fedora 38 timeframe.

Related to that, it's incredibly difficult to give an authoritative answer whether a particular filesystem type can be mounted. There's some hidden magic with userspace mount helpers and I think even for a dry mount a block device is needed. UDisks generally doesn't restrict type of filesystem for mounting, it's up to the system to return an error on the way. So any kind of "CanMount" function would only work as a best guess only and sticking to it might do more harm. I totally agree it would be a great addition, but I have no idea for the moment how to make it reliable. The problem with ntfs(3) is that we don't exactly know what driver or userspace helper would be actually used and what set of mount options does it respect.
Comment 2 Fedora Update System 2022-03-03 16:43:49 UTC 
FEDORA-2022-06ad800b21 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-06ad800b21
Comment 3 Fedora Update System 2022-03-03 23:54:32 UTC 
FEDORA-2022-06ad800b21 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-06ad800b21`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-06ad800b21

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Marius Vollmer 2022-03-04 07:40:50 UTC 
Thank you!
Comment 5 Fedora Update System 2022-03-26 15:09:12 UTC 
FEDORA-2022-06ad800b21 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.