public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Sander Smeenk <ssmeenk@freshdot.net>
To: linux-ext4@vger.kernel.org
Subject: Re: ext4 metadata corruption bug bites again
Date: Mon, 24 Aug 2015 15:14:06 +0200	[thread overview]
Message-ID: <20150824131406.GE20572@dot.dmz.freshdot.net> (raw)
In-Reply-To: <20150821094534.GD20572@dot.dmz.freshdot.net>

Quoting Sander Smeenk (ssmeenk@freshdot.net):

> | [000d00h01m43s] EXT4-fs error (device vdb): ext4_mb_generate_buddy:757:
> |   group 79842, block bitmap and bg descriptor inconsistent: 10073 vs 10071
> |   free clusters
> | [000d00h01m43s] Aborting journal on device vdb-8.

Today it went again:

[000d05h26m50s] EXT4-fs error (device vdb): ext4_mb_generate_buddy:757: group 45706, block bitmap and bg descriptor inconsistent: 1769 vs 1768 free clusters
[000d05h26m50s] Aborting journal on device vdb-8.
[000d05h26m50s] EXT4-fs (vdb): Remounting filesystem read-only
[000d05h16m42s] EXT4-fs (vdb): pa ffff88003527fc30: logic 331144, phys.  1363269705, len 511
[000d05h16m42s] EXT4-fs error (device vdb): ext4_mb_release_inode_pa:3772: group 41603, free 511, pa_free 507
[000d05h16m42s] EXT4-fs (vdb): pa ffff88002ed668f0: logic 286160, phys.  1362907136, len 511
[000d05h16m42s] EXT4-fs error (device vdb): ext4_mb_release_inode_pa:3772: group 41592, free 511, pa_free 503

I'm now running 3.19.8-ckt4 with WARN_ON(1); inserted in the above
mentioned error situations.

-Sndr.
-- 
| Do pilots take crash-courses?
| 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7  FBD6 F3A9 9442 20CC 6CD2

  reply	other threads:[~2015-08-24 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-21  9:45 ext4 metadata corruption bug bites again Sander Smeenk
2015-08-24 13:14 ` Sander Smeenk [this message]
2015-09-14  8:05   ` 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=20150824131406.GE20572@dot.dmz.freshdot.net \
    --to=ssmeenk@freshdot.net \
    --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