From: Christoph Hellwig <hch@lst.de>
To: Boris Burkov <boris@bur.io>
Cc: Christoph Hellwig <hch@lst.de>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com,
sbehrens@giantdisaster.de
Subject: Re: [PATCH] btrfs: btrfs_log_dev_io_error() on all bio errors
Date: Fri, 27 Mar 2026 11:22:53 +0100 [thread overview]
Message-ID: <20260327102253.GA18582@lst.de> (raw)
In-Reply-To: <20260316162951.GA1074179@zen.localdomain>
The work week is almost over, and I'm still in the explore and
experimentation phase. So please go ahead and log extra error,
although traditionally only BLK_STS_IOERR, BLK_STS_PROTECTION and
BLK_STS_MEDIUM are real I/O ero I/O error. The rest is unexpected
here, and maybe just logging a message about that would make sense
here.
prev parent reply other threads:[~2026-03-27 10:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 19:26 [PATCH] btrfs: btrfs_log_dev_io_error() on all bio errors Boris Burkov
2026-03-13 21:18 ` Qu Wenruo
2026-03-16 16:20 ` Christoph Hellwig
2026-03-16 16:29 ` Boris Burkov
2026-03-17 13:59 ` Christoph Hellwig
2026-03-17 16:16 ` David Sterba
2026-03-27 10:22 ` Christoph Hellwig [this message]
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=20260327102253.GA18582@lst.de \
--to=hch@lst.de \
--cc=boris@bur.io \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.de \
/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