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@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
