| Summary: | Special handling of partitions which need an fsck run | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Martin <mrbm74> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | dolphin-bugs-null, nate |
| Priority: | NOR | Keywords: | usability |
| Version First Reported In: | 19.12.3 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
Seems sensible to me. |
SUMMARY Sometimes I'm struggling with external SD-cards and USB drives which were not cleanly unmounted. Under some circumstances Linux mounts them as read only and there is no visible feedback shown to the user. Only a look into the kernel log shows what is really happening in background and that an fsck run is needed with admin rights. EXPECTED RESULT It would be a big improvement if Dolphin would show: - If the device has buggy sectors. So if something like the following errors appear in the kernel log: [ 4472.908058] blk_update_request: I/O error, dev sdc, sector 16576 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [ 4472.908059] Buffer I/O error on dev sdc1, logical block 8384, lost async page write [ 4472.908062] sd 9:0:0:0: [sdc] tag#0 access beyond end of device [ 4472.908063] blk_update_request: I/O error, dev sdc, sector 698050 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [ 4472.908065] Buffer I/O error on dev sdc1, logical block 689858, lost async page write Then Dolphin should inform the user and should offer the option to run fsck on that device or partition. - If the following message appears in the kernel log: "Volume was not properly unmounted. Some data may be corrupt. Please run fsck." Then Dolphin should also offer the option to run fsck. - If the device was mounted as read-only Dolphin should: a) Show the device icon with a lock b) Dolphin should show a message when mounting the device/partition that it was mounted read-only and why it was mounted read-only. c) Show a button to start fsck. If fsck is run a dialog should be displayed which shows the progress and questions which may be asked by fsck.