Re: Best way (only?) to setup SSD's for using TRIM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/11/12 16:01, Wolfgang Denk wrote:
Dear David,

In message <50922FA4.7070702@xxxxxxxxxxxx> you wrote:

If you make your big raid1 pair an LVM physical volume, you can split it
into logical volumes as and when you want, and re-size them whenever
necessary.  Note, however, that the unpartitioned space within the LVM
physical volume is still "used" as far as the SSD is concerned, since
the initial raid1 synchronisation has written to it.  So only space

What if the creation of the array was done with "--assume-clean" ?


I think in that case you will avoid writing to the disks - but you will have trouble if you try to check or scrub the disk, or if it runs a resync due to an unclean shutdown.

I suppose new SSDs may consistently return all zeros or all ones when read - so if they are consistent then you should be fine to "--assume-clean" (for raid1).

However, I think that resyncs currently write data to the second drive without checking if it is out of sync, which would put you back where you started. (I believe there are patches on their way to change that behaviour to save writes on SSDs - but re-writing everything on the second disk is the fastest resync method for normal hard disk setups.)


--
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


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux