Opened 12 years ago
Closed 11 years ago
#10995 closed defect (fixed)
vdi corruption with 4.1.22
| Reported by: | DavidWHodgins | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.1.22 |
| Keywords: | Cc: | ||
| Guest type: | Linux | Host type: | Linux |
Description
As reported at https://bugs.mageia.org/show_bug.cgi?id=7582 I've run into a problem with the vdi file becoming corrupted.
Attachments (1)
Change History (4)
by , 12 years ago
comment:1 by , 12 years ago
Fyi. I've now lost a third .vdi file with the same problem. dmesg shows ... [ 4768.220234] EXT4-fs (dm-0): Unaligned AIO/DIO on inode 1708109 by VirtualBox; performance will be poor. [ 5369.286025] hrtimer: interrupt took 42286 ns [ 6841.377102] INFO: task VirtualBox:24054 blocked for more than 120 seconds. [ 6841.377107] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 6841.377113] VirtualBox D 0000000000000001 0 24054 24026 0x00000000 [ 6841.377122] ffff8802484fdd78 0000000000000082 0000000000000001 ffff88002e9f48f0 [ 6841.377131] ffff88035e950000 ffff8802484fdfd8 ffff8802484fdfd8 ffff8802484fdfd8 [ 6841.377138] ffff880429c843b0 ffff88035e950000 ffff8802484fdd88 ffff88039becc8e0 [ 6841.377146] Call Trace: [ 6841.377158] [<ffffffff8144fe9f>] schedule+0x3f/0x60 [ 6841.377166] [<ffffffff81194d59>] inode_dio_wait+0xb9/0xe0 [ 6841.377175] [<ffffffff81071130>] ? autoremove_wake_function+0x40/0x40 [ 6841.377240] [<ffffffffa0167128>] ext4_setattr+0x338/0x550 [ext4] [ 6841.377248] [<ffffffff81053756>] ? current_fs_time+0x16/0x60 [ 6841.377256] [<ffffffff811785fa>] notify_change+0x1aa/0x340 [ 6841.377265] [<ffffffff8115bd4e>] do_truncate+0x5e/0xa0 [ 6841.377270] [<ffffffff81075bed>] ? up_write+0x1d/0x20 [ 6841.377278] [<ffffffff8115c015>] sys_ftruncate+0xd5/0x120 [ 6841.377285] [<ffffffff81458e79>] system_call_fastpath+0x16/0x1b
So far, all of the corrupted vdi files have 64 bit guests. The host is running Mageia 2 x86-64. The three vdi files I've lost have been Mageia 1, 2, and 3, all x86-64 guests.
comment:2 by , 12 years ago
When I try to klll the virtualbox session, there is also a segfault ... [11107.423801] VirtualBox[15528]: segfault at 400c64d8 ip 00007fc774e40e48 sp 00007ffffa0719a0 error 4 in libX11.so.6.3.0[7fc774e08000+135000] [11108.990065] VirtualBox[15736]: segfault at ffffffffd40c64d8 ip 00007f660b558e48 sp 00007fff6370b9b0 error 4 in libX11.so.6.3.0[7f660b520000+135000]
comment:3 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Please reopen if still relevant with VBox 4.2.12. There were some fixes in the storage subsystem after 4.1.22. Especially there was a fix in 4.1.26 which fixed a potential VDI data corruption after the VDI file was resized (I know you didn't mention a disk resize but anyway).
log file