Chkdsk - read only anomalies

[Guest]

It's a known fact that when someone tries to run chkdsk from the command
prompt (read only), certain errors crop up similar to the following:

Stage 2 of Chkdsk
Recovering orphaned file PERFLI~2.DAT (75852) into directory file 72

Stage 3 of Chkdsk
Correcting errors in the master file table's (MFT) BITMAP attribute
Correcting errors in the Volume Bitmap
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows found problems with the file system.

Microsoft confirms that these type of errors may crop up and they just
inform the users to ignore them. Should this be a cause for concern ? All I
am asking is why are we allowed to run chkdsk of the System Volume from the
command prompt when these type of errors always crop up ? In various forums,
I read comments from other users whereas it seems that data really gets
either corrupted or lost (as in my case). I also read that certain 3rd party
av software or ad-aware products may cause data corruption (eg Kaspersky AV
6). This problem is causing a headache to a lot of users and although I read
a lot of articles re this issue, none seem to detail a solution. With this
pace, we will all end up including the chkdsk /f as a startup option when
booting Windows XP Pro. Any comments are mostly appreciated.

 

[databaseben]

The o.s. is much more complex
then it use to be..

Basically, when the Microsoft master programmers,
ie, certified technicians, say "don't worry about it" then it sounds like
good advice to me.

 

[Rock]

It's a known fact that when someone tries to run chkdsk from the command
prompt (read only), certain errors crop up similar to the following:

Stage 2 of Chkdsk
Recovering orphaned file PERFLI~2.DAT (75852) into directory file 72

Stage 3 of Chkdsk
Correcting errors in the master file table's (MFT) BITMAP attribute
Correcting errors in the Volume Bitmap
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows found problems with the file system.

Microsoft confirms that these type of errors may crop up and they just
inform the users to ignore them. Should this be a cause for concern ?
No.

All I am asking is why are we allowed to run chkdsk of the System Volume
from the
command prompt when these type of errors always crop up ?

Why does the answer to that matter? If you can't do anything about it then
why worry about why?

In various forums, I read comments from other users whereas it seems that
data really gets
either corrupted or lost (as in my case).

Data loss or corruption through the use of chkdsk is a different issue than
what you are asking about. It doesn't happen in this check only mode. And
never run a chkdsk with the option to correct errors without having a full
and complete backup. Why would you not think that problems can happen when
doing something like this?

I also read that certain 3rd party av software or ad-aware products may
cause data corruption (eg Kaspersky AV
6). This problem is causing a headache to a lot of users and although I
read
a lot of articles re this issue, none seem to detail a solution. With
this
pace, we will all end up including the chkdsk /f as a startup option when
booting Windows XP Pro. Any comments are mostly appreciated.

If you have questions about data corruption caused by 3rd party programs ask
the tech support and in the user forums for those programs.