Linux RAID subsystem development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Dexter Filmore <Dexter.Filmore@gmx.de>, linux-raid@vger.kernel.org
Subject: Re: How to force stopping an array`
Date: Fri, 30 May 2008 11:54:30 +1000	[thread overview]
Message-ID: <18495.24150.151366.956469@notabene.brown> (raw)
In-Reply-To: message from Justin Piszcz on Tuesday May 27

On Tuesday May 27, jpiszcz@lucidpixels.com wrote:
> >>> Exactly. reboot pretty much deosn't do any good, afterwars the raid
> >>> resyncs,
> >>> which takes full 7h here.
> >>
> >> There shouldn't be a resync.  Presumably nothing is writing to the
> >> array, and moments after the last write, the array will have been
> >> flagged as 'clean' and will not require a resync after a reboot.
>                                               ^^^^^^^^^^^^^^^^^^^^^^
> 
> His host crashed != reboot so that is the reason for the resync.

If the host crashes will nothing is being written to the array, the
array would be marked clean, so a resync will still not be required.
You should only get a resync if the host crashing within 200msecs of
the last write completing.

NeilBrown

  reply	other threads:[~2008-05-30  1:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 21:43 How to force stopping an array` Dexter Filmore
2008-05-26 22:06 ` Justin Piszcz
2008-05-26 22:26   ` Dexter Filmore
2008-05-26 22:30     ` Justin Piszcz
2008-05-26 23:02       ` Dexter Filmore
2008-05-27  0:05         ` NeilBrown
2008-05-27 10:49           ` Dexter Filmore
2008-05-27 19:42             ` Justin Piszcz
2008-05-30  1:54               ` Neil Brown [this message]
2008-05-30 11:18                 ` Dexter Filmore

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=18495.24150.151366.956469@notabene.brown \
    --to=neilb@suse.de \
    --cc=Dexter.Filmore@gmx.de \
    --cc=jpiszcz@lucidpixels.com \
    --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