It seems, dd is still attempting to write out, even though its complained of 
being out of disk space.
The kernel msgs are full of this:

[ 7902.830935] INFO: task blkid:25921 blocked for more than 120 seconds.
[ 7902.830937] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 7902.830948] blkid           D ffffffff81806240     0 25921    541 0x00000004
[ 7902.830951]  ffff8801b272bb18 0000000000000082 ffff88023e5fbe00 
ffffffffa052a100
[ 7902.830968]  ffff8801b272bfd8 ffff8801b272bfd8 ffff8801b272bfd8 
0000000000013780
[ 7902.830989]  ffffffff81c0d020 ffff88022b8496f0 000000000b300000 
ffff88022d602a58
[ 7902.830998] Call Trace:
[ 7902.831006]  [<ffffffff8165a0df>] schedule+0x3f/0x60
[ 7902.831026]  [<ffffffff8165aee7>] __mutex_lock_slowpath+0xd7/0x150
[ 7902.831034]  [<ffffffff812f9120>] ? disk_map_sector_rcu+0x80/0x80
[ 7902.831042]  [<ffffffff8165aafa>] mutex_lock+0x2a/0x50
[ 7902.831062]  [<ffffffff811b01db>] __blkdev_get+0x7b/0x460
[ 7902.831069]  [<ffffffff811b061e>] blkdev_get+0x5e/0x1e0
[ 7902.831077]  [<ffffffff811b07fd>] blkdev_open+0x5d/0x80
[ 7902.831098]  [<ffffffff81175a50>] __dentry_open+0x290/0x360
[ 7902.831105]  [<ffffffff811b07a0>] ? blkdev_get+0x1e0/0x1e0
[ 7902.831114]  [<ffffffff8129c3dc>] ? security_inode_permission+0x1c/0x30
[ 7902.831135]  [<ffffffff8118369a>] ? inode_permission+0x4a/0x110
[ 7902.831141]  [<ffffffff811760cd>] vfs_open+0x3d/0x40
[ 7902.831148]  [<ffffffff81176fa0>] nameidata_to_filp+0x40/0x50
[ 7902.831167]  [<ffffffff81185ed8>] do_last+0x3f8/0x730
[ 7902.831174]  [<ffffffff811875b1>] path_openat+0xd1/0x3f0
[ 7902.831181]  [<ffffffff8113b189>] ? __pte_alloc+0xa9/0x160
[ 7902.831201]  [<ffffffff811879f2>] do_filp_open+0x42/0xa0
[ 7902.831211]  [<ffffffff81318861>] ? strncpy_from_user+0x31/0x40
[ 7902.831218]  [<ffffffff81182d3a>] ? do_getname+0x10a/0x180
[ 7902.831237]  [<ffffffff8165bfee>] ? _raw_spin_lock+0xe/0x20
[ 7902.831244]  [<ffffffff81194c97>] ? alloc_fd+0xf7/0x150
[ 7902.831251]  [<ffffffff8117709d>] do_sys_open+0xed/0x220
[ 7902.831271]  [<ffffffff811771f0>] sys_open+0x20/0x30
[ 7902.831277]  [<ffffffff81664602>] system_call_fastpath+0x16/0x1b

Nothing stops this unless I kill 'dd' or eject the card.

Then there is a mess as it fails to write...

..
..
..
[ 8877.239519] end_request: I/O error, dev mmcblk0, sector 30337016
[ 8877.239523] end_request: I/O error, dev mmcblk0, sector 30337024
[ 8877.239528] end_request: I/O error, dev mmcblk0, sector 30337032
[ 8877.239562] mmcblk0: error -123 sending status command, retrying
[ 8877.239577] mmcblk0: error -123 sending status command, retrying
[ 8877.239592] mmcblk0: error -123 sending status command, aborting
[ 8877.239593] end_request: I/O error, dev mmcblk0, sector 30337040

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975305

Title:
  dd writing to an SDHC /dev/mmcblk0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/975305/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to