Kernel 2.2.7, fsync() and EIO

• Next message: Andris Pavenis: "Re: [PATCH] fork.c bug (fixes "waitpid() fails when running under debugger")"
• Previous message: BenHanokh Gabriel: "accessing files from kernel space ???"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi all.

A customer is frequently encountering a fsync() returning EIO,
usually if the system has some noticeable I/O load.
This does not look like a disk error since there is no message
in the syslog and reading the disk (eg. tar) works w/o a problem.

The system is SCSI based (probably Adaptec controller).
Acessed files in are on an ext2 filesystem and rather large
(each > 1 GB).

Are there other reasons for fsync() to return an EIO besides
a real I/O error? Anyone remember something like this in the
2.2.7 kernel? Does it make sense to update the kernel to a more
recent one just in case?

I appreciate any help/pointer/comment.

Thanks
Michael

-- 
Michael Marxmeier           Marxmeier Software AG
E-Mail: mike@msede.com      Besenbruchstrasse 9
Phone : +49 202 2431440     42285 Wuppertal, Germany
Fax   : +49 202 2431420     http://www.msede.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Andris Pavenis: "Re: [PATCH] fork.c bug (fixes "waitpid() fails when running under debugger")"
• Previous message: BenHanokh Gabriel: "accessing files from kernel space ???"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue May 23 2000 - 21:00:12 EST