John,
Just my opinion here. FSCHECK does not take that long to run(couple minutes), even on a very large system. The problem running it in batch is, what to do if FSCHECK finds a problem?
I don't think it would be possible to automate a fix in batch.
CHECKDIRC ;FIX if it finds a problem will want a response of what to do. I think it would be very dangerous to imply a 'YES' response.
Personally, I like to run FSCHECK after every system failure.
Good Luck,
-Craig
--- On Tue, 9/15/09, John Bawden <[log in to unmask]> wrote:
> From: John Bawden <[log in to unmask]>
> Subject: Running FSCHECK in a job
> To: [log in to unmask]
> Date: Tuesday, September 15, 2009, 6:53 PM
> We are having some very strange
> problems with files just randomly disappearing with
> absolutely no reason that we can determine. It has been
> recommended that we run FSCHECK with the CHECKALL option to
> see what it shows for a possible explanation or to rule out
> some areas. The file structure is very large and we would
> like to run FSCHECK in a job since all users have to be off
> and this would have to run on a weekend night. But we have
> heard that there can be problems doing this, up to a
> system crash, but no further explanation. I've run FSCHECK
> with the SYNCACCOUNTING option in job mode for several years
> on another system with no problems at all. Does anyone know
> what problems there might be that are related to the
> CHECKALL or has anyone experienced problems.
>
> TIA for nay advice pro and con.
> John Bawden
> Homestead3000 Consulting
> MPE Forever
>
> * To join/leave the list, search archives, change list
> settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
