From: Norman Schmidt <schmidt@naa.net>
To: linux-raid@vger.kernel.org
Subject: Re: split RAID1 during backups?
Date: Tue, 25 Oct 2005 21:20:41 +0200 [thread overview]
Message-ID: <435E8589.9000303@naa.net> (raw)
In-Reply-To: <17246.28805.267226.810872@smtp.charter.net>
John Stoffel schrieb:
> Norman> What you should be able to do with software raid1 is the
> Norman> following: Stop the raid, mount both underlying devices
> Norman> instead of the raid device, but of course READ ONLY. Both
> Norman> contain the complete data and filesystem, and in addition to
> Norman> that the md superblock at the end. Both should be identical
> Norman> copies of that. Thus, you do not have to resync
> Norman> afterwards. You then can backup the one disk while serving the
> Norman> web server from the other. When you are done, unmount,
> Norman> assemble the raid, mount it and go on.
>
> Umm... so what you're proposing would mean that he would have to stop
> his application, make sure nothing is accessing that volume, and then
> restart the application?
>
> Somehow I don't see that happening.
>
> Why do you feel that you have to stop and umount the volume for the
> splitting off of a read-only mirror pair for backups?
>
> John
All this "pulling a disk" sounded to me like a resync, and with that
much data and slow access this resync would take ages.
And as far as I remember, there was a suggestion with stopping or
interrupting applications anyway, was there not? Unfortunately, I have
thrown most of the posts away.
If you keep the volume running, ok - it should still work from the data
integrity point of view. But if you keep using the data from a
functional raid1 (/dev/md1 on /data), you cannot disentangle the access,
since the raid1 will read from both mirrors. But what was desired was a
faster backup and being able to continue serving the data.
If one disk (without the read-balancing of raid1) would provide enough
treoughput for the webserver, one could even do the following:
mount /dev/md1 /writeaccess
mount -r /dev/hda /data
mount -r /dev/hdc /backup
So write from /weiteacces (mirrored to both drives) and read from one
for the webserver (statically) and from the other one for the backup.
Could that work?
Norman.
--
Norman Schmidt Institut fuer Physikal. u. Theoret. Chemie
Dipl.-Chem. Univ. Friedrich-Alexander-Universitaet
schmidt@naa.net Erlangen-Nuernberg
+49 9131 852 7321 IT-Systembetreuer Physikalische Chemie
next prev parent reply other threads:[~2005-10-25 19:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 3:37 split RAID1 during backups? 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 [this message]
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
-- 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-24 20:28 Jeff Breidenbach
2005-10-24 20:58 ` John Stoffel
2005-10-25 22:18 ` David Greaves
2005-10-24 12:07 Jeff Breidenbach
2005-10-24 13:26 ` Paul Clements
2005-10-24 18:55 ` dean gaudet
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=435E8589.9000303@naa.net \
--to=schmidt@naa.net \
--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).