Re: Cluster Freezes

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

This is actually one of the steps I used to troubleshooting this issue.

I took everything offline one at a time to determine if it really was the
disk that was causing the delay in failover and it was.

I take all the resources offline and then move group and then bring IP and
Network Name online, with out any issues. Then I bring each Physical disk
online one at a time and out of the 8 disk 4 of them are taking an extremely
long time to come online. Sometimes as much as 10 minutes for a few of these
disk.

I tried the following KB with no success.
http://support.microsoft.com/kb/929269/en-us


"John Toner [MVP]" wrote:

Odd indeed. Try taking the group offline manually, then move group, then
bring each disk online one at a time. Does this come online faster?

Regards,
John

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

"Rog" <Rog@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E6A8D19C-727C-450D-9AAD-84B3040F0495@xxxxxxxxxxxxxxxx
None, that's is what is odd. I was expecting to have some.

"John Toner [MVP]" wrote:

Are you getting chkdsk logs in you c:\windows\cluster folder when you
fail
over?

Regards,
John

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

"Rog" <Rog@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8875249E-37C3-4F69-8AC4-EACEFCDA4A0C@xxxxxxxxxxxxxxxx
I am not using shadow copy, only using file shares and I have one
service
resource called Extreme Z-IP, that has a dependency of all the disk.

If I take the group offline and bring the disk online one by one. Of
the 8
disk, 4 of them take a long time to come on...as much as 5 minutes per
each
disk. I changed the disk settings so there are no dep. now, but that
didn't
seem to make a difference.

I have 3 other cluster groups and they don't have any issues with disk
or
the group coming online or moving.

So, my natural reaction is that maybe I need to run chkdsk on these 4
disk.
But, not sure where to go from here?

"Edwin vMierlo [MVP]" wrote:


But, the real problem is coming back online. IP and Network name
are
fast
and then I have a period of about 30 minutes waiting for the
Physical
disk
to
come online and then the fileshares come online quickly after or
it
never
finishes bringing the disk online before it freezes.


That is good information,

Question I would ask is, is the time it takes to online the same or
similar
if you take the groups offline, and the only online the disk
(without
moving
any groups) ?

Second question I would ask is are you using shadow copies ?

If your answer is yes to both, the please look at this KB
http://support.microsoft.com/?id=945058

rgds,
Edwin.









.

Relevant Pages

  • Re: Cluster Freezes
    ... When testing the offline times I notice that the file shares go offline in a ... the Physical disk seem to take atleast 30-45 seconds to ... The failover time for all the resources is really good maybe 20 seconds tops ... the real problem is coming back online. ...
    (microsoft.public.windows.server.clustering)
  • Re: Disk Ressource are pointin to different disks
    ... during the time when they wanted to bring this group online the ... disk was presented to the cluster and not offline as it was most of the ...
    (microsoft.public.windows.server.clustering)
  • Re: Cluster Ressource not Fail
    ... Quorum disk ... DisksOpenResourceFileHandle: Disk unique id present trying new ... Online, Send Offline IOCTL to all existing volumes, then Online IOCTL. ... Ip-address -> no Dep. ...
    (microsoft.public.windows.server.clustering)
  • Re: Cluster Ressource not Fail
    ... Quorum disk ... DisksOpenResourceFileHandle: Disk unique id present trying new ... Online, Send Offline IOCTL to all existing volumes, then Online IOCTL. ... Ip-address -> no Dep. ...
    (microsoft.public.windows.server.clustering)
  • Re: Move fails - some drives do not come online?
    ... if disks come online on any node of a cluster, then no disk signatures have changed. ... That step is to set the cluster service to manual and the cluster disk driver to 'demand' on SQL 4 and shut it down. ... Boot up SQL4 and examine disk manager to see if that node sees all disks properly and then do a quick write test to the drives in question. ...
    (microsoft.public.windows.server.clustering)