From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Nageswara R Sastry <rnsastry@linux.vnet.ibm.com>
Cc: linux-ext4@vger.kernel.org, sachinp@linux.vnet.ibm.com,
linux-s390@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [Fwd: [Bug] 2.6.30 kernel stack trace with 'fsfuzzer ext3' on s390]
Date: Mon, 29 Jun 2009 12:28:56 +0200 [thread overview]
Message-ID: <20090629102856.GB9321@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <4A48858B.5080602@linux.vnet.ibm.com>
On Mon, Jun 29, 2009 at 02:42:43PM +0530, Nageswara R Sastry wrote:
> Hitting the same bug with 2.6.31-rc1 on s390 arch.
>
>
> EXT3-fs error (device loop0): htree_dirblock_to_tree: bad entry in
> directory #2: rec_len % 4 != 0 - offset=44, inode=12, rec_len=139,
> name_len=10
> __log_wait_for_space: needed 256 blocks and only had 0 space available
> __log_wait_for_space: no way to get more journal space
Does this _only_ happen on s390? I would expect that this is not
architecture specific. Whatever fsfuzzer is doing.
next prev parent reply other threads:[~2009-06-29 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 9:12 [Fwd: [Bug] 2.6.30 kernel stack trace with 'fsfuzzer ext3' on s390] Nageswara R Sastry
2009-06-29 10:28 ` Heiko Carstens [this message]
2009-07-15 15:36 ` Jan Kara
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=20090629102856.GB9321@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=rnsastry@linux.vnet.ibm.com \
--cc=sachinp@linux.vnet.ibm.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