RE: Event ID:55; Source:NTFS
- From: MarkFox <MarkFox@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 25 Apr 2006 11:42:03 -0700
Sorry, typo, the command is c:>fsutil dirty query f: then you will get an
answer dirty or not dirty.
--
Mark
"MarkFox" wrote:
Carlos,.
Sometimes this message can be ignored, but to check you can run the fsutil
command to determine if the dirty bit is set on the drive reporting the
corruption as follows; fsutil dirry query f: This will check for the dirty
bit on the f: drive. If the result says f: is dirty then you have some
corruption and chkdsk will run at the new resource move/failover. If the
result is not dirty then you should not have to worry about it. We use
Veritas Netbackup and in the past it has generated this message that turned
out to be wrong. Just an FYI, everytime you move a resource or it fails over
the cluster checks for corruption and runs chkdsk if needed.
Hope that helps.
--
Mark
"Carlos" wrote:
Hi,
I recently installed a two-node W2003 SP1 Cluster. Now I´m getting error 55
"The file system structure on disk is corrupt and unusable" with source NTFS.
I´ve checked this error can be ignored
(http://support.microsoft.com/?kbid=885688), but I don´t agree putting the
system in production in this situation.
Can I avoid this error in any way? (clusdisk.sys vs ntfs.sys, versions?)
Which diagnostic tools can I run?
Thanks in advance
Carlos
- Prev by Date: Re: Server Clusters: Rolling Upgrades. Upgrading to Windows Server
- Next by Date: RE: Latest MS patches
- Previous by thread: NLB and ghost images?
- Next by thread: Browse printers in AD on clustered win2k3
- Index(es):
Relevant Pages
|