From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.jonas-server.de ([185.53.128.64]:60381 "EHLO mail.jonas-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751897AbdFSKRi (ORCPT ); Mon, 19 Jun 2017 06:17:38 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Mon, 19 Jun 2017 12:17:25 +0200 From: list@jonas-server.de Subject: Re: XFS Calltraces by using XFS with Ceph In-Reply-To: <20170616174646.GD5421@birch.djwong.org> References: <20170614120829.GA65212@bfoster.bfoster> <20170614140732.GA857@bfoster.bfoster> <20170614155513.GQ4530@birch.djwong.org> <34ddf391569ed02b85a59eff856088ab@jonas-server.de> <20170615192009.18ddd3bc@harpe.intellique.com> <7c00729f5554099fcf5eae65ee1cb4a0@jonas-server.de> <20170616174646.GD5421@birch.djwong.org> Message-ID: <82ba16f5a8bec542ec56c1d4b7fe473e@jonas-server.de> Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: "Darrick J. Wong" Cc: Emmanuel Florac , Brian Foster , linux-xfs@vger.kernel.org, linux-xfs-owner@vger.kernel.org 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. > > (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