From: V P <upathiyayan@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: I/O error propagation
Date: Thu, 3 Mar 2005 13:28:41 -0600 [thread overview]
Message-ID: <c9ad856005030311286314ebfd@mail.gmail.com> (raw)
Hi,
I have a question on how disk errors get propagated to
the file systems.
>From looking at the SCSI/IDE drivers, it looks like there
could be many reasons for an I/O to fail. It could be
bus timeout, media errors, and so on.
Does all these errors get reported to the file system ?
It looks like all the different types of errors get
turned into a single I/O error (-EIO) and passed on to the
file system.
Or is there a way where we can export better error codes
to the file system ?
Any idea/input regarding this is greatly appreciated.
Thanks.
next reply other threads:[~2005-03-03 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 19:28 V P [this message]
2005-03-03 20:20 ` I/O error propagation linux-os
2005-03-03 22:29 ` V P
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=c9ad856005030311286314ebfd@mail.gmail.com \
--to=upathiyayan@gmail.com \
--cc=linux-kernel@vger.kernel.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 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.