[OpenAFS] Problem with mandatory profiles on AFS.
Hi, first environment: AFS servers running 1.4.5, Windows clients 1.5.36. The problem is that when exporting mandatory profiles it usually works fine, but on some profiles it just hangs. Looking at the task manager shows that both CPU and network traffic stops, and after a while an error message pops up (after I assume the SMB timeout). This happens about 700 files and 35MB into a profile of size 5000 files and 125MB. The directory where it fails contains 900 files with quite long names, but it's not the directory max-limit that is the problem. Copying the profile just using Explorer works fine and has no problem. The cache size on the client is set to 800MB (32-bit client). Who can we debug this? Any hints? Have I missed something? :-) -- Ragge ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Problem with mandatory profiles on AFS.
On Tuesday 19 August 2008 11:52:02 Anders Magnusson wrote: Hi, first environment: AFS servers running 1.4.5, Windows clients 1.5.36. The problem is that when exporting mandatory profiles it usually works fine, but on some profiles it just hangs. Looking at the task manager shows that both CPU and network traffic stops, and after a while an error message pops up (after I assume the SMB timeout). This happens about 700 files and 35MB into a profile of size 5000 files and 125MB. The directory where it fails contains 900 files with quite long names, but it's not the directory max-limit that is the problem. Copying the profile just using Explorer works fine and has no problem. The cache size on the client is set to 800MB (32-bit client). Who can we debug this? Any hints? Have I missed something? :-) Hmm, not that I know anything about the windows-client, but maybe you should try the newest windows-client ? It has unicode supported for funny names like Smörebröd in directories and profiles, which could lead to behaviour like that. Just a guess, but give it a try. T/Christof ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Problem with mandatory profiles on AFS.
Christof Hanke wrote: On Tuesday 19 August 2008 11:52:02 Anders Magnusson wrote: Hi, first environment: AFS servers running 1.4.5, Windows clients 1.5.36. The problem is that when exporting mandatory profiles it usually works fine, but on some profiles it just hangs. Looking at the task manager shows that both CPU and network traffic stops, and after a while an error message pops up (after I assume the SMB timeout). This happens about 700 files and 35MB into a profile of size 5000 files and 125MB. The directory where it fails contains 900 files with quite long names, but it's not the directory max-limit that is the problem. Copying the profile just using Explorer works fine and has no problem. The cache size on the client is set to 800MB (32-bit client). Who can we debug this? Any hints? Have I missed something? :-) Hmm, not that I know anything about the windows-client, but maybe you should try the newest windows-client ? It has unicode supported for funny names like Smörebröd in directories and profiles, which could lead to behaviour like that. No, it's not the the character set that is the problem, it's something else. -- Ragge ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Problem with mandatory profiles on AFS.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anders Magnusson wrote: No, it's not the the character set that is the problem, it's something else. I just can tell, my profiles with the latest 1.5.52 release of windows client works moslty fine, but not in all cases. Til yet I cannot reproduce errors to debug them... Sometimes it just failes and hangs forever... -- Ragge MfG, Lars Schimmer - -- - - TU Graz, Institut für ComputerGraphik WissensVisualisierung Tel: +43 316 873-5405 E-Mail: [EMAIL PROTECTED] Fax: +43 316 873-5402 PGP-Key-ID: 0x4A9B1723 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkiqkJoACgkQmWhuE0qbFyNs8wCdG4jZUNv8d5mm+IQMLuSZXxFw sdAAoICWKBv2/6MF2FUvg2WrDtZnv+1Z =mn37 -END PGP SIGNATURE- ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Problem with mandatory profiles on AFS.
Lars Schimmer wrote: I just can tell, my profiles with the latest 1.5.52 release of windows client works mostly fine, but not in all cases. Til yet I cannot reproduce errors to debug them... Sometimes it just failes and hangs forever... If it hangs forever it is possibly a deadlock in which case you should use fs minidump to generate a dump file and send it to [EMAIL PROTECTED] The release notes (which are installed with the OAFW) describe how to debug the client. Jeffrey Altman smime.p7s Description: S/MIME Cryptographic Signature
Re: [OpenAFS] Problem with mandatory profiles on AFS.
Anders Magnusson wrote: Hi, first environment: AFS servers running 1.4.5, Windows clients 1.5.36. The problem is that when exporting mandatory profiles it usually works fine, but on some profiles it just hangs. Looking at the task manager shows that both CPU and network traffic stops, and after a while an error message pops up (after I assume the SMB timeout). This happens about 700 files and 35MB into a profile of size 5000 files and 125MB. The directory where it fails contains 900 files with quite long names, but it's not the directory max-limit that is the problem. Copying the profile just using Explorer works fine and has no problem. The cache size on the client is set to 800MB (32-bit client). Who can we debug this? Any hints? Have I missed something? :-) Debugging techniques are described in the Release Notes. If the client comes to a complete halt it is likely a deadlock. A number of deadlocks have been fixed in the 1.5.51 and 1.5.52 releases that have been present for quite some time. Jeffrey Altman smime.p7s Description: S/MIME Cryptographic Signature
Re: [OpenAFS] Problem with mandatory profiles on AFS.
Jeffrey Altman wrote: Debugging techniques are described in the Release Notes. Yes, I've read them, but I didn't really understand how to parse all information that I could get out from the system :-) If the client comes to a complete halt it is likely a deadlock. A number of deadlocks have been fixed in the 1.5.51 and 1.5.52 releases that have been present for quite some time. No, it do not look like a deadlock, everything else continues and after the timeout (error popup) everything is back to normal. We have tried with 1.5.52 also, but no difference. -- Ragge ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Problem with mandatory profiles on AFS.
Anders Magnusson wrote: Jeffrey Altman wrote: Debugging techniques are described in the Release Notes. Yes, I've read them, but I didn't really understand how to parse all information that I could get out from the system :-) Parsing the output requires an understanding of the source code and of Windows internals. Support is available if you cannot help yourself http://www.secure-endpoints.com/support/openafs.html If the client comes to a complete halt it is likely a deadlock. A number of deadlocks have been fixed in the 1.5.51 and 1.5.52 releases that have been present for quite some time. No, it do not look like a deadlock, everything else continues and after the timeout (error popup) everything is back to normal. We have tried with 1.5.52 also, but no difference. Without access to the information that would be provided by obtaining OpenAFS trace output combined with SysInternals Process Monitor logging it is not possible to provide much in the way of advice. SMB timeouts occur when a request made to the file server fails to respond in 45 seconds. It is crucial that file server bottlenecks be avoided. Running the latest AFS servers, 1.4.7, will help prevent a single client using a large number of worker threads on a single server. Process Monitor output will show you which SMB client requests are failing and how long they are taking. The OpenAFS trace output will show you why they are failing. The Rx Hard Dead, Connection, Idle, and other Timeout values can be adjusted on the client via the registry. The options are described in Appendix A of the release notes. ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
