Greetings,
    We have a Suse 10 Linux client running TSM client 5.4.2.0.  It is
also running Samba on one of it's filesystems.  When the nightly
incremental runs, it backs up the other filesystems, and then hangs on
the /samba filesystem.  It always hangs somewhere around 20,000 files.
We also get a lot of:
 
ANS4008E Error processing 'filespace namepath-namefile-name': file is
temporarily unavailable
 
messages in dsmerror.log, but I don't know if that really has anything
to do with it.  It is a fileserver, after all, and there are bound to be
a bunch of files in use, even in the middle of the night.  It is a
hospital environment, and people work all shifts.
 
We have tried "memoryefficientbackup yes", and also changing the policy
to static, shrstatic, shrdynamic, but nothing has helped.
 
I thought at first that the problem was a corrupt file in the
filesystem, but now I don't think so.  I ran the following little script
 
cd /samba/users
for dir in `ls -1`; do dsmc  inc /samba/users/${dir}/ -subdir=yes; done
 
so that each separate user's account was backed up separately, and that
worked.  So the files themselves can be backed up, if TSM gets a chance
to read them.
 
Is it possible that TSM is being stopped by the Samba processes?  If so,
is there any way to tune Samba to not do this?

Best Regards,

John D. Schneider 
Lead Systems Administrator - Storage 
Sisters of Mercy Health Systems 
Email:  John.Schneider AT Mercy DOT net

 
This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR
OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the
use of the addressee(s) named above. If you are not the addressee, or the
person responsible for delivering this to the addressee(s), you are notified
that reading, copying or distributing this e-mail is prohibited. If you have
received this e-mail in error, please contact the sender immediately.