From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 115491] ext4_mb_generate_buddy, filesystem remounted read-only
Date: Tue, 29 Mar 2016 18:45:11 +0000 [thread overview]
Message-ID: <bug-115491-13602-MWiiEx3ptX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-115491-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=115491
Theodore Tso <tytso@mit.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tytso@mit.edu
--- Comment #1 from Theodore Tso <tytso@mit.edu> ---
Are you running this under KVM? The most recent spate of complaints about
this (which just means that ext4 discovered an inconsistency in the allocation
bitmaps; it doesn't automatically mean it's an ext4 bug) was caused by a bug in
the hypervisor layer of the Host OS. See the resolution of this bug:
https://bugzilla.kernel.org/show_bug.cgi?id=102731
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2016-03-29 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 15:13 [Bug 115491] New: ext4_mb_generate_buddy, filesystem remounted read-only bugzilla-daemon
2016-03-29 18:45 ` bugzilla-daemon [this message]
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-115491-13602-MWiiEx3ptX@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).