Bug 412145

Summary: Dolphin is not aware of unclean mount on exfat
Product: [Applications] dolphin Reporter: Brennan Kinney <polarathene-signup>
Component: generalAssignee: Dolphin Bug Assignee <dolphin-bugs-null>
Status: REPORTED ---    
Severity: normal CC: kfm-devel, nate, polarathene-signup, postix
Priority: NOR    
Version: 19.08.0   
Target Milestone: ---   
Platform: Manjaro   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Brennan Kinney 2019-09-21 05:14:57 UTC 
SUMMARY

When accessing a USB stick formatted with exfat(in a dirty state) via dolphin, the mount fails with a timeout error. Dolphin is unsure of what went wrong. When mounting via terminal, the error states the filesystem was not cleanly unmounted.


STEPS TO REPRODUCE
1. Plug in USB with exfat partition in a dirty state.
2. Access it via Dolphin.
3. Timeout triggers a red status error where Dolphin is unsure of what went wrong.

OBSERVED RESULT

Unable to mount drive, Dolphin does not indicate the actual cause when that information should be available.

EXPECTED RESULT

The error should state that exfat filesystem was not cleanly unmounted and is in a dirty state. Then advise/link to how to repair(windows only I think, maybe 5.4 kernel will change this.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro KDE (up to date), Kernel 4.19.69-1-MANJARO
KDE Plasma Version: 5.16.4
KDE Frameworks Version: 5.61.0
Qt Version: 5.13.0
Comment 1 Brennan Kinney 2019-09-21 05:40:24 UTC 
Output for performing `sudo fsck.exfat /dev/sdc1`

exfatfsck 1.3.0
Checking file system on /dev/sdc1.
WARN: volume was not unmounted cleanly.
ERROR: fsync failed: Input/output error.
File system checking stopped. ERRORS FOUND: 1, FIXED: 0.

The error appears tied to the device becoming unavailable. A physical unplug and re-plug is required as /dev/sdc1 is no longer available afterwards. The warning is the same given when performing `mount -t exfat /dev/sdc1 /mnt/usb_stick`.

Windows 7 and Windows 10 systems detected the errors but both failed to repair. The repair/scan could be ignored and data could be copied off the disk, but write activity appears to cause the device to fail in Windows as well, and it becomes available until physical reconnection is made.

---

When Windows 7 performed a repair/fix, I was able to mount successfully in Dolphin, although while browsing the files, Dolphin became unresponsive, and ksysguard reported 50% CPU usage(4 cores/threads system), htop revealed <5-10% CPU activity, and ksysguard processes(all) sorted by CPU column showed nothing high usage. Eventually that dropped and Dolphin became responsive again, the mounted location became unavailable and could not mount again.

Possibly related to this old bug: https://bugs.kde.org/show_bug.cgi?id=347565
Although another exfat device unmounts cleanly without getting corrupted.

---

Related issues:
Notification Panel, incorrect error(different from Dolphin): https://bugs.kde.org/show_bug.cgi?id=412146
Partition Manager, gets stuck scanning devices after a failed mount: https://bugs.kde.org/show_bug.cgi?id=412147