Hallo Jeff! > At this point, I'd suggest just setting the cifs_max_pending module > parm low (1 or 2) and seeing if that helps. If it does, then that > should basically emulate the effect of steve's eventual patch. If it > doesn't then we'll probably need to have a closer look at why it isn't. I have set cifs_max_pending to 2 (setting it 1 results in value 2). Giving interesting results: Normal mount/cp of single file works (same mount parameter as before). Copying several files with midnight commander showed me a copy speed of 4.5 to 5.6 MByte per second - start at 4.5 and raising quickly to 5.6). This speed is higher then ever received on copying to the same NAS station from same hardware installation. Formerly (kernel 2.6.18 SMBFS) copies startet below 3.5 MBps and raised slowly up to about 4 MBps (or slightly above - only at very big files). So reducing the setting of cifs_max_pendig not only let the drive work it additionally gave me a big step in speed optimization. ... but: Switching virtual console during copy process let the copy stop with a stuck mc as before. The only difference: After killing the process and a delay of about 2 minutes (felt, not measured) the process disappeared and NAS drive returned to a working state without system reboot. If you like/need I may catch more data for diagnosis tomorrow. Just let me know what you need and how I shall test. I'm willing to give you all data for diagnosis I'm able to collect. -- 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
