Piergiorgio> There is LVM on top, I wonder if this makes a difference.
It does not.
Hi all,
it is my understanding that, when backed by SSDs (and configured for
passing down TRIM requests), ThinLVM are prime condidate for trigger the
bug.
But what about ThinLVM + MDRAID10 on top of normal (spinning HDD)?
Generally SATA HDDs do not support TRIM/UNMAP, but when using ThinLVM,
the thin-provision mapper advertise TRIM support, and indeed an "fstrim
-v /" succeeds.
I *think* that, as this TRIM command is processed way above the ATA
layer (it is processed inside the device-mapper code), the bug should
not happen here. Is it correct? Are we safe with ThinLVM + MDRAID10 + HDDs?
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@xxxxxxxxxx - info@xxxxxxxxxx
GPG public key ID: FF5F32A8
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
