On 05/16/2013 10:49 PM, Eric Sandeen wrote: > On 5/16/13 3:43 PM, Toralf Förster wrote: >> On 05/16/2013 10:36 PM, Eric Sandeen wrote: >>> any chance you've got anything crazy going on like mounting the same loop >>> file on 2 machines via an nfs export, or anything else out of the ordinary? >>> >> I mount that directory only from 1 UML guest and only once. >> The I run a lot of trinity test in the UML guest suing that share. > > which apparently manages to break things - as intended. ;) yes - I'm calling for trouble and I get it - but by this (uncommon) scenario few real NFSv4 and UML bugs were found. > Can you narrow down which syscalls cause the problem? Till now not to a single one (would be nice, I know). Currently I observed that issue not with host kernel 3.9, but with host kernel 3.10-rc1. Furthermore on the UML guest trinity has to be run long enough (hours) to produce warnings like : # zgrep "v4 server returned" /var/log/messages* | cut -f3- -d' ' kernel: NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence 0c6a41f0! kernel: NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence 3fe4fa60! kernel: NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence 4143f790! kernel: NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence 48f401f0! ... > Is this the very first umount call . . . ? yes, before that probably the NFS service was either restarted or just halted. -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
