linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robin Hill <robin@robinhill.me.uk>
To: linux-raid@vger.kernel.org
Subject: Re: No resync
Date: Tue, 12 Jan 2010 08:37:54 +0000	[thread overview]
Message-ID: <20100112083753.GA9891@cthulhu.home.robinhill.me.uk> (raw)
In-Reply-To: <4B4C0162.5040807@sauce.co.nz>

[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]

On Tue Jan 12, 2010 at 05:58:10PM +1300, Richard Scobie wrote:

> Leslie Rhorer wrote:
> 
> >> Is there a way to  force assemble a stopped array that has too many
> >> failed devices, while disabling the resync that would normally occur?
> >
> > 	Well, of course if the array has too few members to start (even
> > after the --force), then it won't start and thus won't recync, but assuming
> > one has enough targets to assemble and run the array, I believe
> > --asume-clean will do what you want.  It's in the man page.
> >
> 
> By using force as part of an assemble, all failed devices set to healty 
> again and a resync is immediately started.
> 
> According to the man page --asume-clean is not an available option for 
> assemble.
> 
> I have tried --read-only but that is not an otion either.
> 
> I need to reassemble without resyncing so I can fsck first.
> 
You probably need to start it with missing members then, so it's able to
run but not to resync.

Cheers,
    Robin
-- 
     ___        
    ( ' }     |       Robin Hill        <robin@robinhill.me.uk> |
   / / )      | Little Jim says ....                            |
  // !!       |      "He fallen in de water !!"                 |

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-01-12  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12  4:44 No resync Richard Scobie
2010-01-12  4:52 ` Leslie Rhorer
2010-01-12  4:58   ` Richard Scobie
2010-01-12  8:37     ` Robin Hill [this message]
2010-01-12 18:27       ` Richard Scobie
2010-01-18  3:48         ` Neil Brown

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=20100112083753.GA9891@cthulhu.home.robinhill.me.uk \
    --to=robin@robinhill.me.uk \
    --cc=linux-raid@vger.kernel.org \
    /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).