Re: Correcting corrupt $MFT on shared clustered disk.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Comments inline...

Regards,
John

Visit my blog: http://msmvps.com/blogs/jtoner

"Mike O" <put_the_spam@xxxxxxx> wrote in message
news:u3z24wWAIHA.4568@xxxxxxxxxxxxxxxxxxxxxxx

Thank you for the information. I'd found the maintenance mode KB
article.
After digging into it I figured out I didn't need the extended maintenance
mode and figured out the rest of the article.
The cluster group has two disks, each with shares on it. If I take the
file
share resources for only this disk off line, then take the disk resource
off
line and back, there should be no effect on the other disk & files shares,
even though they're in the same cluster group, correct?


Correct. Chkdsk will tell you if you've got open handles on the drive when
you attempt to run it, so you just need to make sure that the handles are
closed on this disk resource.


I opened the ticket with EMC earlier today. They had me run the SP and
grab
reports. They told me the physical disk structure was OK, although the
did
identify some other issues that had nothing to do with this, though. The
tech said he was going to pass the ticket on to their Windows group and
that
they would call me (they didn't yet..)


We're too busy answering questions in newsgroups instead of doing our jobs
;-)


Currently we have a maintenance "window" from 6:00pm Saturday until about
6:00am Monday. Hopefully 36 hours will be enough to correct the issue.
I've run chkdsk in read-only mode, it identified about 80 things it needed
to fix then said it couldn't contine in "non-fix" mode. Hopefully it
won't
take more than 36 hours...


Have you run a chkdsk on this volume before? It should complete in the same
amount of time. I would guess that it would complete within 36 hours...but I
wouldn't bet my job on it.


I thought about using the mount points, but the problem we have is space
allocation. As I understand it, a junction point looks like a subfolder,
but is a connection to another "drive" (or partition on another drive).
This server has files for about 12 departments. Prior to thsi cluster
most
of them had their own servers. If I assign drives for different areas, I
figure we'll eventually end up with the same problem we had before: some
areas running out of space and others with space to spare. I'm trying not
to have to continually manage and move user files..


You would need to manage/move user files, you just need to manage the amount
of storage you allocate to specific groups...and when a group is running
low, you could expand that LUN to provide additional space. Personally, I'd
rather deal with 12 smaller LUNs than one big ugly LUN.


Thank you again.
Mike O.


Anytime.



.