From: Jens Axboe <axboe@kernel.dk>
To: Junichi Nomura <j-nomura@ce.jp.nec.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
Chaitanya Kulkarni <chaitanya.kulkarni@hgst.com>
Subject: Re: [REGRESSION v4.10-rc1] blkdev_issue_zeroout() returns -EREMOTEIO on the first call for SCSI device that doesn't support WRITE SAME
Date: Fri, 3 Feb 2017 08:21:31 -0700 [thread overview]
Message-ID: <d360a634-2c95-2de5-8647-4e740e92e10a@kernel.dk> (raw)
In-Reply-To: <cc14c28a-0f0a-640a-b576-cdfbaee75dc5@ce.jp.nec.com>
On 02/03/2017 12:55 AM, Junichi Nomura wrote:
> 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 blkdev_issue_zeroout().
> That came from sd driver because WRITE SAME was sent to the device
> which didn't support it.
>
> The problem was introduced by commit e73c23ff736e ("block: add async
> variant of blkdev_issue_zeroout"). Before the commit, blkdev_issue_zeroout
> fell back to normal zero writing when WRITE SAME failed and it seems
> sd driver's heuristics depends on that behaviour.
CC Christoph and Chaitanya.
--
Jens Axboe
next prev parent reply other threads:[~2017-02-03 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 7:55 [REGRESSION v4.10-rc1] blkdev_issue_zeroout() returns -EREMOTEIO on the first call for SCSI device that doesn't support WRITE SAME Junichi Nomura
2017-02-03 15:21 ` Jens Axboe [this message]
2017-02-03 16:12 ` Christoph Hellwig
2017-02-03 16:14 ` Jens Axboe
2017-02-03 22:45 ` Martin K. Petersen
2017-02-03 22:45 ` Martin K. Petersen
2017-02-04 3:17 ` Jens Axboe
2017-02-04 8:48 ` Christoph Hellwig
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=d360a634-2c95-2de5-8647-4e740e92e10a@kernel.dk \
--to=axboe@kernel.dk \
--cc=chaitanya.kulkarni@hgst.com \
--cc=hch@lst.de \
--cc=j-nomura@ce.jp.nec.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.