Kernel is somewhat hacked, but no changes to CIFS. While doing failover testing, we managed to get the cifs client spewing endless serial console spammage. We can ping the system, but otherwise cannot seem to interact with it. I tried serial-console sysrq commands (blind, spewage makes it impossible to see any real results) to turn logging to 0, but that didn't help (yet..going to let it run in case there is just a huge backlog of messages). The file-server cluster is in a bad state, but still not excuse for the clients machine to become useless. The spewage is at least primarily: CIFS VFS: Send error in SessSetup = -88 CIFS VFS: Send error in SessSetup = -88 CIFS VFS: Send error in SessSetup = -88 CIFS VFS: Send error in SessSetup = -88 CIFS VFS: Send error in SessSetup = -88 CIFS VFS: Send error in SessSetup = -88 CIFS VFS: Send error in SessSetup = -88 CIFS VFS: Send error in SessSetup = -88 CIFS VFS: Send error in SessSetup = -88 Seems -88 probably means -ENOTSOCK. At the least, perhaps the cERROR() messages should be rate limitted? This one is hard and slow to reproduce, but we'll keep testing..and will try pertinent patches if someone has some suggestions. Thanks, Ben -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
