public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Alex Gorbachev <ag@iss-integration.com>
Cc: xfs@oss.sgi.com
Subject: Re: Failing XFS filesystem underlying Ceph OSDs
Date: Sat, 4 Jul 2015 09:51:41 +1000	[thread overview]
Message-ID: <20150703235141.GQ7943@dastard> (raw)
In-Reply-To: <CADb9451tB71D3XCqcOkDxzpzbdEHqwj7XCZUpL8yg1DzYbpwBw@mail.gmail.com>

On Fri, Jul 03, 2015 at 05:07:29AM -0400, Alex Gorbachev wrote:
> Hello, we are seeing this and similar errors on multiple Supermicro nodes
> running Ceph.  OS is Ubuntu 14.04.2 with kernel 4.1
> 
> Thank you for any info and troubleshooting advice.

Nothing to suggest that this is an XFS problem. Memory reclaim
triggered by network stack memory pressure is causing inode
eviction. While removing the page cache it's falling over in
the generic truncate code doing a radix tree lookup. That's all
generic code - XFS never touches the page cache radix tree directly.

I haven't seen this before - is this a new problem since you
upgraded your kernel to 4.1? Is it repeatable? if yes to both, then
a bisect may be in order to isolate the problematic commit...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-07-03 23:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03  9:07 Failing XFS filesystem underlying Ceph OSDs Alex Gorbachev
2015-07-03 23:51 ` Dave Chinner [this message]
2015-07-04 14:46   ` Alex Gorbachev
2015-07-04 23:38     ` Dave Chinner
2015-07-05  4:25       ` Alex Gorbachev
2015-07-05 23:24         ` Dave Chinner
2015-07-06 19:20           ` Alex Gorbachev
2015-07-07  0:35             ` Dave Chinner
2015-07-22 12:23               ` Alex Gorbachev
2015-08-13 14:25                 ` Alex Gorbachev
2016-03-11  3:26                   ` Alex Gorbachev

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=20150703235141.GQ7943@dastard \
    --to=david@fromorbit.com \
    --cc=ag@iss-integration.com \
    --cc=xfs@oss.sgi.com \
    /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