From: Lutz Vieweg <lvml@5t9.de>
To: util-linux@vger.kernel.org
Subject: fstrim: "fitrim ioctl failed: input/output error" -> "Logical block address out of range"
Date: Mon, 10 Nov 2014 17:07:12 +0100 [thread overview]
Message-ID: <m3qnrg$5gc$1@ger.gmane.org> (raw)
Hi,
when I use "fstrim" on a just newly "mkfs.xfs /dev/sdb"-ed
filesystem on a newly mounted SSD (Crucial_CT1024M550SSD1,
firmware MU01), I get (after some activity on the device)
this error message:
> fitrim ioctl failed: input/output error
Looking into the dmesg output reveals:
> [1039455.530947] sd 0:0:1:0: [sdb]
> [1039455.533192] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> [1039455.535369] sd 0:0:1:0: [sdb]
> [1039455.537521] Sense Key : Illegal Request [current]
> [1039455.539684] Info fld=0x772cdab0
> [1039455.541802] sd 0:0:1:0: [sdb]
> [1039455.543877] Add. Sense: Logical block address out of range
> [1039455.545966] sd 0:0:1:0: [sdb] CDB:
> [1039455.548008] Unmap/Read sub-channel: 42 00 00 00 00 00 00 00 18 00
> [1039455.550080] end_request: critical target error, dev sdb, sector 1999428272
(I bought 4 of the same SSD model, and the error occurs the same
with the other exemplars, so I assume this is not some hardware issue.)
According to smartctl, the capacity of this SSD is:
> User Capacity: 1,024,209,543,168 bytes [1.02 TB]
> Sector Sizes: 512 bytes logical, 4096 bytes physical
And cat /proc/partitions tells:
> major minor #blocks name
> 8 16 1000204632 sdb
Kernel is mainline linux-3.17.1
fstrim --version says:
> fstrim from util-linux 2.23.2
(Distribution is CentOS 7, if that matters.)
Does anyone have a clue what's going wrong, here?
Regards,
Lutz Vieweg
next reply other threads:[~2014-11-10 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 16:07 Lutz Vieweg [this message]
2014-11-18 10:32 ` fstrim tries to discard data beyond the last sector of a device Lutz Vieweg
2014-11-18 11:03 ` Karel Zak
2014-11-21 16:44 ` Lutz Vieweg
2014-11-21 17:09 ` fstrim on newly created filesystem " Lutz Vieweg
2014-11-21 21:20 ` Mike Frysinger
2014-11-24 9:23 ` Karel Zak
2014-11-24 12:25 ` Lukáš Czerner
2014-11-24 19:30 ` Lutz Vieweg
2014-11-24 19:43 ` Bernd Schubert
2014-11-24 20:03 ` Lutz Vieweg
2014-11-24 20:18 ` Bernd Schubert
2014-11-24 21:24 ` Dave Chinner
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='m3qnrg$5gc$1@ger.gmane.org' \
--to=lvml@5t9.de \
--cc=util-linux@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).