> The file is being copied from yeti to picard. Last packet seen
> is picard telling yeti "OK" after the commit. If soft timeouts
> were occurring shouldn't we be seeing packets from yeti again
> with no response from picard?
You are assuming that the last packet seen is the one that corresponds
to your read. In doing so, you are neglecting the fact that these are
asynchronous reads, and that file readahead can muddle the waters for
you.
Look, this is getting us nowhere. The bottom line is: if you are able
to reproduce the EIO on hard mounts it is a bug, and I'll be happy to
help you trace it. If it is occuring only on soft mounts, it is user
error...
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/