From: Matt Mackall <mpm@selenic.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: ptb@it.uc3m.es, Justin Cormack <justin@street-vision.com>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ENBD for 2.5.64
Date: Tue, 25 Mar 2003 23:55:25 -0600 [thread overview]
Message-ID: <20030326055525.GA20244@waste.org> (raw)
In-Reply-To: <3E81132C.9020506@pobox.com>
On Tue, Mar 25, 2003 at 09:40:44PM -0500, Jeff Garzik wrote:
> Peter T. Breuer wrote:
> >"Justin Cormack wrote:"
> >>And I am intending to write an iscsi client sometime, but it got
> >>delayed. The server stuff is already available from 3com.
> >
> >
> >Possibly, but ENBD is designed to fail :-). And networks fail.
> >What will your iscsi implementation do when somebody resets the
> >router? All those issues are handled by ENBD. ENBD breaks off and
> >reconnects automatically. It reacts right to removable media.
>
> Yeah, iSCSI handles all that and more. It's a behemoth of a
> specification. (whether a particular implementation implements all that
> stuff correctly is another matter...)
Indeed, there are iSCSI implementations that do multipath and
failover.
Both iSCSI and ENBD currently have issues with pending writes during
network outages. The current I/O layer fails to report failed writes
to fsync and friends.
> BTW, I'm a big enbd fan :) I like enbd for it's _simplicity_ compared
> to iSCSI.
Definitely. The iSCSI protocol is more powerful but _much_ more
complex than ENBD. I've spent two years working on iSCSI but guess
which I use at home..
--
Matt Mackall : http://www.selenic.com : of or relating to the moon
next prev parent reply other threads:[~2003-03-26 5:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1048623613.25914.14.camel@lotte>
2003-03-25 20:53 ` [PATCH] ENBD for 2.5.64 Peter T. Breuer
2003-03-26 2:40 ` Jeff Garzik
2003-03-26 5:55 ` Matt Mackall [this message]
2003-03-26 6:31 ` Peter T. Breuer
2003-03-26 6:48 ` Matt Mackall
2003-03-26 7:05 ` Peter T. Breuer
2003-03-26 6:59 ` Andre Hedrick
2003-03-26 13:58 ` Jeff Garzik
2003-03-26 7:31 ` Lincoln Dale
2003-03-26 9:59 ` Lars Marowsky-Bree
2003-03-26 10:18 ` Andrew Morton
2003-03-26 13:49 ` Jeff Garzik
2003-03-26 16:09 ` Matt Mackall
[not found] ` <5.1.0.14.2.20030327085031.04aa7128@mira-sjcm-3.cisco.com>
2003-03-26 22:40 ` Matt Mackall
2003-03-28 11:19 ` Pavel Machek
2003-03-30 20:48 ` Peter T. Breuer
2003-03-26 22:16 Lincoln Dale
2003-03-26 22:56 ` Lars Marowsky-Bree
2003-03-26 23:21 ` Lincoln Dale
-- strict thread matches above, loose matches on Subject: below --
2003-03-26 22:16 Lincoln Dale
2003-03-26 22:32 ` Andre Hedrick
[not found] ` <Pine.LNX.4.10.10303261422580.25072-100000@master.linux-ide .org>
2003-03-26 23:03 ` Lincoln Dale
2003-03-26 23:39 ` Andre Hedrick
[not found] <5.1.0.14.2.20030327083757.037c0760@mira-sjcm-3.cisco.com>
2003-03-26 22:02 ` Peter T. Breuer
2003-03-26 23:49 ` Lincoln Dale
2003-03-27 0:08 ` Peter T. Breuer
2003-03-25 17:27 Peter T. Breuer
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=20030326055525.GA20244@waste.org \
--to=mpm@selenic.com \
--cc=jgarzik@pobox.com \
--cc=justin@street-vision.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ptb@it.uc3m.es \
/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.