I am also facing the Same issue and resource is getting same time when defregmentation is running on this disk.
> On Friday, March 02, 2007 1:18 PM Da wrote:
> Hey guys,
> I had a failure and eventually a problem with my physical disk resource
> this morning and was wondering if these log entries mean anything to
> anyone... The failure happened at about 17:25 and we were back up about 10
> minutes later with a physical disk error. Simply choosing to bring the disk
> back online solved it and we're back up. The event logs have absolutely
> nothing in them that point me to root cause... Here's the cluster.log stuff
> from that time frame.
>
> 00000d7c.000008c4::2007/03/02-16:17:28.856 INFO [LM] LogGetLastChkPoint
> exit, returning 0x00000000
> 00000d7c.000008c4::2007/03/02-16:17:28.856 INFO [Qfs] QfsCloseHandle 2b0,
> status 0
> 00000d7c.000008c4::2007/03/02-16:17:28.856 INFO [Qfs] QfsCloseHandle 94c,
> status 0
> 00000d7c.000008c4::2007/03/02-16:17:28.871 INFO [Qfs] QfsMoveFileEx
> Q:\MSCS\tqu3AC0.tmp=>Q:\MSCS\quolog.log
> 00000d7c.000008c4::2007/03/02-16:17:28.871 INFO [Qfs] QfsOpenFile
> Q:\MSCS\quolog.log => 4, 94c status 0
> 00000d7c.000008c4::2007/03/02-16:17:28.871 INFO [LM] LogpReset exit,
> returning 0x00000000
> 00000d7c.000008c4::2007/03/02-16:17:28.871 INFO [LM] LogReset exit,
> returning 0x00000000
> 00000d7c.000008c4::2007/03/02-16:17:57.153 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000d7c.000008c4::2007/03/02-16:22:57.155 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000d7c.000008c4::2007/03/02-16:27:57.159 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000d7c.000008c4::2007/03/02-16:32:57.163 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000d7c.000008c4::2007/03/02-16:37:57.166 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000d7c.000008c4::2007/03/02-16:42:57.169 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000d7c.000008c4::2007/03/02-16:47:57.175 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000d7c.000008c4::2007/03/02-16:52:57.178 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000d7c.000008c4::2007/03/02-16:57:57.180 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000d7c.000008c4::2007/03/02-17:03:27.888 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000d7c.000008c4::2007/03/02-17:08:18.878 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000d7c.000008c4::2007/03/02-17:13:05.925 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000d7c.000008c4::2007/03/02-17:17:57.194 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000d7c.000008c4::2007/03/02-17:22:57.200 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000d7c.000008c4::2007/03/02-17:28:26.405 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000ac4.00000ad0::2007/03/02-17:32:38.720 INFO File Share <User>: Retrying
> FindFirstFile on error 64 for share \\RWCFPNODE1\User\*.* !
> 00000ac4.000016a0::2007/03/02-17:32:38.720 INFO File Share <Corpweb>:
> Retrying FindFirstFile on error 64 for share \\RWCFPNODE1\corpweb\*.* !
> 00000d7c.000008c4::2007/03/02-17:32:57.204 INFO [Qfs] GetDiskFreeSpaceEx
> Q:\MSCS\, status 0
> 00000ac4.00000ad0::2007/03/02-17:33:46.971 INFO File Share <User>: Retrying
> FindFirstFile on error 64 for share \\RWCFPNODE1\User\*.* !
> 00000ac4.000016a0::2007/03/02-17:33:46.971 INFO File Share <Corpweb>:
> Retrying FindFirstFile on error 64 for share \\RWCFPNODE1\corpweb\*.* !
> 00000d14.00000d18::2007/03/02-17:37:05.921 INFO
>
> 00000d14.00000d18::2007/03/02-17:37:05.921 INFO [CS] Cluster Service started
> - Cluster Node Version 4.3790
> 00000d14.00000d18::2007/03/02-17:37:05.921 INFO
> OS Version 5.2.3790 - Service Pack 1 (ADS 03000112L)
> 00000d14.00000d18::2007/03/02-17:37:05.921 INFO
> Local Time is 2007/03/02-09:37:05.921
> 00000d14.00000d28::2007/03/02-17:37:05.921 INFO [CS] Service Starting...
> 00000d14.00000d28::2007/03/02-17:37:05.921 INFO [INIT] ClusterInitialize
> called to start cluster.
> 00000d14.00000d28::2007/03/02-17:37:05.953 INFO [EP] Initialization...
>
> Thanks,
> Dan
>> On Monday, March 05, 2007 9:54 AM John Toner [MVP] wrote:
>> FYI, the cluster logs are based on GMT time, so make sure you're looking at
>> the log entries at the appropriate time frame. If your servers aren't set to
>> GMT time, we're probably looking at the wrong entries.
>>
>> Regards,
>> John
>>
>> "Dan" <> wrote in message
>> news:F6D68283-37E0-4F04-9831-...
>> 10
>> disk
>> stuff
>> Retrying
>> Retrying
>> started
>>> On Monday, March 05, 2007 10:33 AM Jeff Hughes [MSFT] wrote:
>>> None of those cluster log entries point to any disk problem. However, this
>>> entry:
>>>
>>>
>>> Indicates you might have a problem with the server service. I see these alot
>>> when there's potential system resource issues and the server service cannot
>>> handle the cluster asking "Hey, is my network name still online?". That's
>>> what the error 64 means. You might want to do some perf mon'ing if you see
>>> this reoccur. If it follows a pattern, look for things going on when the
>>> file shares fail like a backup, defrag, etc.
>>> --
>>> Jeff Hughes, MCSE
>>> Support Escalation Engineer
>>> Microsoft Enterprise Platforms Support (Server Core/Cluster)
>>> "Dan" <> wrote in message
>>> news:F6D68283-37E0-4F04-9831-...
|