Very long time to unmout an exfat perndrive

Xwang · 2021-03-16 13:56:28

Hi to all.
I have a 128GB pendrive formatted as exfat.
Till today it worked correctly, but now everytime I try to safely remove it (using the "eject" button of the KDE USB management tool which is i the tray) it takes a lot time to do that (more than 10 minutes).
This is the dmesg output

[   91.330757] usb 4-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[   91.348756] usb 4-1: New USB device found, idVendor=0951, idProduct=1666, bcdDevice= 1.10
[   91.348769] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   91.348775] usb 4-1: Product: DataTraveler 3.0
[   91.348780] usb 4-1: Manufacturer: Kingston
[   91.348784] usb 4-1: SerialNumber: 08606E6B64AAE341B7103CEF
[   91.352365] usb-storage 4-1:1.0: USB Mass Storage device detected
[   91.353137] scsi host4: usb-storage 4-1:1.0
[   92.409606] scsi 4:0:0:0: Direct-Access     Kingston DataTraveler 3.0 PMAP PQ: 0 ANSI: 6
[   92.410228] sd 4:0:0:0: Attached scsi generic sg3 type 0
[   92.410902] sd 4:0:0:0: [sdd] 242221056 512-byte logical blocks: (124 GB/116 GiB)
[   92.411242] sd 4:0:0:0: [sdd] Write Protect is off
[   92.411248] sd 4:0:0:0: [sdd] Mode Sense: 45 00 00 00
[   92.411491] sd 4:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   92.445255]  sdd: sdd1
[   92.446995] sd 4:0:0:0: [sdd] Attached SCSI removable disk
[  615.482062] INFO: task pool-udisksd:138467 blocked for more than 122 seconds.
[  615.482073]       Tainted: P          IOE     5.11.6-zen1-1-zen #1
[  615.482078] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  615.482080] task:pool-udisksd    state:D stack:    0 pid:138467 ppid:     1 flags:0x00004000
[  615.482092] Call Trace:
[  615.482098]  __schedule+0x2dd/0xc70
[  615.482111]  schedule+0x5b/0xc0
[  615.482117]  writeback_inodes_sb+0x125/0x160
[  615.482126]  ? wait_woken+0x80/0x80
[  615.482143]  sync_filesystem+0x29/0x90
[  615.482150]  generic_shutdown_super+0x22/0x100
[  615.482158]  kill_block_super+0x21/0x50
[  615.482164]  deactivate_locked_super+0x36/0x90
[  615.482172]  cleanup_mnt+0x12d/0x190
[  615.482182]  task_work_run+0x5c/0x90
[  615.482190]  exit_to_user_mode_prepare+0x158/0x160
[  615.482200]  syscall_exit_to_user_mode+0x23/0x50
[  615.482209]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  615.482219] RIP: 0033:0x7f3006d2608b
[  615.482226] RSP: 002b:00007f3005c0b4c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
[  615.482234] RAX: 0000000000000000 RBX: 00007f3007365264 RCX: 00007f3006d2608b
[  615.482238] RDX: 000000000000001c RSI: 0000000000000000 RDI: 00007f2ff8075030
[  615.482242] RBP: 00007f2ff800f360 R08: 0000000000000000 R09: 00007f2ff8000080
[  615.482246] R10: 00007f2ff8007230 R11: 0000000000000246 R12: 0000000000000000
[  615.482250] R13: 00007f2ff8075030 R14: 00007f2ff800f470 R15: 00007f2ff8073a60
[  738.362327] INFO: task pool-udisksd:138467 blocked for more than 245 seconds.
[  738.362338]       Tainted: P          IOE     5.11.6-zen1-1-zen #1
[  738.362343] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  738.362345] task:pool-udisksd    state:D stack:    0 pid:138467 ppid:     1 flags:0x00004000
[  738.362362] Call Trace:
[  738.362371]  __schedule+0x2dd/0xc70
[  738.362383]  schedule+0x5b/0xc0
[  738.362389]  writeback_inodes_sb+0x125/0x160
[  738.362398]  ? wait_woken+0x80/0x80
[  738.362415]  sync_filesystem+0x29/0x90
[  738.362422]  generic_shutdown_super+0x22/0x100
[  738.362430]  kill_block_super+0x21/0x50
[  738.362436]  deactivate_locked_super+0x36/0x90
[  738.362444]  cleanup_mnt+0x12d/0x190
[  738.362454]  task_work_run+0x5c/0x90
[  738.362462]  exit_to_user_mode_prepare+0x158/0x160
[  738.362472]  syscall_exit_to_user_mode+0x23/0x50
[  738.362481]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  738.362491] RIP: 0033:0x7f3006d2608b
[  738.362498] RSP: 002b:00007f3005c0b4c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
[  738.362505] RAX: 0000000000000000 RBX: 00007f3007365264 RCX: 00007f3006d2608b
[  738.362510] RDX: 000000000000001c RSI: 0000000000000000 RDI: 00007f2ff8075030
[  738.362514] RBP: 00007f2ff800f360 R08: 0000000000000000 R09: 00007f2ff8000080
[  738.362518] R10: 00007f2ff8007230 R11: 0000000000000246 R12: 0000000000000000
[  738.362522] R13: 00007f2ff8075030 R14: 00007f2ff800f470 R15: 00007f2ff8073a60
[  861.242569] INFO: task pool-udisksd:138467 blocked for more than 368 seconds.
[  861.242580]       Tainted: P          IOE     5.11.6-zen1-1-zen #1
[  861.242584] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  861.242587] task:pool-udisksd    state:D stack:    0 pid:138467 ppid:     1 flags:0x00004000
[  861.242598] Call Trace:
[  861.242605]  __schedule+0x2dd/0xc70
[  861.242617]  schedule+0x5b/0xc0
[  861.242623]  writeback_inodes_sb+0x125/0x160
[  861.242632]  ? wait_woken+0x80/0x80
[  861.242649]  sync_filesystem+0x29/0x90
[  861.242656]  generic_shutdown_super+0x22/0x100
[  861.242664]  kill_block_super+0x21/0x50
[  861.242671]  deactivate_locked_super+0x36/0x90
[  861.242679]  cleanup_mnt+0x12d/0x190
[  861.242688]  task_work_run+0x5c/0x90
[  861.242696]  exit_to_user_mode_prepare+0x158/0x160
[  861.242706]  syscall_exit_to_user_mode+0x23/0x50
[  861.242715]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  861.242725] RIP: 0033:0x7f3006d2608b
[  861.242731] RSP: 002b:00007f3005c0b4c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
[  861.242739] RAX: 0000000000000000 RBX: 00007f3007365264 RCX: 00007f3006d2608b
[  861.242744] RDX: 000000000000001c RSI: 0000000000000000 RDI: 00007f2ff8075030
[  861.242748] RBP: 00007f2ff800f360 R08: 0000000000000000 R09: 00007f2ff8000080
[  861.242752] R10: 00007f2ff8007230 R11: 0000000000000246 R12: 0000000000000000
[  861.242756] R13: 00007f2ff8075030 R14: 00007f2ff800f470 R15: 00007f2ff8073a60
[  984.122718] INFO: task pool-udisksd:138467 blocked for more than 491 seconds.
[  984.122729]       Tainted: P          IOE     5.11.6-zen1-1-zen #1
[  984.122734] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  984.122736] task:pool-udisksd    state:D stack:    0 pid:138467 ppid:     1 flags:0x00004000
[  984.122748] Call Trace:
[  984.122755]  __schedule+0x2dd/0xc70
[  984.122768]  schedule+0x5b/0xc0
[  984.122774]  writeback_inodes_sb+0x125/0x160
[  984.122782]  ? wait_woken+0x80/0x80
[  984.122799]  sync_filesystem+0x29/0x90
[  984.122806]  generic_shutdown_super+0x22/0x100
[  984.122814]  kill_block_super+0x21/0x50
[  984.122821]  deactivate_locked_super+0x36/0x90
[  984.122829]  cleanup_mnt+0x12d/0x190
[  984.122838]  task_work_run+0x5c/0x90
[  984.122847]  exit_to_user_mode_prepare+0x158/0x160
[  984.122856]  syscall_exit_to_user_mode+0x23/0x50
[  984.122865]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  984.122876] RIP: 0033:0x7f3006d2608b
[  984.122883] RSP: 002b:00007f3005c0b4c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
[  984.122891] RAX: 0000000000000000 RBX: 00007f3007365264 RCX: 00007f3006d2608b
[  984.122895] RDX: 000000000000001c RSI: 0000000000000000 RDI: 00007f2ff8075030
[  984.122899] RBP: 00007f2ff800f360 R08: 0000000000000000 R09: 00007f2ff8000080
[  984.122904] R10: 00007f2ff8007230 R11: 0000000000000246 R12: 0000000000000000
[  984.122908] R13: 00007f2ff8075030 R14: 00007f2ff800f470 R15: 00007f2ff8073a60
[ 1107.003007] INFO: task pool-udisksd:138467 blocked for more than 614 seconds.
[ 1107.003018]       Tainted: P          IOE     5.11.6-zen1-1-zen #1
[ 1107.003023] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1107.003025] task:pool-udisksd    state:D stack:    0 pid:138467 ppid:     1 flags:0x00004000
[ 1107.003037] Call Trace:
[ 1107.003043]  __schedule+0x2dd/0xc70
[ 1107.003056]  schedule+0x5b/0xc0
[ 1107.003062]  writeback_inodes_sb+0x125/0x160
[ 1107.003071]  ? wait_woken+0x80/0x80
[ 1107.003087]  sync_filesystem+0x29/0x90
[ 1107.003095]  generic_shutdown_super+0x22/0x100
[ 1107.003103]  kill_block_super+0x21/0x50
[ 1107.003110]  deactivate_locked_super+0x36/0x90
[ 1107.003117]  cleanup_mnt+0x12d/0x190
[ 1107.003127]  task_work_run+0x5c/0x90
[ 1107.003136]  exit_to_user_mode_prepare+0x158/0x160
[ 1107.003145]  syscall_exit_to_user_mode+0x23/0x50
[ 1107.003154]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 1107.003164] RIP: 0033:0x7f3006d2608b
[ 1107.003171] RSP: 002b:00007f3005c0b4c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
[ 1107.003179] RAX: 0000000000000000 RBX: 00007f3007365264 RCX: 00007f3006d2608b
[ 1107.003184] RDX: 000000000000001c RSI: 0000000000000000 RDI: 00007f2ff8075030
[ 1107.003188] RBP: 00007f2ff800f360 R08: 0000000000000000 R09: 00007f2ff8000080
[ 1107.003192] R10: 00007f2ff8007230 R11: 0000000000000246 R12: 0000000000000000
[ 1107.003196] R13: 00007f2ff8075030 R14: 00007f2ff800f470 R15: 00007f2ff8073a60
[ 1229.883166] INFO: task pool-udisksd:138467 blocked for more than 737 seconds.
[ 1229.883177]       Tainted: P          IOE     5.11.6-zen1-1-zen #1
[ 1229.883182] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1229.883184] task:pool-udisksd    state:D stack:    0 pid:138467 ppid:     1 flags:0x00004000
[ 1229.883195] Call Trace:
[ 1229.883202]  __schedule+0x2dd/0xc70
[ 1229.883214]  schedule+0x5b/0xc0
[ 1229.883220]  writeback_inodes_sb+0x125/0x160
[ 1229.883242]  ? wait_woken+0x80/0x80
[ 1229.883259]  sync_filesystem+0x29/0x90
[ 1229.883266]  generic_shutdown_super+0x22/0x100
[ 1229.883274]  kill_block_super+0x21/0x50
[ 1229.883280]  deactivate_locked_super+0x36/0x90
[ 1229.883288]  cleanup_mnt+0x12d/0x190
[ 1229.883298]  task_work_run+0x5c/0x90
[ 1229.883307]  exit_to_user_mode_prepare+0x158/0x160
[ 1229.883317]  syscall_exit_to_user_mode+0x23/0x50
[ 1229.883325]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 1229.883335] RIP: 0033:0x7f3006d2608b
[ 1229.883342] RSP: 002b:00007f3005c0b4c8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
[ 1229.883350] RAX: 0000000000000000 RBX: 00007f3007365264 RCX: 00007f3006d2608b
[ 1229.883354] RDX: 000000000000001c RSI: 0000000000000000 RDI: 00007f2ff8075030
[ 1229.883358] RBP: 00007f2ff800f360 R08: 0000000000000000 R09: 00007f2ff8000080
[ 1229.883362] R10: 00007f2ff8007230 R11: 0000000000000246 R12: 0000000000000000
[ 1229.883366] R13: 00007f2ff8075030 R14: 00007f2ff800f470 R15: 00007f2ff8073a60
[ 1255.048470] usb 4-1: USB disconnect, device number 3

Both fsck.exfat and windows diagnostic tool say that the pendrive does not have errors.
The unmount takes a lo
Another exfat pendrive which is smaller (64GB) and empty does not give any error and the unmount happens immediately.
Any idea on how to solve this issue?

Last edited by Xwang (2021-03-20 08:52:40)

paulkerry · 2021-03-16 14:58:04

Have you taken a look at things to do with sysctl, like...

vm.dirty_ratio
vm.dirty_background_ratio

see also https://bbs.archlinux.org/viewtopic.php?id=188345

Last edited by paulkerry (2021-03-16 15:06:19)

Xwang · 2021-03-16 15:09:24

paulkerry wrote:

Have you taken a look at things to with sysctl, like...
vm.dirty_ratio
vm.dirty_background_ratio
see also https://bbs.archlinux.org/viewtopic.php?id=188345

sysctl vm.dirty_ratio says:

vm.dirty_ratio = 50

sysctl vm.dirty_background_ratio says:

vm.dirty_background_ratio = 20

and I've not changed them as far as I can remember and surely not in the later days.

Moreover, I've just tried to revert to the previous version of kio because it seemed the only package which has been updated in the latest days which could have been related to the problem, but the issue is present even with the previous version of kio.

paulkerry · 2021-03-16 15:14:50

