From: Bernd Schubert <bernd.schubert-97jfqw80gc6171pxa8y+qA@public.gmane.org>
To: Lutz Vieweg <lvml-i6VILw57VWU@public.gmane.org>,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org
Subject: Re: fstrim on newly created filesystem tries to discard data beyond the last sector of a device
Date: Mon, 24 Nov 2014 20:43:38 +0100 [thread overview]
Message-ID: <54738A6A.40906@fastmail.fm> (raw)
In-Reply-To: <5473873E.1070101-i6VILw57VWU@public.gmane.org>
> Then there's another idea: The device is a SATA SSD, but attached
> to a SAS2 expander chip on the backplane of the server (LSI SAS2X28)
> which in turn is connected to a LSI SAS HBA 9207-4i4e.
> could maybe, just maybe, the TRIM command be modified wrongly
> on its way through these / their respective drivers?
>
Yeah, it is a known issue with LSI firmware.
http://osdir.com/ml/dm-devel/2013-09/msg00126.html
Last time I checked (FWv19?) it was still not fixed.
Cheers,
Bernd
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-11-24 19:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3qnrg$5gc$1@ger.gmane.org>
[not found] ` <m4f77a$ivg$1@ger.gmane.org>
2014-11-21 17:09 ` fstrim on newly created filesystem tries to discard data beyond the last sector of a device 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
[not found] ` <5473873E.1070101-i6VILw57VWU@public.gmane.org>
2014-11-24 19:43 ` Bernd Schubert [this message]
[not found] ` <54738A6A.40906-97jfqw80gc6171pxa8y+qA@public.gmane.org>
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=54738A6A.40906@fastmail.fm \
--to=bernd.schubert-97jfqw80gc6171pxa8y+qa@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-xfs-VZNHf3L845pBDgjK7y7TUQ@public.gmane.org \
--cc=lvml-i6VILw57VWU@public.gmane.org \
--cc=util-linux-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).