All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Cracauer <cracauer@cons.org>
To: Carlos Carvalho <carlos@fisica.ufpr.br>
Cc: Martin Cracauer <cracauer@cons.org>, linux-raid@vger.kernel.org
Subject: Re: replace disk in raid5 without linux noticing?
Date: Sun, 23 Apr 2006 12:43:50 -0400	[thread overview]
Message-ID: <20060423124350.B38675@cons.org> (raw)
In-Reply-To: <17482.27751.358345.185741@fisica.ufpr.br>; from carlos@fisica.ufpr.br on Sat, Apr 22, 2006 at 02:48:23PM -0300

Carlos Carvalho wrote on Sat, Apr 22, 2006 at 02:48:23PM -0300: 
> Martin Cracauer (cracauer@cons.org) wrote on 22 April 2006 11:08:
>  >> stop the array
>  >> dd warning disk => new one
>  >> remove warning disk
>  >> assemble the array again with the new disk
>  >> 
>  >> The inconvenience is that you don't have the array during the copy.
>  >
>  >Stopping the array and restarting it as readonly will give you access
>  >to the data while that copy is in progress.
> 
> Yes but then you could just switch it to read-only without stopping.

I believe that would be fine to do the whole operation.  Filesystem
read-only, then md read-only, copy disk, then you need to unmount and
stop the md to restart it with the new disk.

If the final disk change involves a powerdown and putting the new disk
on the physical interface that the old one was on it should be
transparent.

%%

BTW, last time I tested a Linux software RAID-5 by ripping out an
active disk I noticed that while the filesystem stayed up and usable,
a currently ongoing system call would not return and block forever.

Is that a know behaviour?

Martin
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@cons.org>   http://www.cons.org/cracauer/
FreeBSD - where you want to go, today.      http://www.freebsd.org/

      reply	other threads:[~2006-04-23 16:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-19 14:31 replace disk in raid5 without linux noticing? Dexter Filmore
2006-04-19 16:31 ` Shai
2006-04-19 17:03   ` Ming Zhang
2006-04-19 17:41     ` Brendan Conoboy
2006-04-19 18:16       ` Ming Zhang
2006-04-20 15:22         ` Gabor Gombas
2006-04-20 15:24           ` Ming Zhang
2006-04-21 18:23   ` Dexter Filmore
2006-04-21 22:25     ` Carlos Carvalho
2006-04-22 15:08       ` Martin Cracauer
2006-04-22 17:48         ` Carlos Carvalho
2006-04-23 16:43           ` Martin Cracauer [this message]

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=20060423124350.B38675@cons.org \
    --to=cracauer@cons.org \
    --cc=carlos@fisica.ufpr.br \
    --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 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.