From: Guenter Roeck <linux@roeck-us.net>
To: Jan Kara <jack@suse.cz>
Cc: Davidlohr Bueso <davidlohr@hp.com>, Theodore Ts'o <tytso@mit.edu>,
LKML <linux-kernel@vger.kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: WARNING: CPU: 26 PID: 93793 at fs/ext4/inode.c:230 ext4_evict_inode+0x4c9/0x500 [ext4]() still in 3.11-rc3
Date: Wed, 07 Aug 2013 09:07:55 -0700 [thread overview]
Message-ID: <520270DB.2060909@roeck-us.net> (raw)
In-Reply-To: <20130807153334.GC26516@quack.suse.cz>
On 08/07/2013 08:33 AM, Jan Kara wrote:
> On Wed 07-08-13 08:27:32, Guenter Roeck wrote:
>> On 08/07/2013 08:20 AM, Jan Kara wrote:
>>> On Thu 01-08-13 20:58:46, Davidlohr Bueso wrote:
>>>> On Thu, 2013-08-01 at 22:33 +0200, Jan Kara wrote:
>>>>> Hi,
>>>>>
>>>>> On Thu 01-08-13 13:14:19, Davidlohr Bueso wrote:
>>>>>> FYI I'm seeing loads of the following messages with Linus' latest
>>>>>> 3.11-rc3 (which includes 822dbba33458cd6ad)
>>>>> Thanks for notice. I see you are running reaim to trigger this. What
>>>>> workload?
>>>>
>>>> After re-running the workloads one by one, I finally hit the issue again
>>>> with 'dbase'. FWIW I'm using ramdisks + ext4.
>>> Hum, I'm not able to reproduce this with current Linus' kernel - commit
>>> e4ef108fcde0b97ed38923ba1ea06c7a152bab9e - I've tried with ramdisk but no
>>> luck. Are you using some special mount options?
>>>
>> I don't see this commit in the upstream kernel ?
> It is Linus's merge of Tejun's libata fix from Tuesday...
>
>> I tried reproducing the problem on the same system I had seen 822dbba33458cd6ad on,
>> with the same workload. It has now been running since last Friday, but I have
>> not seen any problems.
> Ah, OK, so it may be fixed after all. If you happen to see it again,
> please let me know. Thanks!
>
At least the problem I found, yes. The problem Davidlohr found may be a different one.
Guenter
next prev parent reply other threads:[~2013-08-07 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 20:14 WARNING: CPU: 26 PID: 93793 at fs/ext4/inode.c:230 ext4_evict_inode+0x4c9/0x500 [ext4]() still in 3.11-rc3 Davidlohr Bueso
2013-08-01 20:33 ` Jan Kara
2013-08-02 3:58 ` Davidlohr Bueso
2013-08-07 15:20 ` Jan Kara
2013-08-07 15:27 ` Guenter Roeck
2013-08-07 15:33 ` Jan Kara
2013-08-07 16:07 ` Guenter Roeck [this message]
2013-08-07 18:08 ` Davidlohr Bueso
2013-08-07 18:45 ` Jan Kara
2013-08-07 21:07 ` Davidlohr Bueso
2013-08-12 9:57 ` 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=520270DB.2060909@roeck-us.net \
--to=linux@roeck-us.net \
--cc=davidlohr@hp.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.