From: Sachin Sant <sachinp@in.ibm.com>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: jfs-discussion@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Jfs-discussion] [BUG/JFS/2.6.29-rc8] kernel BUG at fs/mpage.c:473!
Date: Wed, 18 Mar 2009 10:59:21 +0530 [thread overview]
Message-ID: <49C086B1.9060500@in.ibm.com> (raw)
In-Reply-To: <1237299710.26674.6.camel@norville.austin.ibm.com>
Dave Kleikamp wrote:
> On Mon, 2009-03-16 at 12:40 +0530, Sachin Sant wrote:
>
>> While running file system stress (fsstress) on a JFS partition
>> with 2.6.29-rc8, i hit the following BUG.
>>
>
> I tried reproducing this yesterday, but was unsuccessful. Maybe I
> didn't let it run long enough. Have you run this successfully on
> earlier kernels? If so, what was the most recent that worked for you.
> Have you seen it more than once? I'm not sure how easy it is to
> reproduce.
I haven't tried to test with earlier kernels. This was the first
time i ran these tests on this particular box.I run the fsstress
on different type of file systems one after the another (in no
particular order ). Something like ..
* create ext2 filesystem on a device
* run fsstress.
* unmount the device.
I repeat the above steps with ext3, reiserfs and jfs. May be this
combination is causing this problem.
I have seen this problem on two partitions of a power box. Same problem
seem to have been reported earlier against 2.6.25-rcx kernel.
http://lkml.indiana.edu/hypermail/linux/kernel/0803.2/1418.html
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-03-18 5:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 7:10 [BUG/JFS/2.6.29-rc8] kernel BUG at fs/mpage.c:473! Sachin Sant
2009-03-17 14:21 ` [Jfs-discussion] " Dave Kleikamp
2009-03-18 5:29 ` Sachin Sant [this message]
2009-03-18 10:05 ` Christian Kujau
2009-03-19 6:33 ` Sachin Sant
2009-03-20 1:50 ` Christian Kujau
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=49C086B1.9060500@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.