Bug 594061 - nfs: sys_read sometimes returns -EIO [rhel-5.5.z]
Summary: nfs: sys_read sometimes returns -EIO [rhel-5.5.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.4
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jiri Pirko
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On: 557423
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-20 13:05 UTC by RHEL Program Management
Modified: 2015-05-05 01:20 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
On NFS, the read(2) system call could have returned an unexpected EIO (input/ouput error) value.
Clone Of:
Environment:
Last Closed: 2010-07-01 18:29:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0504 0 normal SHIPPED_LIVE Important: kernel security and bug fix update 2010-07-01 18:26:58 UTC

Description RHEL Program Management 2010-05-20 13:05:46 UTC 
This bug has been copied from bug #557423 and has been proposed
to be backported to 5.5 z-stream (EUS).
Comment 4 Jiri Pirko 2010-06-02 11:11:25 UTC 
in 2.6.18-194.5.1.el5
Comment 8 Douglas Silas 2010-06-28 20:24:34 UTC 
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.

New Contents:
On NFS, the read(2) system call could have returned an unexpected EIO (input/ouput error) value.
Comment 10 errata-xmlrpc 2010-07-01 18:29:40 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2010-0504.html
Note You need to log in before you can comment on or make changes to this bug.