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 16:04:12 +0200 [thread overview]
Message-ID: <20170801160412.1ee5be5b@harpe.intellique.com> (raw)
In-Reply-To: <b29b31a1-edb9-47f4-a641-11ecfc289c99@profihost.ag>
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
Le Tue, 1 Aug 2017 15:50:20 +0200
Stefan Priebe - Profihost AG <s.priebe@profihost.ag> écrivait:
> Hello Emmanuel,
>
> yes there are bcache patches already applied:
> 0002-bcache-bch_writeback_thread-is-not-freezable.patch
> 0003-bcache-bch_allocator_thread-is-not-freezable.patch
> 0001-bcache-partition-support-add-16-minors-per-bcacheN-d.patch
> 0044-bcache-Remove-deprecated-create_workqueue.patch
> 0045-bcache-Remove-redundant-parameter-for-cache_alloc.patch
> 0046-bcache-update-document-info.patch
> 0047-bcache-Remove-redundant-block_size-assignment.patch
> 0048-bcache-register_bcache-call-blkdev_put-when-cache_al.patch
> 0049-bcache-pr_err-more-meaningful-error-message-when-nr_.patch
> 0071-bcache-switch-to-using-blk_queue_write_cache.patch
> 0092-bcache-use-op_is_write-instead-of-checking-for-REQ_W.patch
> 0110-bcache-use-bio-op-accessors.patch
> 0253-bcache-use-op_is_sync-to-check-for-synchronous-reque.patch
> 0344-bcache-debug-avoid-accessing-.bi_io_vec-directly.patch
> 0002-bcache-fix-calling-ida_simple_remove-with-incorrect-minor.patch
> 0001-bcache-force-trigger-gc.patch
> 0001-bcache-only-recovery-I-O-error-for-writethrough-mode.patch
Good.
> There is no trace involved as there is no kernel bug triggered. That's
> the whole output.
Too bad :/ What are the underlying devices? No error at all at the
kernel level? No IO error? Is bcache configured write-back or
write-through?
--
------------------------------------------------------------------------
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 --]
next prev parent reply other threads:[~2017-08-01 14:04 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 [this message]
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=20170801160412.1ee5be5b@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