From: Andreas Dilger <adilger@clusterfs.com>
To: "Jure Pečar" <pegasus@nerv.eu.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ixt3
Date: Tue, 17 Oct 2006 03:22:48 -0600 [thread overview]
Message-ID: <20061017092248.GY6221@schatzie.adilger.int> (raw)
In-Reply-To: <20061017110637.187ae3c0.pegasus@nerv.eu.org>
On Oct 17, 2006 11:06 +0200, Jure Pečar wrote:
> On Tue, 17 Oct 2006 02:51:30 -0600
> Andreas Dilger <adilger@clusterfs.com> wrote:
> > None of the retry code has been looked at.
>
> This is what I'm mostly interested in ... predictable, well behaving
> and tested error handling & recovery. Is ext4 going to be any better
> here than ext3?
Not unless someone massages the ixt3 code into a form usable in the
kernel. I'd suggest you contact the authors if you are interested in
doing this work.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
prev parent reply other threads:[~2006-10-17 9:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 8:36 ixt3 Jure Pečar
2006-10-17 8:51 ` ixt3 Andreas Dilger
2006-10-17 9:06 ` ixt3 Jure Pečar
2006-10-17 9:22 ` Andreas Dilger [this message]
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=20061017092248.GY6221@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=pegasus@nerv.eu.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