From: Nathaniel W Filardo <nwf@cs.jhu.edu>
To: Theodore Tso <tytso@google.com>
Cc: Mike Rubin <mrubin@google.com>, Frank Mayhar <fmayhar@google.com>,
admins@acm.jhu.edu, linux-ext4@vger.kernel.org
Subject: Re: ext4 metadata corruption bug?
Date: Thu, 10 Apr 2014 01:04:28 -0400 [thread overview]
Message-ID: <20140410050428.GV10985@gradx.cs.jhu.edu> (raw)
In-Reply-To: <CAGagf4eEzY4+3cfNWSEENTo1PKe40nq1Ne6ZzOLGm-O78W7RcA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1891 bytes --]
On Wed, Apr 09, 2014 at 10:55:48PM -0400, Theodore Tso wrote:
> Hi Nathaniel,
>
> In general, it's best if you send these sorts of requests for help to the
> linux-ext4@vger.kernel.org mailing list.
Added to CC.
> The fact that we see the "error count" line early in the boot message
> suggests to me that your VM is not running fsck to fix up the errors before
> mounting the file system. (Well, either that or you're using a really
> ancient version of e2fsck, but given that you're using a bleeding edge
> kernel, but I'm guessing you're using a reasonably recent version of
> e2fsck. But that would be good for you to check.)
e2fsck version is 1.42.9 using the same library version.
> The ext4 error message is due to the file system getting corrupted. How
> the file system got corrupted isn't 100% clear, but one potential cause is
> how the disk is configured with qemu.
>[snip]
We use QEMU directives like
-drive format=raw,file=rbd:rbdafs-mirror/mirror-0,id=drive5,if=none,cache=writeback \
-device driver=ide-hd,drive=drive5,discard_granularity=512,bus=ahci0.3
We've never had, so far as I know, an unexpected shutdown of the QEMU
process, so I don't think that unexpected loss of cache contents is to
blame.
Perhaps the dmesg I sent was not representative; some days ago, we saw, only
(comparatively!) late in the machine's uptime:
[309894.428685] EXT4-fs (sdd): pa ffff88000d9f9440: logic 832, phys. 957458972, len 192
[309894.430023] EXT4-fs error (device sdd): ext4_mb_release_inode_pa:3729: group 29219, free 192, pa_free 191
[309894.431822] Aborting journal on device sdd-8.
[309894.442913] EXT4-fs (sdd): Remounting filesystem read-only
with Debian kernel 3.13.5-1; sdd here is the same filesystem as in the
earlier dmesg.
I'll capture any subsequent crashes and follow up.
Thanks much!
--nwf;
[-- Attachment #2: Type: application/pgp-signature, Size: 181 bytes --]
next parent reply other threads:[~2014-04-10 5:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140409223820.GU10985@gradx.cs.jhu.edu>
[not found] ` <CAGagf4eEzY4+3cfNWSEENTo1PKe40nq1Ne6ZzOLGm-O78W7RcA@mail.gmail.com>
2014-04-10 5:04 ` Nathaniel W Filardo [this message]
2014-04-10 14:03 ` ext4 metadata corruption bug? Theodore Ts'o
2014-04-10 16:33 ` Nathaniel W Filardo
2014-04-10 22:17 ` Theodore Ts'o
2014-04-20 16:32 ` Nathaniel W Filardo
2014-04-20 17:57 ` Theodore Ts'o
2014-04-23 7:23 ` Sander Smeenk
2014-04-23 14:36 ` Theodore Ts'o
2014-04-23 15:30 ` Nathaniel W Filardo
2014-04-23 18:05 ` Sander Smeenk
2014-04-29 15:22 ` Nathaniel W Filardo
2014-05-01 16:25 ` Nathaniel W Filardo
2014-05-06 15:42 ` Theodore Ts'o
2014-05-06 15:51 ` Nathaniel W Filardo
2014-07-31 2:37 ` Theodore Ts'o
2014-08-06 8:53 ` Sander Smeenk
2014-05-01 17:02 ` Sander Smeenk
2014-05-06 14:22 ` Sander Smeenk
2014-05-26 14:59 ` Sander Smeenk
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=20140410050428.GV10985@gradx.cs.jhu.edu \
--to=nwf@cs.jhu.edu \
--cc=admins@acm.jhu.edu \
--cc=fmayhar@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mrubin@google.com \
--cc=tytso@google.com \
/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).