From: list@jonas-server.de
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Emmanuel Florac <eflorac@intellique.com>,
Brian Foster <bfoster@redhat.com>,
linux-xfs@vger.kernel.org, linux-xfs-owner@vger.kernel.org
Subject: Re: XFS Calltraces by using XFS with Ceph
Date: Mon, 10 Jul 2017 08:34:48 +0200 [thread overview]
Message-ID: <b0762ee29a99f864e0be1e2ea7118baf@jonas-server.de> (raw)
In-Reply-To: <82ba16f5a8bec542ec56c1d4b7fe473e@jonas-server.de>
Am 2017-06-19 12:17, schrieb list@jonas-server.de:
> Am 2017-06-16 19:46, schrieb Darrick J. Wong:
>> On Fri, Jun 16, 2017 at 07:37:11AM +0200, list@jonas-server.de wrote:
>>> Am 2017-06-15 19:20, schrieb Emmanuel Florac:
>>> >Le Thu, 15 Jun 2017 07:55:12 +0200
>>> >list@jonas-server.de écrivait:
>>> >
>>> >>> Looking at the new Elixir[1], it looks like we're trying to deref
>>> >>> ((*bpp)->b_addr)->magic, so that might explain the crash you see.
>>> >>>
>>> >>> --D
>>> >>>
>>> >>> [1]
>>> >>> http://elixir.free-electrons.com/linux/v4.4.72/source/fs/xfs/libxfs/xfs_da_btree.c#L270
>>> >>>
>>> >>>>
>>> >
>>> >Indeed that matches exactly the crash Darrick mentioned. Looks like you
>>> >need either a special hand-patched kernel... or wait for an official
>>> >fix for this one :/
>>>
>>> When will a fix normally be in the ubuntu kernel? I need to have a
>>> stable
>>> distribution kernel, I can not install a patched version.
>>
>> Like Emmanuel said, first a fix has to go upstream, then it can go to
>> the
>> 4.4 stable kernel, and then it'll probably end up in the Ubuntu
>> kernel.
>>
>> Can you post a metadump of the xfs filesystem somewhere for further
>> analysis? I'm pretty sure it's the same problem reported by David
>> Shaw
>> on this list a couple of weeks ago. Since you can't run one-off test
>> kernels, send us a metadump for recreation in a lab is the only other
>> way to figure out if the fix works.
>
> So it is hard for me to run tests with untested kernels as the system
> is already
> used in production. I've created a metadump from the xfs filesystem and
> uploaded it:
> https://transfer.sh/XdlZ5/xfs_metadump.gz
>
> I hope it helps you trigger the bug during your tests.
So what about the issue? Is there a fix available? Will it get upstream
in the next time?
I'm looking forward hearing about that topic.
>
>>
>> (And yes, I /do/ have a lightly tested fix which I'm about to send
>> out.)
>>
>> --D
>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-xfs"
>>> in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-07-10 6:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 8:22 XFS Calltraces by using XFS with Ceph list
2017-06-14 12:08 ` Brian Foster
2017-06-14 13:22 ` list
2017-06-14 14:07 ` Brian Foster
2017-06-14 15:55 ` Darrick J. Wong
2017-06-15 5:55 ` list
2017-06-15 17:20 ` Emmanuel Florac
2017-06-16 5:37 ` list
2017-06-16 13:15 ` Emmanuel Florac
2017-06-16 17:46 ` Darrick J. Wong
2017-06-19 10:17 ` list
2017-07-10 6:34 ` list [this message]
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=b0762ee29a99f864e0be1e2ea7118baf@jonas-server.de \
--to=list@jonas-server.de \
--cc=bfoster@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=eflorac@intellique.com \
--cc=linux-xfs-owner@vger.kernel.org \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).