On 24 July 2014 16:45, Trent W. Buck <[email protected]> wrote: > hannah commodore <[email protected]> > writes: > >> On 24 Jul 2014, at 12:07, Russell Coker <[email protected]> wrote: >> >>> This could be related to TRIM. If you have it enabled it can cause >>> significant delays and if you don't then eventually the SSD will need >>> to clear erase blocks and cause delays for random writes. >> >> Thanks. I'll have to see about how to change the TRIM settings on these >> Plextor >> drives. They don't show up as individual disks to the OS, but just the single >> logical volume > > You change it by mounting the filesystem with -o trim (or not) or > calling fstrim(8). The drives either support it or they don't (they > probably do). The iffy bit will be whether the controller tells the OS > "this [logical] drive doesn't support TRIM", or passes it through to the > physical disks, or if you can configure either behaviour.
I really doubt that particular RAID card supports TRIM. Sorry. > I doubt TRIM is going to be the issue here. Agreed. Losing it hurts your performance a bit in the long run, but it wouldn't cause SSDs to get kicked out of arrays. _______________________________________________ luv-main mailing list [email protected] http://lists.luv.asn.au/listinfo/luv-main
