From: "Stephen D. Williams" <sdw@lig.net>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
user-mode-linux-user@lists.sourceforge.net
Subject: [uml-devel] Re: [uml-user] Dynamic remount with variable COW stacking/merging needed, support for snapshot repilication
Date: Sun, 18 Jan 2004 02:07:56 -0500 [thread overview]
Message-ID: <400A30CC.20308@lig.net> (raw)
In-Reply-To: <20040118044551.GB8571@ccure.user-mode-linux.org>
[-- Attachment #1: Type: text/plain, Size: 2003 bytes --]
Yes, but that doesn't meet the key requirement I am proposing: that the
downtime be limited to a few seconds. The only potential significant
downtime with what I am proposing is merging COWs if there was a lot of
disk I/O during the 'snapshot mode'. The existing ability is certainly
useful, but not sufficient to get backups with the least impact to a
running system. Snapshot mode is suspend and flush/sync with the
additional semantics of an automatic temporary push/pop of a COW layer
on all filesystem images. The remaining issue of merging COW's could be
handled by RAID-recovery like gradual merging.
The problem is that if you have gigabytes of filesystem images, it takes
time to copy them, even if using something like rsync to determine what
has changed. It also costs, unless there is a program that determines
which blocks are actually utilized without reads, to scan zero holes in
sparse files.
I should have also mentioned that it should be possible to get a
reliable feed of what blocks, or ranges more likely have changed since a
certain event. This would allow very efficient, near-realtime
replication. At the very least this could be used in suspend or
'snapshot mode' for efficiency, but with proper push of blocks, buffer
visibility, or some kind of write-through notification, synchronization
could be realtime.
sdw
Jeff Dike wrote:
>On Sat, Jan 17, 2004 at 04:13:39PM -0500, Stephen D. Williams wrote:
>
>
>>When a UML instance is running a always-on service, such as a web
>>server, an administrator needs to be able to make live backups, or
>>replications, of a running system.
>>
>>Can this be done now? What needs to be added to support it?
>>
>>
>
>Have you seen the stop, sysrq s, cp, go trick described at
>http://user-mode-linux.sourceforge.net/mconsole.html ?
>
> Jeff
>
>
--
swilliams@hpti.com http://www.hpti.com Personal: sdw@lig.net http://sdw.st
Stephen D. Williams 703-724-0118W 703-995-0407Fax 20147-4622 AIM: sdw
[-- Attachment #2: sdw.vcf --]
[-- Type: text/x-vcard, Size: 234 bytes --]
begin:vcard
fn:Stephen Williams
n:Williams;Stephen
email;internet:sdw@lig.net
tel;work:703-724-0118
tel;fax:703-995-0407
tel;pager:sdwpage@lig.net
tel;home:703-729-5405
tel;cell:703-371-9362
x-mozilla-html:TRUE
version:2.1
end:vcard
next prev parent reply other threads:[~2004-01-18 7:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 21:13 [uml-devel] Dynamic remount with variable COW stacking/merging needed, support for snapshot repilication Stephen D. Williams
2004-01-18 4:45 ` [uml-devel] Re: [uml-user] " Jeff Dike
2004-01-18 7:07 ` Stephen D. Williams [this message]
2004-01-18 16:23 ` s-uml
2004-01-18 11:04 ` [uml-devel] " BlaisorBlade
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=400A30CC.20308@lig.net \
--to=sdw@lig.net \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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.