Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: [RFD] What error should FS return when I/O failure occurs?
Date: Mon, 16 May 2005 22:36:54 -0700
Message-ID: <75D9B5F4E50C8B4BB27622BD06C2B82B2264F6@xmb-sjc-235.amer.cisco.com>
Thread-Topic: [RFD] What error should FS return when I/O failure occurs?
Thread-Index: AcVanZSiAjaRyLPYTseJfnO1/U5eHQABCvZA
From: "Hua Zhong \(hzhong\)" <hzhong@cisco.com>
To: "fs" <fs@ercist.iscas.ac.cn>, <coywolf@lovecn.org>
Cc: "linux-fsdevel" <linux-fsdevel@vger.kernel.org>,
       "linux-kernel" <linux-kernel@vger.kernel.org>,
       "Kenichi Okuyama" <okuyama@intellilink.co.jp>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 826
Lines: 19

> 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?

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
-
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/