Almost all the errors that show up in your ANALYZE/DISK output are normal and to be expected since you ran it on an active volume without using the /REPAIR or /LOCK qualifiers.
If you investigate I'm sure you will find that the files mentioned in the BADDIRENT, BAD_FIDSEQ, and BAD_DIRFIDSEQ messags were being created and/or deleted while you were running ANAL/DISK. You might also get them for old files if the system crashed, etc. while those files were being created or deleted, but /REPAIR will fix those.
Likewise the errors ALLOCCLR, or its cousins ALLOCSET and DUALLOC, will occur on an active volume. I'm not sure about the ALLOCEXT message but it might also be normal when multitple file headers are involved.
Tbe DELHEADER message is normal even with the disk locked if a file has been marked for delete on close but is still open by an application.
On the other hand I'm not sure why you would get the BADNAMEFORM or BADHEADER messages unless those particular file headers were corrupted.
Bottom line: ANAL/DISK without /REPAIR or DFU VERIFY without /FIX (or /LOCK) are both pretty useless for detecting file corruption on a volume with file activity.
I've always wondered if it would be possible to first scan the volume without /LOCKing it, make a list of *potential* problems, and then do a quick lock/check/unlock for each problem in the list.
This approach wouldn't work for ALLOCCLR errors since you would have to rescan the entire index file to confirm the problem, but ALLOCLCR is just lost space, not real corruption anyway.
However it should allow a real quick check (in terms of how long the volume is locked) for whether ALLOCSET, DUALLOC, BADDIRENT, BAD_FIDSEQ and some other errors detected during an unlocked pass were real errors or not.
I realize this approach would give some false negatives since a real problem with the storage bitmap can, on an active volume, migrate between various files and from being detected as ALLOCSET or as DUALLOC. Still this option would be an extremely valuable tool for detecting real disk corruption without locking large active volumes for several minutes - which is the only option available now
I have one, but it's personal.
