[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130709040658.GA7763@roeck-us.net>
Date: Mon, 8 Jul 2013 21:06:58 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Theodore Ts'o <tytso@....edu>
Cc: linux-ext4@...r.kernel.org,
Andreas Dilger <adilger.kernel@...ger.ca>,
Jan Kara <jack@...e.cz>
Subject: Re: WARNING: at fs/ext4/inode.c:230 ext4_evict_inode+0x41b/0x510
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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists