The behaviour does not occur with if=scsi or if=ide. Tested using 2 different SATA controllers, 1.5 TB lvm/mdraid, single 1.5 TB drive and 2 TB lvm/mdraid. In my case I was switching to virtio at one point, but the behaviour didn't show until there was > 1 TB data on the filesystem. (The following entries will repeat infinitely, mkfs.ext4 will not exit and cannot be killed) Jan 15 20:45:55 q Backgrounding to notify hosts. Jan 15 20:40:44 q kernel: lost page write due to I/O error on vde Jan 15 20:40:44 q kernel: Buffer I/O error on device vde, logical block 366283769 Jan 15 20:40:44 q kernel: Buffer I/O error on device vde, logical block 366283768 Jan 15 20:40:44 q kernel: Buffer I/O error on device vde, logical block 366283767 Jan 15 20:40:44 q kernel: Buffer I/O error on device vde, logical block 366283766 Jan 15 20:40:44 q kernel: Buffer I/O error on device vde, logical block 366283765 Jan 15 20:40:44 q kernel: Buffer I/O error on device vde, logical block 366283764 Here's a typical log excerpt when using mkfs.ext4 on a 1.5 TB drive on a Ubuntu 9.10 guest:
Processes (like mkfs.ext4) might freeze completely when filesystems are created on the guest. When attaching raw drives > 1 TB, buffer io errors will most likely occur, filesystems get corrupted.
0 kommentar(er)
