lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 22 May 2022 20:18:56 +0000
Subject: [Bug 216012] Data loss on VirtualBox VMs

AA ( changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|ANSWERED                    |---

--- Comment #2 from AA ( ---

I provided the information I had. You're not talking to a complete noob, Artem.
If this issue was deterministically reproducible, you can be assured I'd have
provided the steps to reproduce it and any additional details.

There is some multi-factor problem going on here, and frankly, I don't even
know where to start in order to determine the cause! This is a linux virtual
machine hosted by virtualbox on mac os x.

Since the error is reported by ext4-fs, and I did not immediately find other
errors reported, I reported the ext4-fs errors to ext4.

One possibility is that this occurs when the os x system is under relatively
high load. Under 5x kernel versions on this VB host I have also seen some
occasional CPU X stuck for 22s messages. However these messages have not been
correlated with the ext4 errors.

If anyone has knowledge as to the conditions that can cause this ext4 error
message, I will try to dig deeper next time it happens. The combination of
factors seems to point to core issues in the VirtualBox drivers and/or
virtualization interfaces but I'm just not sure. Maybe the virtual block device
driver bubbles up a timeout of some kind as an unrecoverable write to ext4 via
whatever kernel interface is being used to write fs blocks???

If you still feel ubuntu is the right place to chase down the issue I'll go
there. I've not gotten any traction from reporting the CPU stuck issue to

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

Powered by blists - more mailing lists