From: Bernd Eckenfels <ecki@calista.eckenfels.6bone.ka-ip.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] nbd driver for 2.5.72
Date: Sat, 21 Jun 2003 08:36:07 +0200 [thread overview]
Message-ID: <E19Tbyp-0004mi-00@calista.inka.de> (raw)
In-Reply-To: <3EF3F08B.5060305@aros.net>
In article <3EF3F08B.5060305@aros.net> you wrote:
> There's
> definately room for more improvements
...
> + * 03-06-12 Added a default BLOCKING stratedgy on network downtime with a
> + * non-default NBD_NONBLOCKING flag. This has the net effect of blocking
> + * I/O when there's only transient problems like a server reboot. If used
> + * in conjunction now with RAID mirroring, transient errors (while they'll
> + * pause the system) will not nessesitate a complete recopying of the
> + * server's exported block device which could potentially take much longer
> + * than a reboot.
Is anybody aware of a journalling nbd, which keeps track of unsynced
changes, so a fast reintegration is possible?
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.
Greetings
Bernd
--
eckes privat - http://www.eckes.org/
Project Freefire - http://www.freefire.org/
next prev parent reply other threads:[~2003-06-21 6:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-21 5:43 Lou Langholtz
2003-06-21 6:23 ` Pavel Machek
2003-06-21 6:36 ` Bernd Eckenfels [this message]
2003-06-21 7:42 ` Wichert Akkerman
2003-06-23 9:05 ` Lars Marowsky-Bree
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=E19Tbyp-0004mi-00@calista.inka.de \
--to=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
all inboxes | Powered by JetHome®