Hallo Jeff! > Is this the same NAS that requests a maxmpx of 1? If so, the fact that > cifs sends more than one request a time to this server might be the > ultimate cause. > > Obviously the server should handle that situation without corrupting > its replies, but cifs is clearly broken in this regard and shouldn't be > sending more than one request at a time to such a server. I doubt > there's anything you can do until Steve fixes that bug. That cifs_max_pending=2 module parameter helps a lot on my side. It not only avoids many cases the cifs process gets stuck it even leads to the interesting behavior that such processes vanish (accept the kill) after a couple of minutes. In those cases the device even return to a working state without an reboot. After that you may unmount normal or continue to access the NAS device. Awesome those stuck periods but better than having to reboot. Especially as those collisions happen much less than without the module parameter. -- Harald -- 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
