All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: linux-xfs@vger.kernel.org
Subject: Re: metadata I/O error: block 0x575b6d70,("xfs_trans_read_buf_map") error 4 numblks 16
Date: Wed, 2 Aug 2017 08:23:30 +1000	[thread overview]
Message-ID: <20170801222330.GO17762@dastard> (raw)
In-Reply-To: <e4606e43-468e-431c-1663-6b167cc5648b@profihost.ag>

On Tue, Aug 01, 2017 at 10:12:57AM +0200, Stefan Priebe - Profihost AG wrote:
> Hello,
> 
> under very high load i'm getting the following error on a bcache device
> using XFS:
> XFS (bcache1): metadata I/O error: block 0x575b6d70
> ("xfs_trans_read_buf_map") error 4 numblks 16

#define EINTR            4      /* Interrupted system call */

That's an EINTR error coming from the block layer. This is most
definitely not an error that the block layer should be returning to
the filesystem.

IOWs, you've hit a bcache bug.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  parent reply	other threads:[~2017-08-01 22:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-01  8:12 metadata I/O error: block 0x575b6d70,("xfs_trans_read_buf_map") error 4 numblks 16 Stefan Priebe - Profihost AG
2017-08-01 13:35 ` Emmanuel Florac
2017-08-01 13:50   ` Stefan Priebe - Profihost AG
2017-08-01 14:04     ` Emmanuel Florac
2017-08-01 22:23 ` Dave Chinner [this message]
2017-08-02  6:33   ` Stefan Priebe - Profihost AG
  -- strict thread matches above, loose matches on Subject: below --
2017-08-01  8:03 Stefan Priebe - Profihost AG

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=20170801222330.GO17762@dastard \
    --to=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=s.priebe@profihost.ag \
    /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.