From: Karel Zak <kzak@redhat.com>
To: Lutz Vieweg <lvml@5t9.de>
Cc: util-linux@vger.kernel.org
Subject: Re: fstrim tries to discard data beyond the last sector of a device
Date: Tue, 18 Nov 2014 12:03:29 +0100 [thread overview]
Message-ID: <20141118110329.GG6704@x2.net.home> (raw)
In-Reply-To: <m4f77a$ivg$1@ger.gmane.org>
On Tue, Nov 18, 2014 at 11:32:10AM +0100, Lutz Vieweg wrote:
> I'm kind of concerned that there was no reaction on my recent
> post - maybe the subject I chose wasn't colorful enough to
> draw attention on what I think is a real threat to data integrity
> on persistent storage.
This is upstream development mailing list, it's better to report bugs
to distribution specific mailing lists or bug tracking systems.
what is your fstrim command line, it would be nice to see strace
output to verify the ioctl return code.
> The "Logical block address out of range" error amongst the (cited below)
> messages says no less than that fstrim issued a fitrim ioctl that
> was asking the device to discard the content of sectors well beyond
> the boundaries of the device. If it wasn't for the "end of the physical
> device" making the SSD return an error, if instead there was another
> partition behind a filesystem to trim, then valuable, live data
> would have been discarded.
>
> If email to this list is not a suitable form to report such issues,
> please let me know where I can report this issue better.
Maybe you can ask linux-fs mailing list. It really does not seem like
fstrim command issue.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-11-18 11:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 16:07 fstrim: "fitrim ioctl failed: input/output error" -> "Logical block address out of range" Lutz Vieweg
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 [this message]
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=20141118110329.GG6704@x2.net.home \
--to=kzak@redhat.com \
--cc=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).