unexplained system hangs - possible smbfs issue ??

Murray Taylor MTaylor at bytecraft.com.au
Sun Oct 9 23:37:33 PDT 2005


The information transmitted in this e-mail is for the exclusive
use of the intended addressee and may contain confidential
and/or privileged material. Any review, re-transmission,
dissemination or other use of it, or the taking of any action
in reliance upon this information by persons and/or entities
other than the intended recipient is prohibited. If you
received this in error, please inform the sender and/or
addressee immediately and delete the material. 

E-mails may not be secure, may contain computer viruses and
may be corrupted in transmission. Please carefully check this
e-mail (and any attachment) accordingly. No warranties are
given and no liability is accepted for any loss or damage
caused by such matters.

***This Email has been scanned for Viruses by MailMarshal.***
-------------- next part --------------

-----Original Message-----
From: owner-freebsd-questions at freebsd.org
[mailto:owner-freebsd-questions at freebsd.org] On Behalf Of Garrett Cooper
Sent: Monday, October 10, 2005 3:35 PM
To: freebsd-questions at freebsd.org
Subject: Re: unexplained system hangs - possible smbfs issue ??

     Have you thought of looking into filing a bug report with the  
Samba people (http://www.samba.org/)? This may be an issue with  
either your client program, or the SMB implementation in Win2k3,  
which can be solved by getting the ball rolling with SMB and/or  
possibly MS.
     Either way, that is quite a few files to have to parse through,  
and although it may seem somewhat ludicrous, adding an additional  
script to presort out your minute reports would greatly reduce the  
amount of open-file records you need, and while that may not be a  
permanent solution it can serve as a better base for sorting your  
data. You could just create proper directories on the Win2k3 server,  
like %BASE_DIR%\Year\Day\Hour, if you get a large volume of files, or  
just strictly put them in a daily directory since it sounds like your  
volume is manageable. Plus, it's probably easier for humans to manage  
as opposed to 2000+ flat files in the same directory ;). Any SQL  
would handle this issue nicely as well since one of databases' best  
selling points is this type of application.


Thanks for your input, as it all ties things up with the observed
which we have been slowly closing in on by a process of isolating
processes onto a 'sacrifical' host. 

BTW it still seems to be a bit time dependant, unless the 
comments regarding the extra files of zero length mentioned in other
replies and PR's apply here. Our test bed _never_ crashed under high
load testing
(20K+ files grown incrementally).  Maybe the test bed always had
files and/or file structures..... (sigh)

(really silly thought - I wonder if it is as 'simple' as needing 
an even / odd file count when the count gets high?? )

A 'move_files to dated directory' process is being built within the main
process as a final 
operation for cleanup. This will mean that the smbfs will never have
more than
10 files or so in any given 1 minute cycle.



More information about the freebsd-questions mailing list