On Wed, Dec 04, 2013 at 10:44:45PM +0200, Antti Tönkyrä wrote: > Looks like I can strace it and I did an example strace, if you need > something more specific please do tell. Command log has completion > timestamps for associating what part of strace happened at what > command. > > http://daedalus.pingtimeout.net/dbg/strace-ioerr.txt > http://daedalus.pingtimeout.net/dbg/strace-commandlog.txt Eh, not much use without knowing fuse's protocol, but: > And just in case you missed my other mail, the I/O error doesn't > kill the share if using NFSv3 (mount -t nfs -o vers=3,intr,hard > ...). The initial I/O error happens but the share doesn't die even > when there are file handles open there. Oh, I overlooked that. So that merits another look at the network trace: > >>http://daedalus.pingtimeout.net/dbg/eilseq_ioerr.pcap And I see something I'd overlooked before: the client is sending the later opens with the same open owner and sequence id. But NFS4ERR_IO is a seqid-mutating error. So now I think this probably *is* a client bug.... What's the client kernel version? --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
