Sorry for the delayed response On 03/19/2015 12:57 PM, Rupert Dance wrote: > We tried uncommenting the code but we are still seeing failures. We are > running Connectathon on a variety of systems pairs testing both Mellanox and > Intel Hardware. Most of the combinations pass the Connectathon Basic, > Locking and Special tests but fail the General tests with the error message > "Nroff ./stat: no data in nroff.time" What does output from the time command look like? > > There are several other combinations that cause other errors: > > 1. The test hangs and no error is reported. In these cases the client > system MUST be restarted before it becomes usable again. The server system > is restarted to get back to a known good state and clear the exports before > restarting testing > > 2. Connectathon Basic test hangs with the client system displaying: ./test5: > read and write Is it really hung or is it just slow? On the client, use tshark host <server> to see if there is anything going over the wire... steved. -- 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
