Hi Jerry,

The key message here is the first line you listed. The next thing is to find
out what the return code 164 means. The return code is either from ADSM or
something else (i.e. operating system, TCP/IP, etc.). In the UNIX world, if it
comes from "something else", you'll see "errno=<return code>". When it comes
from ADSM, you'll see "rc=<return code>". In this case, it's the latter.

You can look up ADSM return codes in the "Using the Application Programming
Interface" manual. If you have the ADSM API installed, you can also look in the
dsmrc.h file. Return code 164 indicates a file I/O error, which means that
there is a problem with one or more files in the /home/as_ps directory.

At this point you need to pin-point the problem file(s). You can check
dsmerror.log to see if there is an error message for the file at the same time
(22:03:52). If there is nothing in dsmerror.log, then you'll need to use
whatever disk maintenance tools you have at your disposal to isolate the
problem. If nothing else leads to the problem, then you can try using ADSM.
Although ADSM is not a diagnostic tool per se, you can try running a manual
backup of the files in that directory until ADSM stumbles across the bad file
again. Make sure you use the "verbose" option.

Good luck!

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com



ADSM-L AT VM.MARIST DOT EDU on 07/20/98 05:21:05 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: What's wrong with this picture?


Hello Andrew,

I found these lines in my dsmerror.log file:

07/17/1998 22:03:52 PrivIncrFileSpace: Received rc=164 from
fioGetDirEntries:  /home  /as_ps
07/17/1998 22:03:52 ANS4023E Error processing '/home': file input/output
error
07/17/1998 23:08:57 ANS1512E Scheduled event 'GCAC13_BUP' failed.
Return code = 4.

Do you know what action should be taken now?

Jerry Caupain