Re: [PATCH] btrfs: btrfs_log_dev_io_error() on all bio errors

[Christoph Hellwig <hch@lst.de>]

On Fri, Mar 13, 2026 at 12:26:05PM -0700, Boris Burkov wrote:
> As far as I can tell, we never intentionally constrained ourselves to
> these status codes, and it is misleading and surprising to lack the
> bdev error logging when we get a different error code from the block
> layer. This can lead to jumping to a wrong conclusion like "this
> system didn't see any bio failures but aborted with EIO".
> 
> For example on nvme devices, I observe many failures coming back as
> BLK_STS_MEDIUM. It is apparent that the nvme driver returns a variety of
> BLK_STS_* status values in nvme_error_status().

This goes all the way back to adding the error counts in commit
442a4f6308e69.  The block error values are a bit of a mess and it's
on my todo list to sort them out - only a small number of them should
even be seen here.  I'd suggest to leave things as-is for now, and
I'll make sure you're included in the discussion when I get around
to attack the block status vs file system issues, which will hopefully
be very soon.