I/O error (5)

[Abhijith Madhav]

Hi all,

During compilation of a .c file I get a

"Error 5: "a.c", line 8 # Unable to open file /home/abhijith/b.h; I/O error (5)."

even though I have the appropriate include path in the compilation line. What does the "I/O error (5)" telling me?? How can I resolve the issue??

Thanks,
Abhijith

[Steven Schweda]

The errno value EIO (symbolic) is 5
(numeric), and "I/O error" (text).

Apparently, the compiler can't read that
header file. What happens if you:

cat /home/abhijith/b.h

The cause could be bad hardware (disk) or
file system corruption, or any number of
other things.

[Abhijith Madhav]

.I can open and read the file without any problem.

. Below is the permissions for the file.
-r--r--r-- 1 vobadm lang 21596 Feb 10 2003 /home/abhijith/b.h

. Might it help if I mention that the header file is versioned under clearcase.

[Abhijith Madhav]

.I can open and read the file without any problem.

. Below is the permissions for the file.
-r--r--r-- 1 vobadm lang 21596 Feb 10 2003 /home/abhijith/b.h

. Might it help if I mention that the header file is versioned under clearcase.

[Steven Schweda]

Normally, I'd expect the compiler to be able
to deal with the file as well as anyone else
could.

> Might it help if I mention that the header
> file is versioned under clearcase.

I haven't used ClearCase for a while, and
that wouldn't tell me why _you_ can read a
file but the compiler couldn't, but you might
be seeing some kind of ClearCase (or NFS)
problem, too.

There might be something useful in an error
log on the ClearCase server. No bets.

[Abhijith Madhav]

This compilation was a part of the build. I'd refired the build to check if it wasn't a spurious nfs isssue as you pointed out. The compilation has gone mighty fine this time.

[Abhijith Madhav]

Haven't found the exact cause. A likely spurious nfs issue