Linux RAID subsystem development
 help / color / mirror / Atom feed
From: David Brown <david.brown@hesbynett.no>
To: Wolfgang Denk <wd@denx.de>
Cc: Curtis J Blank <curt@curtronics.com>,
	"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>
Subject: Re: Best way (only?) to setup SSD's for using TRIM
Date: Thu, 01 Nov 2012 17:41:28 +0100	[thread overview]
Message-ID: <5092A638.8060307@hesbynett.no> (raw)
In-Reply-To: <20121101150144.6BA1D2005D0@gemini.denx.de>

On 01/11/12 16:01, Wolfgang Denk wrote:
> Dear David,
>
> In message <50922FA4.7070702@hesbynett.no> 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.)



      reply	other threads:[~2012-11-01 16:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-28 18:59 Best way (only?) to setup SSD's for using TRIM Curtis J Blank
     [not found] ` <CAH3kUhHX28yNXggLuA+D_cH0STY-Rn_BjxVt_bh1sMeYLnM0cw@mail.gmail.com>
2012-10-29 14:35   ` Curtis J Blank
     [not found]   ` <508E9289.5070904@curtronics.com>
     [not found]     ` <CAH3kUhEdOO+GXKK6ALFUYJdYeTw2Mx-PF9M=0vQvkzzidihxSg@mail.gmail.com>
2012-10-29 17:08       ` Curt Blank
2012-10-29 18:06         ` Roberto Spadim
2012-10-30  9:49 ` David Brown
2012-10-30 14:29   ` Curtis J Blank
2012-10-30 14:33     ` Roberto Spadim
2012-10-30 15:55     ` David Brown
2012-10-30 18:30       ` Curt Blank
2012-10-30 18:43         ` Roberto Spadim
2012-10-30 19:59         ` Chris Murphy
2012-10-31  8:32           ` David Brown
2012-10-31 13:44             ` Roberto Spadim
     [not found]             ` <CAJEsFnkM9w0kNbNd51ShP0uExvsZE6V9h3WKKs3nxWfncUCYJA@mail.gmail.com>
2012-10-31 14:11               ` David Brown
2012-11-13 13:39                 ` Ric Wheeler
2012-11-13 15:13                   ` David Brown
2012-11-13 15:39                     ` Ric Wheeler
2012-10-31 17:34             ` Curtis J Blank
2012-10-31 20:04               ` David Brown
2012-11-01  1:54                 ` Curtis J Blank
2012-11-01  8:15                   ` David Brown
2012-11-01 15:01                     ` Wolfgang Denk
2012-11-01 16:41                       ` David Brown [this message]

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=5092A638.8060307@hesbynett.no \
    --to=david.brown@hesbynett.no \
    --cc=curt@curtronics.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=wd@denx.de \
    /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