Xwang wrote:

and I've not changed them as far as I can remember and surely not in the later days.

What I'm saying is try to change them and see if that helps.
You could use sysctl from the command line to temporarily change settings to perhaps...
vm.dirty_ratio=10
vm.dirty_background_ratio=5

and if that is successful, create a sysctl.d config file

seth · 2021-03-16 15:39:04

This is only relevant if the delay is caused by large sync demands (ie. a lot of stuff was written onto the 128GB drive but nothing onto the 64GB one)

@Xwang , if you just mount and immediately umount it and ensure nothing tries to write it (in doubt take KDE out of the equation, its tracker might index to the drive), is the umount still slow?
If not, what if you just touch a file there (or copy a small file)?

Xwang · 2021-03-16 15:41:10

Changing the vm_ parameters has changed nothing.

seth wrote:

This is only relevant if the delay is caused by large sync demands (ie. a lot of stuff was written onto the 128GB drive but nothing onto the 64GB one)
@Xwang , if you just mount and immediately umount it and ensure nothing tries to write it (in doubt take KDE out of the equation, its tracker might index to the drive), is the umount still slow?
If not, what if you just touch a file there (or copy a small file)?

If I mount and then unmount it immediately, still it gives thoes errors and takes about 10 minutes to complete.

seth · 2021-03-16 15:50:33

