>>>>> " " == Mike Black <firstname.lastname@example.org> writes:
> I've been getting random NFS EIO errors for a few months but
> now it's repeatable. Trying to copy a large file from one
> 2.4.8 SMP box to another is consistently failing (at different
> offsets each time). This doesn't appear to be a network
> problem as the last comm between the machines looks OK. By the
> timestamps it appears that a read() is taking too long and
> causing a timeout?
Morale: Don't use soft mounts: they are prone to these things. If you
insist on using them, then try playing around with the `timeo' and
`retrans' mount variables.
Soft mount timeouts are not only due to network problems, but can
equally well be due to internal congestion. The rate at which the
network can transmit requests is usually (unless you are using
Gigabit) way below the rate at which your machine can generate them.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/