From: Paul Clements <paul.clements@steeleye.com>
To: Jeff Breidenbach <jeff@jab.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: split RAID1 during backups?
Date: Mon, 24 Oct 2005 09:26:56 -0400 [thread overview]
Message-ID: <435CE120.2030003@steeleye.com> (raw)
In-Reply-To: <E1EU16u-0002ZK-00@toko.jab.org>
Jeff Breidenbach wrote:
>>However you will endure a rebuild on md0 when you re-add the disk, but
>>given everything is mounted read-only, you should not practically be
>>doing anything
>
>
> If the rebuild operation is a no-op, then that sounds like a great
> idea. If the rebuild operation requires scanning over all data in both
> drives, I think that's going to be at least as expensive as the
> current 10 hour process.
You seem to be using a pretty bleeding edge kernel (2.6.12). If you were
to upgrade to 2.6.13, the md bitmap (intent logging) functionality that
is present in that kernel will allow the resync to be a no-op.
Basically, the bitmap tracks writes to the md array, and then when
resync occurs, only syncs blocks that have been written. Since the array
would be readonly while you're doing backups, there would be nothing to
resync.
See the list archives for more details on md bitmap.
--
Paul
next prev parent reply other threads:[~2005-10-24 13:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 12:07 split RAID1 during backups? Jeff Breidenbach
2005-10-24 13:26 ` Paul Clements [this message]
2005-10-24 18:55 ` dean gaudet
-- strict thread matches above, loose matches on Subject: below --
2005-10-30 3:06 Jeff Breidenbach
2005-10-26 8:17 Jeff Breidenbach
2005-10-27 13:23 ` Bill Davidsen
2005-10-25 5:01 Jeff Breidenbach
2005-10-25 3:37 Jeff Breidenbach
2005-10-25 4:07 ` dean gaudet
2005-10-25 8:35 ` Norman Schmidt
2005-10-25 17:51 ` John Stoffel
2005-10-25 19:20 ` Norman Schmidt
2005-10-25 18:04 ` John Stoffel
2005-10-25 18:13 ` Paul Clements
2005-10-25 20:05 ` Bill Davidsen
2005-10-26 18:15 ` Dan Stromberg
2005-10-24 20:28 Jeff Breidenbach
2005-10-24 20:58 ` John Stoffel
2005-10-25 22:18 ` David Greaves
2005-10-24 10:57 Jeff Breidenbach
2005-10-24 11:22 ` Jurriaan Kalkman
2005-10-24 11:37 ` Brad Campbell
2005-10-24 19:05 ` Bill Davidsen
2005-10-25 4:30 ` Thomas Garner
2005-10-27 0:04 ` Christopher Smith
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=435CE120.2030003@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=jeff@jab.org \
--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).