linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Majed B." <majedb@gmail.com>
To: Michael Evans <mjevans1983@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: reconstruct raid superblock
Date: Thu, 17 Dec 2009 14:45:26 +0300	[thread overview]
Message-ID: <70ed7c3e0912170345s9482d6ek1950422359b3da88@mail.gmail.com> (raw)
In-Reply-To: <4877c76c0912170322oda9d5f0tdb13c37517bb5e31@mail.gmail.com>

Is that because the disk was removed from the array and/or lost its
superblock info?

I've had problems with arrays before during resync, and I was able to
stop them and resume them again, sometimes after disks jump out of the
array (but still retaining their superblock info).

On Thu, Dec 17, 2009 at 2:22 PM, Michael Evans <mjevans1983@gmail.com> wrote:
> He's using v0.9 superblocks; even if the replaced device was at 99%
> complete it would still have to restart from 0% when re-added.
>



-- 
       Majed B.

  reply	other threads:[~2009-12-17 11:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17  3:53 reconstruct raid superblock Carl Karsten
     [not found] ` <70ed7c3e0912162117n3617556p3a8decef94f33a1c@mail.gmail.com>
     [not found]   ` <70ed7c3e0912162121v5df1b972x6d9176bdf7e27401@mail.gmail.com>
2009-12-17  6:18     ` Carl Karsten
     [not found]       ` <4877c76c0912162226w3dfbdbb2t4b13e016f53728a0@mail.gmail.com>
     [not found]         ` <549053140912162236l134c38a9v490ba172231e6b8c@mail.gmail.com>
2009-12-17  7:35           ` Michael Evans
2009-12-17 10:35     ` Majed B.
2009-12-17 11:22       ` Michael Evans
2009-12-17 11:45         ` Majed B. [this message]
2009-12-17 14:15       ` Carl Karsten
2009-12-17 14:39         ` Majed B.
2009-12-17 15:06           ` Carl Karsten
2009-12-17 15:40             ` Majed B.
2009-12-17 16:17               ` Carl Karsten
2009-12-17 18:07                 ` Majed B.
2009-12-17 19:18                   ` Michael Evans

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=70ed7c3e0912170345s9482d6ek1950422359b3da88@mail.gmail.com \
    --to=majedb@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=mjevans1983@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).