From: Lars Marowsky-Bree <lmb@suse.de>
To: Bernd Eckenfels <ecki@calista.eckenfels.6bone.ka-ip.net>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] nbd driver for 2.5.72
Date: Mon, 23 Jun 2003 11:05:00 +0200 [thread overview]
Message-ID: <20030623090500.GG26081@marowsky-bree.de> (raw)
In-Reply-To: <E19Tbyp-0004mi-00@calista.inka.de>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
On 2003-06-21T08:36:07,
Bernd Eckenfels <ecki@calista.eckenfels.6bone.ka-ip.net> said:
> Is anybody aware of a journalling nbd, which keeps track of unsynced
> changes, so a fast reintegration is possible?
drbd does that, port to 2.5 is in progress.
> Well perhaps this is a property of the md device, instead... hmm. Is there
> such a function available? Could be some left over from snapshot code.
Peter T. Breuer has also been working on intent logging for md, which
will also achieve largely the same thing, just with slightly different
properties. I'm not fully aware on the current status of this
implementation.
Sincerely,
Lars Marowsky-Brée <lmb@suse.de>
--
SuSE Labs - Research & Development, SuSE Linux AG
"If anything can go wrong, it will." "Chance favors the prepared (mind)."
-- Capt. Edward A. Murphy -- Louis Pasteur
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-23 9:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-21 5:43 [RFC][PATCH] nbd driver for 2.5.72 Lou Langholtz
2003-06-21 6:23 ` Pavel Machek
2003-06-21 6:36 ` Bernd Eckenfels
2003-06-21 7:42 ` Wichert Akkerman
2003-06-23 9:05 ` Lars Marowsky-Bree [this message]
2003-06-23 19:21 ` Paul Clements
2003-06-21 6:44 ` Andrew Morton
2003-06-21 15:59 ` Lou Langholtz
2003-06-21 7:04 ` Pavel Machek
2003-06-21 7:32 ` viro
2003-06-21 7:45 ` Sam Ravnborg
2003-06-21 16:39 ` Lou Langholtz
2003-06-21 19:31 ` viro
2003-06-21 20:23 ` Lou Langholtz
2003-06-22 10:30 ` Jens Axboe
2003-06-22 14:15 ` Lou Langholtz
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=20030623090500.GG26081@marowsky-bree.de \
--to=lmb@suse.de \
--cc=ecki@calista.eckenfels.6bone.ka-ip.net \
--cc=linux-kernel@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