public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@sun.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: error in ext4_mb_release_inode_pa
Date: Mon, 07 Jul 2008 20:04:12 -0500	[thread overview]
Message-ID: <4872BD0C.9080404@redhat.com> (raw)
In-Reply-To: <20080707232022.GX6239@webber.adilger.int>

Andreas Dilger wrote:
> On Jul 07, 2008  10:29 -0500, Eric Sandeen wrote:
>> This was on #linuxfs last night, and I think I've seen at least one
>> other report of it:
>>
>> [22:44]  <shehjart> any ideas why i get the following two lines on the
>> serial console when writing to ext4 over software raid0:
>> [22:44]  <shehjart> pa e00001004112d450: logic 11928, phys. 47003288,
>> len 360
>> [22:45]  <shehjart> EXT4-fs error (device md0):
>> ext4_mb_release_inode_pa: free 176, pa_free 174
> 
> The bug that I recalled from Lustre is unlikely to be the same.  It is
> https://bugzilla.lustre.org/show_bug.cgi?id=15932
> 
> 	"error: N blocks in bitmap, M in gd"
> 
> There was a second bug in ext3_mb_use_best_found() hit on > 8TB filesystems:
> https://bugzilla.lustre.org/show_bug.cgi?id=16101
> 
> 	BUG_ON(ac->ac_b_ex.fe_group != e3b->bd_group);
> 

Thanks Andreas -

In an effort to not lose track of it I filed a bug:

http://bugzilla.kernel.org/show_bug.cgi?id=11053

-Eric

  reply	other threads:[~2008-07-08  1:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07 15:29 error in ext4_mb_release_inode_pa Eric Sandeen
2008-07-07 23:20 ` Andreas Dilger
2008-07-08  1:04   ` Eric Sandeen [this message]
2008-07-08  7:49   ` Aneesh Kumar K.V

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=4872BD0C.9080404@redhat.com \
    --to=sandeen@redhat.com \
    --cc=adilger@sun.com \
    --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