Bug 26344 - Automount in (at least XFCE) of exfat device fail since kernel 5.5.9
Summary: Automount in (at least XFCE) of exfat device fail since kernel 5.5.9
Status: RESOLVED DUPLICATE of bug 26396
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: https://www.mageialinux-online.org/fo...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-03-15 23:12 CET by Nicolas Nicolas
Modified: 2020-04-05 19:53 CEST (History)
4 users (show)

See Also:
Source RPM: kernel-desktop-5.5.9-1.mga7-1-1.mga7
CVE:
Status comment:


Attachments

Description Nicolas Nicolas 2020-03-15 23:12:55 CET
Hello,

Note: don't have exfat device to test.

It was reported in French MLO forum, that mounting exfat device fail in 5.5.9 kernel.

When user connect exfat device in Xfce, it no more automount.

It fail with the following message.

type de système de fichiers « exfat » inconnu. ( unknown exfat file system)

When booting under the 5.5.6 version of kernel, the mounting is working as expected.

It appears that exfat driver has changed of location between between the 2 kernel (from staging folder to fs folder) .

$locate exfat | grep modules
/usr/lib/modules/5.5.6-desktop-2.mga7/kernel/drivers/staging/exfat
/usr/lib/modules/5.5.6-desktop-2.mga7/kernel/drivers/staging/exfat/exfat.ko.xz
/usr/lib/modules/5.5.9-desktop-1.mga7/kernel/fs/exfat
/usr/lib/modules/5.5.9-desktop-1.mga7/kernel/fs/exfat/exfat.ko.xz

User also reports the following trace in the kernel:

mars 15 16:51:40 localhost kernel: sdb: sdb1
mars 15 16:51:40 localhost kernel: sd 2:0:0:0: [sdb] Attached SCSI disk
mars 15 16:51:40 localhost systemd-udevd[3580]: Process 'ata_id --export /dev/sdb' failed with exit code 2.
mars 15 16:51:40 localhost systemd-udevd[3580]: Process 'udisks-probe-ata-smart /dev/sdb' failed with exit code 1.
mars 15 16:51:45 localhost kernel: exfat: Unknown parameter 'namecase' 

Device can be mounted is a manual way.
Comment 1 Dave Hodgins 2020-03-16 00:16:48 CET
I cannot recreate the problem. Inserted a usb stick with one partition on it,
formatted as exfat using "mkfs.exfat -n red" /dev/sde1.
# blkid /dev/sde*
/dev/sde: PTUUID="40c4891b" PTTYPE="dos"
/dev/sde1: LABEL="red" UUID="D6AE-F7B5" TYPE="exfat" PTTYPE="dos" PARTUUID="40c4891b-01"

Running xfce in a newly created user (so using default settings), when I
inserted the usb stick, an icon with the label name appeared on the desktop.
Hovering the mouse over the icon showed it was not mounted yet. Clicking on
the icon, the partition was mounted, and opened in the file manager.

Only thing I can think of that might be different from defaults, is that
I added exfat to /etc/filesystems when I first installed the exfat packages.

# rpm -qa|grep exfat
fuse-exfat-1.3.0-1.mga7.tainted
exfat-utils-1.3.0-1.mga7.tainted

# grep exfat /etc/filesystems 
exfat

# uname -r
5.5.9-desktop-1.mga7

Even with the filesystem mounted, the exfat module does not show up in
/proc/modules.


# journalctl -b|grep sde
Mar 15 18:57:10 x3.hodgins.homeip.net cryptdrive[3860]: inserted sde1
Mar 15 18:57:16 x3.hodgins.homeip.net udisksd[3324]: Mounted /dev/sde1 at /run/media/tester/red on behalf of uid 1001

I also tested with the same usb stick on a second system, where I do not have
the exfat rpm packages installed, or have it listed in /etc/filesystems, and
on that system as soon as I inserted the usb stick, the file manager opened
showing the contents of the exfat file system.

Searching on the error message, shows it started with kernel 5.4 for another
user, but doesn't indicate why some people are seeing the error while others
are not.
https://bbs.archlinux.org/viewtopic.php?id=252727

So while It's clear there is a problem, I have no idea how to isolate where
the problem is, since I cannot recreate it.

CC: (none) => davidwhodgins

Comment 2 Alain Choucroot 2020-03-16 17:53:41 CET
Hello. I confirm that the issue seems to be linked with the presence of the fuse-exfat-1.3.0-1.mga7.tainted package.

I have the problem under Xfce. This is new, as it's appeared since kernel 5.5.9 . With previous kernels, (and fuse-exfat not installed), exfat32 usb keys are correctly handled.

Under 5.5.9 and fuse-exfat uninstalled, an extfat usb key is not automatically mounted when inserted. Trying to mount it via the desktop icon ends-up in a popup error ("unknown exfat file system"). Yet it can be manually mounted in a terminal via a mount command.
Still under 5.5.9, if fuse-exfat is installed, the normal behaviour is back. An exfat usb key is automatically mounted when inserted. It can also be mounted/unmounted via the desktop icon.

CC: (none) => choucroot

Comment 3 Thomas Backlund 2020-03-16 20:25:02 CET
kernel 5.5.9-1 now contains the officially sanctioned exfat driver that will be merged upstream in kernel 5.7 series

So you should not need the fuse-exfat anymore.

CC: (none) => tmb

Comment 4 Thomas Backlund 2020-03-16 20:27:58 CET
maybe the automount stuff need to learn how to handle upstream supported exfat
Comment 5 Alain Choucroot 2020-03-17 09:36:05 CET
If the automount stuff needs evolution to be compatible with next kernels, who is in charge of that feature ? Do you mean it is an XFCE issue ? Or is it deeper than just the desktop part ?
Comment 6 Dave Hodgins 2020-03-17 15:35:40 CET
As it's a kernel change that's made that fuse-exfat obsolete, shouldn't
the kernel now use a conflict to force fuse-exfat removal?
Morgan Leijström 2020-03-25 11:08:42 CET

CC: (none) => fri

Comment 7 Dave Hodgins 2020-04-05 03:52:31 CEST
Closing this report as a duplicate of bug 26396 where additional testing results
identified the the problem, which has been fixed.

The issue will be fixed for users when the kernel from bug 26434 is pushed
from core updates testing to updates.

*** This bug has been marked as a duplicate of bug 26396 ***

Resolution: (none) => DUPLICATE
Status: NEW => RESOLVED

Comment 8 Thomas Backlund 2020-04-05 19:53:28 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGASA-2020-0162.html

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