You are not logged in.
I have a sandisk cruzer blade USB drive, which I have used for the past hours extensively. At one point, I couldn't manage to write data to it. It acted like it had, but it didn't, as it silently remounted as readonly. I solved this by remounting as rw and retried.
Now, when using the same drive, after writing around 2 GiB worth of data to it (creating files), and attempting to unmount, the unmount command freezes for a long period of time. I check dmesg and it says its frozen. So I open up another tab to try and rescue the writes I made by typing sync. This also freezes and generates dmesg messages.
As I'm typing this the commands seemed to have succeeded, but I'm wondering, what causes these problems? Is the problem known?
dmesg output:
[ 1440.339510] INFO: task umount:1540 blocked for more than 120 seconds.
[ 1440.339518] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1440.339523] umount D ffff88021da81950 0 1540 1539 0x00000004
[ 1440.339531] ffff8801d9ad7c70 0000000000000082 0000000000014500 ffff8801d9ad7fd8
[ 1440.339538] ffff8801d9ad7fd8 0000000000014500 ffff88021da81950 ffff88022ec94500
[ 1440.339545] ffff8801d9ad7bc0 ffffffff81091995 ffff88022211c380 0000000000000002
[ 1440.339551] Call Trace:
[ 1440.339565] [<ffffffff81091995>] ? check_preempt_curr+0x85/0xa0
[ 1440.339571] [<ffffffff8108ecfa>] ? ttwu_stat+0x9a/0x110
[ 1440.339579] [<ffffffff81093a0c>] ? try_to_wake_up+0x1fc/0x2c0
[ 1440.339586] [<ffffffff814e1029>] schedule+0x29/0x70
[ 1440.339593] [<ffffffff814dd909>] schedule_timeout+0x219/0x290
[ 1440.339599] [<ffffffff8107b746>] ? __queue_work+0x136/0x390
[ 1440.339606] [<ffffffff814e03c3>] wait_for_common+0xd3/0x180
[ 1440.339612] [<ffffffff81093b10>] ? wake_up_process+0x40/0x40
[ 1440.339617] [<ffffffff814e048d>] wait_for_completion+0x1d/0x20
[ 1440.339625] [<ffffffff811c8bd0>] writeback_inodes_sb_nr+0x80/0xb0
[ 1440.339648] [<ffffffff811c8c25>] writeback_inodes_sb+0x25/0x30
[ 1440.339655] [<ffffffff811cdedd>] sync_filesystem+0x2d/0xa0
[ 1440.339662] [<ffffffff811a1cb0>] generic_shutdown_super+0x30/0xe0
[ 1440.339668] [<ffffffff811a1f97>] kill_block_super+0x27/0x70
[ 1440.339678] [<ffffffff811a22fd>] deactivate_locked_super+0x3d/0x60
[ 1440.339684] [<ffffffff811a28e6>] deactivate_super+0x46/0x60
[ 1440.339689] [<ffffffff811bdeaf>] mntput_no_expire+0xef/0x150
[ 1440.339695] [<ffffffff811bf0b1>] SyS_umount+0x91/0x3b0
[ 1440.339701] [<ffffffff814ea5dd>] system_call_fastpath+0x1a/0x1f
[ 1560.250364] INFO: task umount:1540 blocked for more than 120 seconds.
[ 1560.250371] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1560.250375] umount D ffff88021da81950 0 1540 1539 0x00000004
[ 1560.250383] ffff8801d9ad7c70 0000000000000082 0000000000014500 ffff8801d9ad7fd8
[ 1560.250390] ffff8801d9ad7fd8 0000000000014500 ffff88021da81950 ffff88022ec94500
[ 1560.250397] ffff8801d9ad7bc0 ffffffff81091995 ffff88022211c380 0000000000000002
[ 1560.250403] Call Trace:
[ 1560.250416] [<ffffffff81091995>] ? check_preempt_curr+0x85/0xa0
[ 1560.250422] [<ffffffff8108ecfa>] ? ttwu_stat+0x9a/0x110
[ 1560.250429] [<ffffffff81093a0c>] ? try_to_wake_up+0x1fc/0x2c0
[ 1560.250435] [<ffffffff814e1029>] schedule+0x29/0x70
[ 1560.250442] [<ffffffff814dd909>] schedule_timeout+0x219/0x290
[ 1560.250448] [<ffffffff8107b746>] ? __queue_work+0x136/0x390
[ 1560.250454] [<ffffffff814e03c3>] wait_for_common+0xd3/0x180
[ 1560.250460] [<ffffffff81093b10>] ? wake_up_process+0x40/0x40
[ 1560.250465] [<ffffffff814e048d>] wait_for_completion+0x1d/0x20
[ 1560.250473] [<ffffffff811c8bd0>] writeback_inodes_sb_nr+0x80/0xb0
[ 1560.250493] [<ffffffff811c8c25>] writeback_inodes_sb+0x25/0x30
[ 1560.250499] [<ffffffff811cdedd>] sync_filesystem+0x2d/0xa0
[ 1560.250506] [<ffffffff811a1cb0>] generic_shutdown_super+0x30/0xe0
[ 1560.250513] [<ffffffff811a1f97>] kill_block_super+0x27/0x70
[ 1560.250522] [<ffffffff811a22fd>] deactivate_locked_super+0x3d/0x60
[ 1560.250528] [<ffffffff811a28e6>] deactivate_super+0x46/0x60
[ 1560.250533] [<ffffffff811bdeaf>] mntput_no_expire+0xef/0x150
[ 1560.250538] [<ffffffff811bf0b1>] SyS_umount+0x91/0x3b0
[ 1560.250545] [<ffffffff814ea5dd>] system_call_fastpath+0x1a/0x1f
[ 1560.250550] INFO: task sync:1547 blocked for more than 120 seconds.
[ 1560.250553] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1560.250556] sync D ffffffff811cdd00 0 1547 985 0x00000000
[ 1560.250561] ffff8801be2e1e68 0000000000000086 0000000000014500 ffff8801be2e1fd8
[ 1560.250567] ffff8801be2e1fd8 0000000000014500 ffff8801c1335460 ffff8801be2e1e70
[ 1560.250573] ffffffff811326ab ffff8801be2e1de0 ffff88020bdbc280 0000000000000080
[ 1560.250579] Call Trace:
[ 1560.250586] [<ffffffff811326ab>] ? filemap_fdatawait_range+0x17b/0x1a0
[ 1560.250594] [<ffffffff811cdd00>] ? generic_write_sync+0x60/0x60
[ 1560.250599] [<ffffffff814e1029>] schedule+0x29/0x70
[ 1560.250604] [<ffffffff814e1d85>] rwsem_down_read_failed+0xc5/0x120
[ 1560.250610] [<ffffffff81292744>] call_rwsem_down_read_failed+0x14/0x30
[ 1560.250616] [<ffffffff814dffa7>] ? down_read+0x17/0x20
[ 1560.250620] [<ffffffff811a34cc>] iterate_supers+0x9c/0x110
[ 1560.250628] [<ffffffff811cdf85>] sys_sync+0x35/0x90
[ 1560.250633] [<ffffffff814ea5dd>] system_call_fastpath+0x1a/0x1fOffline
You do know that flash memories have limited number of write cycles, right?
What happened to Arch's KISS? systemd sure is stupid but I must have missed the simple part ...
... and who is general Failure and why is he reading my harddisk?
Offline
You do know that flash memories have limited number of write cycles, right?
Limited how? Like all storage devices have (in other words, after a while they break)?
The drive is completely new, like 3 weeks or something.
Offline