disk analyse error

[kaira_falla]

when I run Analyse/disk/repair, i get the following error.

FIRST I GET THIS ERROR

%ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
-SYSTEM-W-NOSUCHFILE, no such file


LATER I GET THIS ERROR

%ANALDISK-W-DELETE, file (6361,66,0)
error deleting file
-SYSTEM-W-ACCONFLICT, file access conflict
%ANALDISK-W-DELETE, file (13431,7,0)
error deleting file
-SYSTEM-W-ACCONFLICT, file access conflict

please help

[Jess Goodman]

The first message is NOT an error. Note the "-I-" in the first line. That means it is Informational. It is just telling you that disk quotas are not enabled on this volume. The secondary ("-" prefix) warning (-W-") messsage "no such file" is just how ANALDISK detected this.

The "%ANALDISK-W-DELETE" messages are warnings and can be ignored too. They indicate that the disk scan found files that were "marked for delete". This means that the files should be automatically deleted when they are closed by all users and applications.

Sometimes this doesn't happen (system crash, etc.) so ANALYZE/DISK will TRY to delete all such "marked for delete" files it finds. But these two files are still open, so the delete attempt fails due to "file access conflict".

[Hein van den Heuvel]

These are all just warnings and informationals.

There is no quota file.
That's just fine when not using quota.

A file which analyze/disk though should be deleted, probably because it was marked for delete, could not be deleted because it was in use "access conflict".
Sounds fine to me.

You _may_ want to check what file it was reporting on using either:

$DUMP/HEAD/BLO=COUNT=0 ( or 1) /ID=6361 disk:

or

$WRITE SYS$OUTPUT F$FID ("disk:", "6361,66,0")

Now please realize that his is not unlikely to fail or give odd results if it was a transient situation.

In the above "disk:" must be replaced with the (logical) name for the disk in question.

Also... Be sure to check out

$HELP/MESSAGE/FAC=ANA DELETE ( or whatever)

hth,
Hein.

[Hoff]

These are probably normal warnings; the stuff shown is typically harmless fodder.

Now... Why are you running ANALYZE /DISK /REPAIR here?

And why are running it against an active disk?

I'm presuming there's a reason or a trigger here around why you've gotten this tool out of the toolbox and have started to use it, of course.

[GuentherF]

I think I haven't seen this one before: "error deleting file"

Why would ANALYZE/DISK/REPAIR try to delete a file?

I would definitely try to find out which file that is with file ID (6361,66,0) and (13431,7,0).

/Guenther

[Jim_McKinney]

> Why would ANALYZE/DISK/REPAIR try to delete a file?

The file's header in the INDEXF been marked for delete but the file is still present on the disk. And the delete might fail if... file is still open (ACCONFLICT), maybe an installed image that has been replaced and marked for deletion but is still being accessed by some process (there are other cases where a file can be in use but marked for delete).

[Volker Halle]

Günther,

>Why would ANALYZE/DISK/REPAIR try to delete >a file?

$ ANAL/DISK/REPAIR/CONFIRM might do this.

The ACCONFLICT message indicates, that this file is still opened.

Volker.

[GuentherF]

Volker,

would you expect a disk structure utility to delete user files? Entering them in SYSLOST or, dealing with files makred for delte, ja, but deleting a file???

/Guenther

[Steven Schweda]

> would you expect a disk structure utility to
> delete user files? Entering them in SYSLOST
> or, dealing with files makred for delte, ja,
> but deleting a file???

My idea of dealing with a file marked for
delete is to delete it. What would _you_
expect to happen to it? (It's marked for
_delete_, so let's _save_ it somewhere?)

[GuentherF]

Steve,

I didn't see in the original report that the file was marked for delete. Hence I wonder why ANALYZE tries to delete a file.

/Guenther