From: Philipp Hahn <hahn@univention.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-fsdevel@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at linux-3.16.7-ckt25/fs/dcache.c:2373!
Date: Fri, 3 Jun 2016 11:17:16 +0200 [thread overview]
Message-ID: <57514B1C.3080506@univention.de> (raw)
In-Reply-To: <20160602200201.GA15429@fieldses.org>
Hello,
Am 02.06.2016 um 22:02 schrieb J. Bruce Fields:
> On Thu, Jun 02, 2016 at 09:51:27AM +0200, Philipp Hahn wrote:
>> probably during heavy IO our file server crashed on a BUG_ON in dache.c,
>> probably triggered by NFS:
>>
>>> ------------[ cut here ]------------
>>> kernel BUG at /var/build/temp/tmp.BPql4ErveJ/pbuilder/linux-3.16.7-ckt25/fs/dcache.c:2373!
...
>> Our kernel is 3.16.7-ckt25 from Debian + ckt26 and ckt27 on top.
>
> So this is the BUG_ON(!d_unhashed(..)) at the top of __d_rehash? I
> don't know the -ckt kernels, and I don't have a BUG at line 2373 of
> dcache.c, or something else?
Yes, exactly that first line.
> There have been a lot of changes in the area since 3.16.7.
Too bad.
Any concrete hint or should I better spent my time convincing management
to install a newer Linux kernel?
Anyway, thank you for the response.
Philipp
next prev parent reply other threads:[~2016-06-03 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 7:51 kernel BUG at linux-3.16.7-ckt25/fs/dcache.c:2373! Philipp Hahn
2016-06-02 20:02 ` J. Bruce Fields
2016-06-03 9:17 ` Philipp Hahn [this message]
2016-06-03 13:14 ` J. Bruce Fields
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=57514B1C.3080506@univention.de \
--to=hahn@univention.de \
--cc=bfields@fieldses.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox