blk_update_request: I/O error

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1526537

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc5-wily

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Joseph, I encounter this problem also in ubuntu 15.04 with a linux-image-3.19.0-15-generic.

I can append some additional information how to reproduce this issue. After my analysis I found dependence: drive filesystem vs backing file filesystem:

Create backing file on a drive that is formatted to NTFS
dd if=/dev/zero of=./Test.img bs=1M count=1024

Find free loop device
losetup -f

Connect backing file with a loop device [ losetup -f ], for example: /dev/loop3
losetup /dev/loop3 ./Test.img

Create filesystem on backing file via loop device
mkfs.ext4 /dev/loop3

Mount backing file via loop device into /mnt directory
mount -t ext4 /dev/loop3 /mnt/

Write some data on backing file via loop device
dd if=/dev/zero of=/mnt/Test.file bs=1M count=512

After this procedure you will be see errors on a kernel log:
[ 1370.381087] blk_update_request: I/O error, dev loop3, sector 25864
[ 1370.789277] blk_update_request: I/O error, dev loop3, sector 29960
[ 1371.193360] blk_update_request: I/O error, dev loop3, sector 34056

Marcin, at your earliest convenience, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

Marcin, was this issue not reproducible in a release prior to 15.04?

Yes, this issue not reproducible in a release prior to 15.04 [ ex. 14.04.3 ]

Marcin, the next step is to fully commit bisect from kernel 3.13 to 4.2 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Still seeing this in 4.4.0 kernels on Ubuntu 16.04.

$ dmesg | grep -i blk
[ 5.660121] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN)
[ 60.473635] blk_update_request: I/O error, dev loop0, sector 151271776
[ 64.663131] blk_update_request: I/O error, dev loop0, sector 193202168
[ 67.053226] blk_update_request: I/O error, dev loop0, sector 155758640
[ 67.119192] blk_update_request: I/O error, dev loop0, sector 155758648
[ 67.189707] blk_update_request: I/O error, dev loop0, sector 155758656
[ 67.353011] blk_update_request: I/O error, dev loop0, sector 154296456
[ 67.411390] blk_update_request: I/O error, dev loop0, sector 155758664
[ 67.469595] blk_update_request: I/O error, dev loop0, sector 154296464
[ 67.529317] blk_update_request: I/O error, dev loop0, sector 155758672
[ 67.586518] blk_update_request: I/O error, dev loop0, sector 155758680
[ 67.669838] blk_update_request: I/O error, dev loop0, sector 155758688
[ 67.746886] blk_update_request: I/O error, dev loop0, sector 155758696
[ 72.829706] blk_update_request: 8 callbacks suppressed
[ 72.829712] blk_update_request: I/O error, dev loop0, sector 155758768
[ 73.164340] blk_update_request: I/O error, dev loop0, sector 155758776
[ 73.672569] blk_update_request: I/O error, dev loop0, sector 155758784
[ 80.571864] blk_update_request: I/O error, dev loop0, sector 155758792
[ 80.660314] blk_update_request: I/O error, dev loop0, sector 67514472
[ 80.735506] blk_update_request: I/O error, dev loop0, sector 158408744
[ 80.789497] blk_update_request: I/O error, dev loop0, sector 67514480
[ 80.843609] blk_update_request: I/O error, dev loop0, sector 67514488
[ 80.898603] blk_update_request: I/O error, dev loop0, sector 67514496
[ 80.957007] blk_update_request: I/O error, dev loop0, sector 67514504
[ 99.165416] blk_update_request: I/O error, dev loop0, sector 158408720
[ 100.452488] blk_update_request: I/O error, dev loop0, sector 158409144
[ 100.452497] blk_update_request: I/O error, dev loop0, sector 158409184
[ 106.492835] blk_update_request: I/O error, dev loop0, sector 67515384
[ 107.409988] blk_update_request: I/O error, dev loop0, sector 155760968
[ 705.902224] blk_update_request: I/O error, dev loop0, sector 158410984
[ 707.433389] blk_update_request: I/O error, dev loop0, sector 158411328
[ 710.156894] blk_update_request: I/O error, dev loop0, sector 154299240
[ 711.846610] blk_update_request: I/O error, dev loop0, sector 158411440
[ 712.162845] blk_update_request: I/O error, dev loop0, sector 158411664
[ 713.730702] blk_update_request: I/O error, dev loop0, sector 158411680
[ 800.300872] blk_update_request: I/O error, dev loop0, sector 154299328
[ 880.661945] blk_update_request: I/O error, dev loop0, sector 155762080
[ 881.002646] blk_update_request: I/O error, dev loop0, sector 158411848
[ 883.469054] blk_update_request: I/O error, dev loop0, sector 158411968
[ 1489.772068] blk_update_request: I/O error, dev loop0, sector 158412376
[ 2018.027178] blk_update_request: I/O error, dev loop0...

I can confirm that the error messages on Ubuntu 16.04 (daily) still exist but it seems that it is not as bad as it looks.

I followed the steps which Marcin described in comment #16. Instead of

> Write some data on backing file via loop device
> dd if=/dev/zero of=/mnt/Test.file bs=1M count=512

I copied a known iso file to the created loop device
dd if=lubuntu-14.04.4-desktop-amd64.iso of=/mnt/Test.file bs=1M

I got also some error messages as described in previous comments but md5sum said

md5sum lubuntu-14.04.4-desktop-amd64.iso && md5sum /mnt/Test.file

0b0fc8652afe0761edc3ed33e1b199f0 lubuntu-14.04.4-desktop-amd64.iso
0b0fc8652afe0761edc3ed33e1b199f0 /mnt/Test.file

Then I unmounted the test image and checked it for errors.

umount /mnt/
fsck -pvcf ./Test.img

...and I got:

fsck from util-linux 2.27.1
./Test.img: Updating bad block inode.

          12 inodes used (0.02%, out of 65536)
           0 non-contiguous files (0.0%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 3/1
      201308 blocks used (76.79%, out of 262144)
           0 bad blocks
           1 large file

           1 regular file
           2 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
           3 files

D. Charles Pyle / hakuna_matata, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

I have the same problem on Ubuntu 16.04 and Kernel 4.10.0-38-generic .

Lancillotto (antonio-petricca), it will help immensely if you filed a new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

I solved my problem!

Recently I have published a guide on how to install linux on loopback LVM devices booting from USB (so without have to install grub on the internal disk, leaving it as original). Here is the guide: https://github.com/DareDevil73/linux-on-loopback-usb .

Then I fallen in the freeze issue on high memory load and I observed an abnormal swap space usage (all the RAM eaten, and swap usage near to zero). Obviously the LVM swap partition was mounted and working properly, but I don't known why the kernel did not use it as expected.

I tried an alternative solution. I have created a swap loopback file (not LVM) and the freeze is gone. Now the swap file is used as it would be, and the OS never freeze!

Please look at https://github.com/DareDevil73/linux-on-loopback-usb#known-issues to get deeper information.