Re: [PATCH] block: don't try Write Same from __blkdev_issue_zeroout

te Same from blkdev_issue_zeroout an don't try it > at all from __blkdev_issue_zeroout as a non-invasive workaround. > > Signed-off-by: Christoph Hellwig <h...@lst.de> > Reported-by: Junichi Nomura <j-nom...@ce.jp.nec.com> > Fixes: e73c23ff ("block: add async variant of blkd

[REGRESSION v4.10-rc1] blkdev_issue_zeroout() returns -EREMOTEIO on the first call for SCSI device that doesn't support WRITE SAME

I found following ext4 error occurs on a certain storage since v4.10-rc1: EXT4-fs (sdc1): Delayed block allocation failed for inode 12 at logical offset 100 with max blocks 2 with error 121 EXT4-fs (sdc1): This should not happen!! Data will be lost Error 121 (EREMOTEIO) was returned from

Re: [PATCH 05/16] dm: always defer request allocation to the owner of the request_queue

On 01/25/17 01:39, Mike Snitzer wrote: > On Tue, Jan 24 2017 at 9:20am -0500, Christoph Hellwig wrote: >> On Tue, Jan 24, 2017 at 05:05:39AM -0500, Mike Snitzer wrote: >>> possible and is welcomed cleanup. The only concern I have is that using >>> get_request() for the old