From: fs <fs@ercist.iscas.ac.cn>
To: "Hua Zhong (hzhong)" <hzhong@cisco.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Kenichi Okuyama <okuyama@intellilink.co.jp>
Subject: RE: [RFD] What error should FS return when I/O failure occurs?
Date: Tue, 17 May 2005 12:55:44 -0400 [thread overview]
Message-ID: <1116348944.2428.42.camel@CoolQ> (raw)
In-Reply-To: <75D9B5F4E50C8B4BB27622BD06C2B82B2264F6@xmb-sjc-235.amer.cisco.com>
On Tue, 2005-05-17 at 01:36, Hua Zhong (hzhong) wrote:
> > What you said is based on the FS implementor's perspective.
> > But from user's perspective, they open a file with O_RDWR, get a
> > success, then write returns EROFS?
> > Besides, EXT3 ALWAYS return EROFS for the 1st and 2nd case, even
> > you specify errors=continue, things are still the same.
>
> Which version of kernel you are using?
My test environment is based on 2.6.11 kernel
> It was probably the case in kernel before 2.4.20. The old ext3 had a
> problem that it ignored IO error at journal commit time. I submitted a
> patch to fix that around the time of 2.4.20. 2.6 should be fine too,
> unless someone else broke it again.
>
> Hua
next prev parent reply other threads:[~2005-05-17 5:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 5:36 [RFD] What error should FS return when I/O failure occurs? Hua Zhong (hzhong)
2005-05-17 16:55 ` fs [this message]
[not found] <05May16.114248edt.32448@gpu.utcc.utoronto.ca>
2005-05-17 15:43 ` fs
2005-05-17 18:26 ` Bryan Henderson
2005-05-18 17:10 ` fs
2005-05-18 7:57 ` Valdis.Kletnieks
2005-05-18 19:06 ` Bryan Henderson
-- strict thread matches above, loose matches on Subject: below --
2005-05-17 6:00 Hua Zhong (hzhong)
2005-05-17 17:20 ` fs
2005-05-16 17:14 fs
2005-05-16 6:35 ` Valdis.Kletnieks
2005-05-16 18:04 ` fs
2005-05-16 17:58 ` Valdis.Kletnieks
2005-05-17 16:47 ` fs
[not found] ` <200505171057.10540.vda@ilport.com.ua>
2005-05-17 19:41 ` fs
2005-05-16 20:11 ` Kenichi Okuyama
2005-05-16 20:35 ` Valdis.Kletnieks
2005-05-16 21:39 ` Kenichi Okuyama
2005-05-16 22:04 ` Brad Boyer
2005-05-16 22:30 ` Elladan
2005-05-17 6:17 ` Denis Vlasenko
2005-05-17 18:10 ` Bryan Henderson
2005-05-18 6:54 ` Denis Vlasenko
2005-05-17 21:26 ` Kenichi Okuyama
2005-05-19 15:44 ` Elladan
2005-05-16 22:57 ` Coywolf Qi Hunt
2005-05-16 22:54 ` Coywolf Qi Hunt
2005-05-17 16:06 ` fs
2005-05-16 17:36 ` Hans Reiser
2005-05-16 18:04 ` Bryan Henderson
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=1116348944.2428.42.camel@CoolQ \
--to=fs@ercist.iscas.ac.cn \
--cc=hzhong@cisco.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okuyama@intellilink.co.jp \
/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;
as well as URLs for NNTP newsgroup(s).