From: Pavel Machek <pavel@ucw.cz>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: adilger.kernel@dilger.ca, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 5.0.0-rc8-next-20190301+: kernel bug at fs/inode.c:513
Date: Tue, 5 Mar 2019 00:14:26 +0100 [thread overview]
Message-ID: <20190304231426.GA6191@amd> (raw)
In-Reply-To: <20190304223232.GA6323@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
Hi!
> (Adding linux-mm and moving linux-ext4 and linux-kernel to the bcc
> list...)
Umm. So I ... bcc them too?
> On Mon, Mar 04, 2019 at 05:02:55PM +0100, Pavel Machek wrote:
> >
> > This happened on trying to sync filesystems with unison:
> >
> > Any ideas?
> >
> > Should I be forcing fsck soon?
> > Pavel
> >
> > [12717.827444] ------------[ cut here ]------------
> > [12717.827465] kernel BUG at fs/inode.c:513!
>
> It seems unlikely that fsck is going to help. The BUG_ON in question
> appears to be:
>
> BUG_ON(inode->i_data.nrexceptional);
>
> This is an in-memory accounting variable which seems to be related to
> tracking DAX and shadow page entries --- and it seems very unlikely to
> be the sort of thing triggered by an on-disk corruption.
>
> Do you have a reliable repro for this? If so, the next step would be
> to bisect...
It happened just once... so I don't yet know.
I'm not even sure what file was affected. unison was showing some kind
of png from openstreetmap cache, but I could read it using md5sum just
fine.
-next is normally pretty boring, but it seems to get pretty
interesting around -final release...
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-03-04 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 16:02 5.0.0-rc8-next-20190301+: kernel bug at fs/inode.c:513 Pavel Machek
2019-03-04 22:32 ` Theodore Y. Ts'o
2019-03-04 23:14 ` Pavel Machek [this message]
2019-03-05 21:33 ` Theodore Y. Ts'o
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=20190304231426.GA6191@amd \
--to=pavel@ucw.cz \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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.