linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Robinson <john.robinson@anonymous.org.uk>
To: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID without superblock
Date: Mon, 20 Apr 2009 00:33:08 +0100	[thread overview]
Message-ID: <49EBB4B4.40102@anonymous.org.uk> (raw)
In-Reply-To: <20090419210200.GA6942@lazy.lzy>

On 19/04/2009 22:04, Piergiorgio Sartor wrote:
>> Why would you want a RAID-1 without superblock. I generally
>> consider that a legacy configuration.
> 
> Ah! I was thinking about it as a method to
> build a RAID with an already existing disk
> or partition, which cannot be modified.

Well, something somewhere is going to have to change; at the very least 
you're going to have to stop whatever's using the filesystem, unmount 
it, do whatever to create the new RAID-1 incorporating the original 
disc, and remount the filesystem now on the new md device.

So instead you could create a new RAID-1 md device with (a superblock 
and) one disc missing, create a filesystem on it, stop your original 
filesystem, copy its contents to the new md device, mount it, and add 
the original disc into the new md device.

If you've too much data to be able to afford the downtime copying, use 
rsync with the appropriate options while the filesystem's still in use, 
then again after it's been stopped; the second copy will complete far 
faster than the full copy.

Cheers,

John.


  parent reply	other threads:[~2009-04-19 23:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19 11:47 RAID without superblock Piergiorgio Sartor
2009-04-19 20:44 ` NeilBrown
2009-04-19 21:04   ` Piergiorgio Sartor
2009-04-19 21:57     ` Andrew Burgess
2009-04-20 18:10       ` Piergiorgio Sartor
2009-04-20 18:17         ` Christopher Chen
2009-04-19 23:33     ` John Robinson [this message]
2009-04-20  5:13     ` Tapani Tarvainen

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=49EBB4B4.40102@anonymous.org.uk \
    --to=john.robinson@anonymous.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=piergiorgio.sartor@nexgo.de \
    /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).