Unsolved

This post is more than 5 years old

1 Rookie

 • 

4 Posts

750

November 6th, 2006 11:00

autostart chkdsks large shared drive

I have an 810 GB shared SAN drive on my dmx1000 that windows 2000 adv server will chkdsk when failing over from its cluster partner. chkdsk takes 6 hours to complete. by the time it's done, we cannot troubleshoot as we're trying to get our production corporate imaging system back online. shared drive has approximately 14 million files. this is the second attempt we've made doing this with no luck. it bombs in the identical spot. aam 5.1.2, server A w2k adv server w/sp4, server B w2k3 with sp1

Autostart support recommends a good delay between the shutting down of the IP address and offlining the drive to let windows flush the cache, yet I've heard that during the drive offline autostart flushes the cache

Here are the results of the chkdsk;

Checking file system on I:
The type of the file system is NTFS.
Volume label is Images3.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 2421 unused index entries from index $SII of file 0x9.
Cleaning up 2421 unused index entries from index $SDH of file 0x9.
Cleaning up 2421 unused security descriptors.
CHKDSK is verifying Usn Journal...
The USN Journal length 0x8856bfb40 in file 0x7b9c is less the
largest USN encountered, 0x8856c42d0, plus eight in file 0xc9998a.
Repairing Usn Journal $J data stream.
Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the volume bitmap.
Windows has made corrections to the file system.

857340823 KB total disk space.
770188316 KB in 13770360 files.
4719268 KB in 1018093 indexes.
0 KB in bad sectors.
14887283 KB in use by the system.
65536 KB occupied by the log file.
67545956 KB available on disk.

4096 bytes in each allocation unit.
214335205 total allocation units on disk.
16886489 allocation units available on disk.

1 Rookie

 • 

22 Posts

November 16th, 2006 18:00

What option do you have configure in the data source about chkdsk? you must configure dirty bit option

1 Rookie

 • 

4 Posts

November 17th, 2006 10:00

we have the chkdsk set to run if it finds a dirty bit. because autostart now owns the disk, it will behave like windows and look for a dirty bit. if it sees the dirty bit, it will run chkdsk /f like windows would.

autostart support has recommended that we turn that off, yet microsoft says problems will snowball if you don't chkdsk. I don't see why you would leave it off.

autostart is leaning towards open handles on the shared drive, but I cannot figure out what would be causing this. our test environment has open handles and autostart does not chkdsk here. we even bcv'd the production volume to test, passed it back and forth between cluster nodes and could NOT break it and we tried.

thanks edgar

Top