public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.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: Tue, 1 Aug 2017 15:35:48 +0200	[thread overview]
Message-ID: <20170801153548.15cf74ef@harpe.intellique.com> (raw)
In-Reply-To: <e4606e43-468e-431c-1663-6b167cc5648b@profihost.ag>

[-- Attachment #1: Type: text/plain, Size: 1462 bytes --]

Le Tue, 1 Aug 2017 10:12:57 +0200
Stefan Priebe - Profihost AG <s.priebe@profihost.ag> écrivait:

> 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
> XFS (bcache1): xfs_imap_to_bp: xfs_trans_read_buf() returned error -4.
> XFS (bcache1): xfs_do_force_shutdown(0x8) called from line 3519 of
> file fs/xfs/xfs_inode.c. Return address = 0xffffffff993441ff
> XFS (bcache1): Corruption of in-memory data detected. Shutting down
> filesystem
> XFS (bcache1): Please umount the filesystem and rectify the problem(s)
> XFS (bcache1): xfs_log_force: error -5 returned.
> XFS (bcache1): xfs_log_force: error -5 returned.
> XFS (bcache1): xfs_log_force: error -5 returned.
> 
> The used kernel is 4.4.79 based while using an opensuses patchset. Is
> this something which is a known problem or something suse has broken?

Do you know if the patchset includes Eric Wheeler's stability patches
for bcache?

Also please post the output from dmesg with the complete trace.

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

[-- Attachment #2: Signature digitale OpenPGP --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2017-08-01 13:35 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 [this message]
2017-08-01 13:50   ` Stefan Priebe - Profihost AG
2017-08-01 14:04     ` Emmanuel Florac
2017-08-01 22:23 ` Dave Chinner
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=20170801153548.15cf74ef@harpe.intellique.com \
    --to=eflorac@intellique.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox