From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: linux-xfs@vger.kernel.org
Subject: metadata I/O error: block 0x575b6d70,("xfs_trans_read_buf_map") error 4 numblks 16
Date: Tue, 1 Aug 2017 10:12:57 +0200 [thread overview]
Message-ID: <e4606e43-468e-431c-1663-6b167cc5648b@profihost.ag> (raw)
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?
Thanks!
Greets,
Stefan
next reply other threads:[~2017-08-01 8:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 8:12 Stefan Priebe - Profihost AG [this message]
2017-08-01 13:35 ` metadata I/O error: block 0x575b6d70,("xfs_trans_read_buf_map") error 4 numblks 16 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
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=e4606e43-468e-431c-1663-6b167cc5648b@profihost.ag \
--to=s.priebe@profihost.ag \
--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