All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Turmel <philip@turmel.org>
To: Mark Knecht <markknecht@gmail.com>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: md: kicking non-fresh sdf3 from array!
Date: Thu, 27 Dec 2012 15:25:17 -0500	[thread overview]
Message-ID: <50DCAEAD.3090205@turmel.org> (raw)
In-Reply-To: <50DCAE69.1080003@turmel.org>

Whoops!  The list was dropped...

On 12/27/2012 03:24 PM, Phil Turmel wrote:
> On 12/27/2012 03:20 PM, Mark Knecht wrote:
>> Thanks Phil,
>>    I've added the device back in and the rebuild is proceeding.
>>
>>    So the new piece of info here for me is this idea of a bitmap. I'll
>> have to go look into that, but a quick question - is that something
>> that can be added to the RAID6 at this time, or can you only do that
>> when you first build it? As I have some issue with my (possibly)
>> initramfs I expect I'll kick the devices a few more times before I get
>> it worked out. Would be nice if putting the disk back in didn't take
>> so long.
> 
> You can add a bitmap to any v1.x array after the fact with "--grow".  It
> does add a little overhead to the write path, so you might not want it
> in a heavily loaded server.  For a test-bed or other system prone to
> crashes, it's a godsend.
> 
> Phil
> 


  parent reply	other threads:[~2012-12-27 20:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-27 18:48 md: kicking non-fresh sdf3 from array! Mark Knecht
2012-12-27 19:57 ` Phil Turmel
     [not found]   ` <CAK2H+ecBALbrpshYQ5TZhuOJh_kgXqi_C90Zp-FtCgaE4dEgSw@mail.gmail.com>
     [not found]     ` <50DCAE69.1080003@turmel.org>
2012-12-27 20:25       ` Phil Turmel [this message]
2012-12-27 20:52         ` Mark Knecht
2012-12-27 21:38           ` Mark Knecht

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=50DCAEAD.3090205@turmel.org \
    --to=philip@turmel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=markknecht@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.