Can you read this file using another program (vi ...)?
google only showed this site for "PrivIncrFileSpace 164"
http://www.lofland.net/LoflandBLOG/category/unix-notes/
He had a corrupted filesystem causing the error.

HTH
Thomas Rupp

-----Ursprüngliche Nachricht-----
Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Farren 
Minns
Gesendet: Donnerstag, 24. August 2006 11:36
An: ADSM-L@VM.MARIST.EDU
Betreff: [ADSM-L] TSM Client file input/output error error


Hi All

Running TSM Client 5.1.6.0 on Solaris against a 5.2.7.2 server on Solaris
2.9.

We have been backing up this client for a long time now and it has been
fine. However, the sys admin did a patch cluster install at the weekend and
ever since I have been seeing the following errors.

dsmsched.log

23/08/06   22:21:05 ANS4023E Error processing '/usr/local/webservers': file
input/output error
23/08/06   22:21:05 --- SCHEDULEREC OBJECT END COI-DAILY-INC 23/08/06
21:30:00
23/08/06   22:21:05 ANS1512E Scheduled event 'COI-DAILY-INC'
failed.  Return code = 12.

dsmerror.log

23/08/06   22:20:59 PrivIncrFileSpace: Received rc=164 from
fioGetDirEntries:  /usr/local/webservers  /phy/live/htdocs/Phy/External/PhyH


Any idea what I'm seeing here?

Thanks

Farren

######################################################################
The information contained in this e-mail and any subsequent 
correspondence is private and confidential and intended solely 
for the named recipient(s).  If you are not a named recipient, 
you must not copy, distribute, or disseminate the information, 
open any attachment, or take any action in reliance on it.  If you 
have received the e-mail in error, please notify the sender and delete
the e-mail.  

Any views or opinions expressed in this e-mail are those of the 
individual sender, unless otherwise stated.  Although this e-mail has 
been scanned for viruses you should rely on your own virus check, as 
the sender accepts no liability for any damage arising out of any bug 
or virus infection.
######################################################################

Reply via email to