From: fs <fs@ercist.iscas.ac.cn>
To: Chris Siebenmann <cks@utcc.utoronto.ca>
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 11:43:00 -0400 [thread overview]
Message-ID: <1116344580.2428.7.camel@CoolQ> (raw)
In-Reply-To: <05May16.114248edt.32448@gpu.utcc.utoronto.ca>
On Mon, 2005-05-16 at 11:42, Chris Siebenmann wrote:
> You write:
> | When I/O failure occurs, there should be some standards which
> | define the ONLY error that should be returned from VFS, right?
>
> In practice there is no standard and there never will be any standard.
> In general the only thing code can do on any write error is to abort
> the operation, regardless of what errno is. (The exceptions are for
> things like nonblocking IO, where 'EAGAIN' and 'EWOULDBLOCK' are not
> real errors.)
Yes, we're sure to abort the operation, but we can't use
exit(EXIT_FAILURE) directly. For HA environment, we should
identify the cause of the error, take correspondent action,
right? So we need to get the right error.
> ---
> "I shall clasp my hands together and bow to the corners of the world."
> Number Ten Ox, "Bridge of Birds"
> cks@utcc.toronto.edu utgpu!cks
regards,
----
Qu Fuping
next parent reply other threads:[~2005-05-17 4:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <05May16.114248edt.32448@gpu.utcc.utoronto.ca>
2005-05-17 15:43 ` fs [this message]
2005-05-17 18:26 ` [RFD] What error should FS return when I/O failure occurs? Bryan Henderson
2005-05-18 17:10 ` fs
2005-05-18 7:57 ` Valdis.Kletnieks
2005-05-18 19:06 ` Bryan Henderson
2005-05-17 6:00 Hua Zhong (hzhong)
2005-05-17 17:20 ` fs
-- strict thread matches above, loose matches on Subject: below --
2005-05-17 5:36 Hua Zhong (hzhong)
2005-05-17 16:55 ` 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=1116344580.2428.7.camel@CoolQ \
--to=fs@ercist.iscas.ac.cn \
--cc=cks@utcc.utoronto.ca \
--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 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.