From: jim owens <jowens@hp.com>
To: linux-raid@vger.kernel.org
Subject: Re: Converting system to raid
Date: Sat, 11 Apr 2009 11:04:40 -0400 [thread overview]
Message-ID: <49E0B188.8050009@hp.com> (raw)
In-Reply-To: <20090411143642.GA9915@cthulhu.home.robinhill.me.uk>
Robin Hill wrote:
>> From: "CoolCold" <coolthecold@gmail.com>
>>
>> # rsync -avHhx --progress --delete / /mnt/raid-md0
>>
> Yes, this is an alternative to running from a bootable CD. In
> single-user mode (init 1), there can be no background applications
> running, so there should be no open files to worry about. I'd still
> rather use a bootable CD though.
Strong ACK on bootable CD as the right method, or doing it all
while init 1... not as a 2-step multi-user mode, single user.
rsync is a very good tool but unless you use:
-c, --checksum skip based on checksum, not mod-time & size
the consistency between runs is not 100% safe. It may be 99.9%,
but the problem is that for file blocks being rewritten you don't
know what is on disk or in memory and mod-time only changes at the
whim of the FS (I'm an FS developer) and at the granularity of
the FS and system clock... nanosecond time stamps are a myth!
And if you are going to use the rsync -c 2-pass method it will
probably take your system off line longer than a CD boot and copy.
At the end of process, is 99.9% good enough? For much of my
backup needs it is because I only care about not loosing more
than a small amount of work. But if I'm converting to a new
disk and loosing the old one, I want 100%.
jim
next prev parent reply other threads:[~2009-04-11 15:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 23:44 Converting system to raid Timothy D. Lenz
2009-04-10 9:10 ` KwangErn Liew
2009-04-10 9:55 ` CoolCold
2009-04-10 19:43 ` Timothy D. Lenz
2009-04-10 19:53 ` Robin Hill
2009-04-10 20:45 ` Timothy D. Lenz
2009-04-10 20:59 ` Robin Hill
2009-04-10 21:26 ` Timothy D. Lenz
2009-04-10 21:51 ` Robin Hill
2009-04-11 5:29 ` Timothy D. Lenz
2009-04-11 14:29 ` CoolCold
2009-04-11 18:47 ` Timothy D. Lenz
2009-04-12 0:53 ` Timothy D. Lenz
2009-04-12 11:11 ` Robin Hill
2009-04-12 19:55 ` Timothy D. Lenz
2009-04-14 9:30 ` Robin Hill
2009-04-17 0:47 ` Timothy D. Lenz
2009-04-17 7:49 ` Robin Hill
2009-04-11 14:36 ` Robin Hill
2009-04-11 15:04 ` jim owens [this message]
2009-04-11 15:44 ` Jeff Garzik
2009-04-11 17:40 ` jim owens
2009-04-12 11:11 ` Jeff Garzik
2009-04-12 16:43 ` jim owens
2009-04-12 17:18 ` Jeff Garzik
2009-04-10 13:22 ` Robin Hill
2009-04-10 19:22 ` Timothy D. Lenz
2009-04-10 19:50 ` Robin Hill
2009-04-11 4:40 ` Jon Lewis
2009-04-11 7:48 ` Jan Ceuleers
2009-04-11 8:50 ` Goswin von Brederlow
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=49E0B188.8050009@hp.com \
--to=jowens@hp.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 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.