From: Goswin von Brederlow <goswin-v-b@web.de>
To: Jon Lewis <jlewis@lewis.org>
Cc: Robin Hill <robin@robinhill.me.uk>, linux-raid@vger.kernel.org
Subject: Re: Converting system to raid
Date: Sat, 11 Apr 2009 10:50:35 +0200 [thread overview]
Message-ID: <87y6u7o9pg.fsf@frosties.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0904110035420.6312@soloth.lewis.org> (Jon Lewis's message of "Sat, 11 Apr 2009 00:40:37 -0400 (EDT)")
Jon Lewis <jlewis@lewis.org> writes:
> On Fri, 10 Apr 2009, Robin Hill wrote:
>
>> On Fri Apr 10, 2009 at 12:22:44PM -0700, Timothy D. Lenz wrote:
>>
>>> How can cp not work? every guide I found used ether cp or rsync. Even
>>> guides on seting up an auto backup system use cp or rsync.
>>> Seems the only files/folders that shouldn't get copied are the block
>>> device ones that are created at boot and are not really on the drive.
>>>
>> They'll all get copied, but you won't necessarily get the correct
>> contents. Because the system is in use:
>> - files will be being written, so you'll either get a partial copy, or
>> an old version.
>> - files may be locked, so you won't be able to copy them.
>>
>> Doing a backup of a running system using cp/rsync will work fine for a
>> lot of things (especially for config files, documents, etc) but will
>> almost certainly fail miserably for some (databases for example).
What one can easily do is rsync the running system, then init 1 and
rsync again to get all the changed or blocked files. In runlevel 1
there should be nothing left blocking files.
MfG
Goswin
prev parent reply other threads:[~2009-04-11 8:50 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
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 [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=87y6u7o9pg.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=jlewis@lewis.org \
--cc=linux-raid@vger.kernel.org \
--cc=robin@robinhill.me.uk \
/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