If you don't mount it, but dd *from* the device (eg. "dd if=/dev/sdb1 of=/dev/null"), do you get similar hangs and timeouts?
Did you update (and/or reboot) before "today" (ie. could it be a kernel regression)?
Do you use both pendrives at the same usb port?

If you can, try the pendrive on a completely different system (hardware/software) because it becomes increasingly likely that the error is with the drive.

Xwang · 2021-03-16 15:51:06

Sorry, I had a sense of dejavu with this problem:
https://bbs.archlinux.org/viewtopic.php?id=263090

I remembered that some months ago it happened a similar thing, so I suspect that I have to format the pendrive again.

Xwang · 2021-03-20 09:07:37

I reopen the thread because meantime I've tested the pendrive with badblocks and f3write, f3read and f3probe.
No issue was found and since some of these test were destructive I've had to recreate the partition table of the pen drive and reformat it.
But still it gives the same error.
I found also this thread https://bbs.archlinux.org/viewtopic.php?id=264604 which has the same issue.

Arch Linux

#1 2021-03-16 13:56:28

Very long time to unmout an exfat perndrive

#2 2021-03-16 14:58:04

Re: Very long time to unmout an exfat perndrive

#3 2021-03-16 15:09:24

Re: Very long time to unmout an exfat perndrive

#4 2021-03-16 15:14:50

Re: Very long time to unmout an exfat perndrive

#5 2021-03-16 15:39:04

Re: Very long time to unmout an exfat perndrive

#6 2021-03-16 15:41:10

Re: Very long time to unmout an exfat perndrive

#7 2021-03-16 15:50:33

Re: Very long time to unmout an exfat perndrive

#8 2021-03-16 15:51:06

Re: Very long time to unmout an exfat perndrive

#9 2021-03-20 09:07:37

Re: Very long time to unmout an exfat perndrive

Board footer