All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Elliott, Robert (Servers)" <elliott@hpe.com>
To: smitha sunder <sundersmitha@gmail.com>,
	Sitsofe Wheeler <sitsofe@gmail.com>
Cc: fio <fio@vger.kernel.org>
Subject: RE: 4KiB + 64 B formatted drive : Invalid or incomplete multibyte or wide character: write offset=4096, buflen=4096
Date: Fri, 10 Jan 2020 00:45:18 +0000	[thread overview]
Message-ID: <TU4PR8401MB092733E68E23F041756044D9AB380@TU4PR8401MB0927.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CA+zhgFRV0LcX+jZOGgjkfc+5v0iwk=C+hVEoP9e1hnTQEMa2vQ@mail.gmail.com>

That errno is EILSEQ, which the linux block layer generates for a few
reasons related to the T10 protection information (using the internal
return value of BLK_STS_PROTECTION).

Look at your kernel log (dmesg command) for these two possible reasons:
    pr_err("%s: ref tag error at location %llu (rcvd %u)\n",
    pr_err("%s: guard tag error at sector %llu (rcvd %04x, want %04x)\n",



  reply	other threads:[~2020-01-10  0:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08 17:51 4KiB + 64 B formatted drive : Invalid or incomplete multibyte or wide character: write offset=4096, buflen=4096 smitha sunder
2020-01-09  7:40 ` Sitsofe Wheeler
2020-01-09 17:30   ` smitha sunder
2020-01-10  0:45     ` Elliott, Robert (Servers) [this message]
2020-01-10  0:56       ` smitha sunder
2020-01-10  6:35         ` Elliott, Robert (Servers)
2020-01-13  8:04           ` Sitsofe Wheeler
2020-01-17 21:17             ` smitha sunder
2020-01-17 22:15               ` Matthew Eaton
2020-01-18 15:48               ` Sitsofe Wheeler

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=TU4PR8401MB092733E68E23F041756044D9AB380@TU4PR8401MB0927.NAMPRD84.PROD.OUTLOOK.COM \
    --to=elliott@hpe.com \
    --cc=fio@vger.kernel.org \
    --cc=sitsofe@gmail.com \
    --cc=sundersmitha@gmail.com \
    /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.