From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 216012] New: Data loss on VirtualBox VMs
Date: Sat, 21 May 2022 17:52:41 +0000 [thread overview]
Message-ID: <bug-216012-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216012
Bug ID: 216012
Summary: Data loss on VirtualBox VMs
Product: File System
Version: 2.5
Kernel Version: Linux ubuntu 5.13.0-35-generic #40-Ubuntu SMP Mon Mar
7 08:03:10 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: aathan_kernel@memeplex.com
Regression: No
From recent kernel and/or vbox versions forward, I've started to experience
data loss and/or filesystem corruption on a regular enough basis that I've
enabled fsck on every reboot. Mac OSX hosted VM.
It's not clear to me what the source of the problem is, but it may not be ext4
itself vs some element of the block device drivers and/or related hypervisor
facilities.
Message from syslogd@ubuntu at May 21 15:56:49 ...
kernel:[1958392.548682] EXT4-fs (dm-0): failed to convert unwritten extents to
written extents -- potential data loss! (inode 259291, error -30)
Message from syslogd@ubuntu at May 21 15:56:50 ...
kernel:[1958392.830326] EXT4-fs (dm-0): failed to convert unwritten extents to
written extents -- potential data loss! (inode 262111, error -30)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-05-21 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 17:52 bugzilla-daemon [this message]
2022-05-22 6:04 ` [Bug 216012] Data loss on VirtualBox VMs bugzilla-daemon
2022-05-22 20:18 ` bugzilla-daemon
2022-05-23 21:05 ` bugzilla-daemon
2022-05-25 8:22 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-216012-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.