Messages in this thread | | | From | Bernd Eckenfels <> | Subject | Re: [RFC][PATCH] nbd driver for 2.5.72 | Date | Sat, 21 Jun 2003 08:36:07 +0200 |
| |
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/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |