On Wed Nov 11, 2009 at 09:01:46AM -0600, Leslie Rhorer wrote:

quoted

quoted

If you have a temporary space for your data, I'd suggest you move it
out and go for an internal bitmap solution. It certainly beats the
patch work you're going to have to do on the startup scripts (and
every time you update mdadm, or the distro).

There should be no need to move the data off - you can add an internal
bitmap using the --grow option.  An internal bitmap does have more of an
overhead than an external one though.

	I thought I remembered reading in the man page than an internal
bitmap could only be added when the array was created?  Is that incorrect?  

I've certainly done this with mdadm 2.6.8 - I guess older versions may
not be able to though.  It's only able to use a limited amount of space
though (whatever's left between the metadata and the data/end of disk),
so you don't get as much (if any) control of the chunk size.

Cheers,
    Robin
-- 
     ___        
    ( ' }     |       Robin Hill        [off-list ref] |
   / / )      | Little Jim says ....                            |
  // !!       |      "He fallen in de water !!"                 |