From: Guenter Roeck <linux@roeck-us.net>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org,
Andreas Dilger <adilger.kernel@dilger.ca>,
Jan Kara <jack@suse.cz>
Subject: Re: WARNING: at fs/ext4/inode.c:230 ext4_evict_inode+0x41b/0x510
Date: Mon, 8 Jul 2013 21:06:58 -0700 [thread overview]
Message-ID: <20130709040658.GA7763@roeck-us.net> (raw)
In-Reply-To: <20130709033510.GE6000@thunk.org>
On Mon, Jul 08, 2013 at 11:35:10PM -0400, Theodore Ts'o wrote:
> On Mon, Jul 08, 2013 at 11:38:29AM -0700, Guenter Roeck wrote:
> > Hi,
> >
> > seen this morning with a brand new top-of-tree kernel (as of last night) plus a
> > couple of patches I am working on.
> >
> > Due to my changes, there is a slight chance that the problem is not due to an
> > upstream bug, but I think that is quite unlikely (my changes are unrelated
> > to file system code).
> >
> > If there is anything I can help to track this down, please let me know.
> >
> > [13071.291013] ------------[ cut here ]------------
> > [13071.291021] WARNING: at fs/ext4/inode.c:230 ext4_evict_inode+0x41b/0x510()
>
> Hmm, this warning was added by commit 5dc23bdd5: ext4: remove
> ext4_ioend_wait().
>
> What sort of work load are you running on this machine? Do you know
> what might have triggered it?
>
My nightly kernel builds were running at the time. This is a sequence of git
clone/checkout operations followed by builds for several targets.
I have the same kernel running on three systems, but this only happened on the
build machine, and I have not seen it again during the day.
I'll let you know if it happens again tonight.
Guenter
next prev parent reply other threads:[~2013-07-09 4:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 18:38 WARNING: at fs/ext4/inode.c:230 ext4_evict_inode+0x41b/0x510 Guenter Roeck
2013-07-09 3:35 ` Theodore Ts'o
2013-07-09 4:06 ` Guenter Roeck [this message]
2013-07-09 8:39 ` Jan Kara
2013-07-09 14:22 ` Guenter Roeck
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=20130709040658.GA7763@roeck-us.net \
--to=linux@roeck-us.net \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@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.