{Delayed Write Failed} message on Windows 2003 R2 Cluster

Sponsored Links

I am receiving the following sequence of events on an R2 3-node
cluster. What concerns me is the " delayed write failed" message.

Event Type: Information
Event Source: Quota
Event Category: None
Event ID: 9
Date: 1/23/2007
Time: 7:33:32 PM
User: N/A
Computer: SERVER1
Description:
The quota minifilter driver was successfully attached to volume
"\Device\tsmlvsa\Volume{c2ec42f3-7bde-11db-a85c-0015600b (%3)" but the
quota usage information is possibly out of date, and the volume will be
rescanned. This can typically occur as a result of a system crash,
quota configuration backup/restore, and volume failover in a cluster.
Once the scan completes quotas will function properly.

Event Type: Information
Event Source: Quota
Event Category: None
Event ID: 10
Date: 1/23/2007
Time: 7:33:32 PM
User: N/A
Computer: SERVER2
Description:
The quota minifilter driver completed rescanning directories under
quota management on volume
"\Device\tsmlvsa\Volume{c2ec42f3-7bde-11db-a85c-0015600b (%3)". All
quota information is up-to-date.

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 1/23/2007
Time: 7:33:33 PM
User: N/A
Computer: SERVER1
Description:
Application popup: Windows - Delayed Write Failed : Windows was unable
to save all the data for the file R:\System Volume
Information\SRM\quota.md. The data has been lost. This error may be
caused by a failure of your computer hardware or network connection.
Please try to save this file elsewhere.


Event Type: Warning
Event Source: Ntfs
Event Category: None
Event ID: 50
Date: 1/23/2007
Time: 7:33:33 PM
User: N/A
Computer: SERVER1
Description:
{Delayed Write Failed} Windows was unable to save all the data for the
file . The data has been lost. This error may be caused by a failure of
your computer hardware or network connection. Please try to save this
file elsewhere.

Yea, I would be concerned about that as well. If there is file corruption
here then the quota information for that file system may be lost as well.
You can run the 'chkntfs' command against the drive in question to see if
the dirty bit is being set. If it is, you will need to run a chkdsk
operation to fix the file system. Typically lost-delayed writes start
pointing to a hardware issue or a 3rd party app that has a handle on a
clustered disk and is not releasing when cluster needs to take it offline
for any reason.

Chuck Timon, Jr.
Microsoft Corporation
Longhorn Readiness Team
This posting is provided "AS IS" with no warranties, and confers no rights.

"Tom" <usernetuser@yahoo.com> wrote in message
news:1169660193.583852.211980@a34g2000cwb.googlegroups.com...
>I am receiving the following sequence of events on an R2 3-node
> cluster. What concerns me is the " delayed write failed" message.
>
> Event Type: Information
> Event Source: Quota
> Event Category: None
> Event ID: 9
> Date: 1/23/2007
> Time: 7:33:32 PM
> User: N/A
> Computer: SERVER1
> Description:
> The quota minifilter driver was successfully attached to volume
> "\Device\tsmlvsa\Volume{c2ec42f3-7bde-11db-a85c-0015600b (%3)" but the
> quota usage information is possibly out of date, and the volume will be
> rescanned. This can typically occur as a result of a system crash,
> quota configuration backup/restore, and volume failover in a cluster.
> Once the scan completes quotas will function properly.
>
> Event Type: Information
> Event Source: Quota
> Event Category: None
> Event ID: 10
> Date: 1/23/2007
> Time: 7:33:32 PM
> User: N/A
> Computer: SERVER2
> Description:
> The quota minifilter driver completed rescanning directories under
> quota management on volume
> "\Device\tsmlvsa\Volume{c2ec42f3-7bde-11db-a85c-0015600b (%3)". All
> quota information is up-to-date.
>
> Event Type: Information
> Event Source: Application Popup
> Event Category: None
> Event ID: 26
> Date: 1/23/2007
> Time: 7:33:33 PM
> User: N/A
> Computer: SERVER1
> Description:
> Application popup: Windows - Delayed Write Failed : Windows was unable
> to save all the data for the file R:\System Volume
> Information\SRM\quota.md. The data has been lost. This error may be
> caused by a failure of your computer hardware or network connection.
> Please try to save this file elsewhere.
>
>
> Event Type: Warning
> Event Source: Ntfs
> Event Category: None
> Event ID: 50
> Date: 1/23/2007
> Time: 7:33:33 PM
> User: N/A
> Computer: SERVER1
> Description:
> {Delayed Write Failed} Windows was unable to save all the data for the
> file . The data has been lost. This error may be caused by a failure of
> your computer hardware or network connection. Please try to save this
> file elsewhere.
>

Thanks Chuck. I checked the drive in question & it is not dirty. I've
seen this happening only after FSRM was installed & quota was enabled
on a volume on that drive. Are there any patches & hotfixes that I
should be aware of as far as FSRM & R2 clustering are concerned?

On Jan 24, 3:01 pm, "Chuck Timon [Microsoft]"
<cti...@online.microsoft.com> wrote:
> Yea, I would be concerned about that as well. If there is file corruption
> here then the quota information for that file system may be lost as well.
> You can run the 'chkntfs' command against the drive in question to see if
> the dirty bit is being set. If it is, you will need to run a chkdsk
> operation to fix the file system. Typically lost-delayed writes start
> pointing to a hardware issue or a 3rd party app that has a handle on a
> clustered disk and is not releasing when cluster needs to take it offline
> for any reason.
>
> Chuck Timon, Jr.
> Microsoft Corporation
> Longhorn Readiness Team
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Tom" <usernetu...@yahoo.com> wrote in messagenews:1169660193.583852.211980@a34g2000cwb.googlegroups.com...
>
>
>
> >I am receiving the following sequence of events on an R2 3-node
> > cluster. What concerns me is the " delayed write failed" message.
>
> > Event Type: Information
> > Event Source: Quota
> > Event Category: None
> > Event ID: 9
> > Date: 1/23/2007
> > Time: 7:33:32 PM
> > User: N/A
> > Computer: SERVER1
> > Description:
> > The quota minifilter driver was successfully attached to volume
> > "\Device\tsmlvsa\Volume{c2ec42f3-7bde-11db-a85c-0015600b (%3)" but the
> > quota usage information is possibly out of date, and the volume will be
> > rescanned. This can typically occur as a result of a system crash,
> > quota configuration backup/restore, and volume failover in a cluster.
> > Once the scan completes quotas will function properly.
>
> > Event Type: Information
> > Event Source: Quota
> > Event Category: None
> > Event ID: 10
> > Date: 1/23/2007
> > Time: 7:33:32 PM
> > User: N/A
> > Computer: SERVER2
> > Description:
> > The quota minifilter driver completed rescanning directories under
> > quota management on volume
> > "\Device\tsmlvsa\Volume{c2ec42f3-7bde-11db-a85c-0015600b (%3)". All
> > quota information is up-to-date.
>
> > Event Type: Information
> > Event Source: Application Popup
> > Event Category: None
> > Event ID: 26
> > Date: 1/23/2007
> > Time: 7:33:33 PM
> > User: N/A
> > Computer: SERVER1
> > Description:
> > Application popup: Windows - Delayed Write Failed : Windows was unable
> > to save all the data for the file R:\System Volume
> > Information\SRM\quota.md. The data has been lost. This error may be
> > caused by a failure of your computer hardware or network connection.
> > Please try to save this file elsewhere.
>
> > Event Type: Warning
> > Event Source: Ntfs
> > Event Category: None
> > Event ID: 50
> > Date: 1/23/2007
> > Time: 7:33:33 PM
> > User: N/A
> > Computer: SERVER1
> > Description:
> > {Delayed Write Failed} Windows was unable to save all the data for the
> > file . The data has been lost. This error may be caused by a failure of
> > your computer hardware or network connection. Please try to save this
> > file elsewhere.- Hide quoted text -- Show quoted text -

Here is a list of all recommended Post-SP1 cluster fixes -
http://support.microsoft.com/kb/923830/en-us

Chuck Timon, Jr.
Microsoft Corporation
Longhorn Readiness Team
This posting is provided "AS IS" with no warranties, and confers no rights.

"Tom" <usernetuser@yahoo.com> wrote in message
news:1169672254.854876.98270@j27g2000cwj.googlegroups.com...
> Thanks Chuck. I checked the drive in question & it is not dirty. I've
> seen this happening only after FSRM was installed & quota was enabled
> on a volume on that drive. Are there any patches & hotfixes that I
> should be aware of as far as FSRM & R2 clustering are concerned?
>
> On Jan 24, 3:01 pm, "Chuck Timon [Microsoft]"
> <cti...@online.microsoft.com> wrote:
>> Yea, I would be concerned about that as well. If there is file
>> corruption
>> here then the quota information for that file system may be lost as well.
>> You can run the 'chkntfs' command against the drive in question to see if
>> the dirty bit is being set. If it is, you will need to run a chkdsk
>> operation to fix the file system. Typically lost-delayed writes start
>> pointing to a hardware issue or a 3rd party app that has a handle on a
>> clustered disk and is not releasing when cluster needs to take it offline
>> for any reason.
>>
>> Chuck Timon, Jr.
>> Microsoft Corporation
>> Longhorn Readiness Team
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Tom" <usernetu...@yahoo.com> wrote in
>> messagenews:1169660193.583852.211980@a34g2000cwb.googlegroups.com...
>>
>>
>>
>> >I am receiving the following sequence of events on an R2 3-node
>> > cluster. What concerns me is the " delayed write failed" message.
>>
>> > Event Type: Information
>> > Event Source: Quota
>> > Event Category: None
>> > Event ID: 9
>> > Date: 1/23/2007
>> > Time: 7:33:32 PM
>> > User: N/A
>> > Computer: SERVER1
>> > Description:
>> > The quota minifilter driver was successfully attached to volume
>> > "\Device\tsmlvsa\Volume{c2ec42f3-7bde-11db-a85c-0015600b (%3)" but the
>> > quota usage information is possibly out of date, and the volume will be
>> > rescanned. This can typically occur as a result of a system crash,
>> > quota configuration backup/restore, and volume failover in a cluster.
>> > Once the scan completes quotas will function properly.
>>
>> > Event Type: Information
>> > Event Source: Quota
>> > Event Category: None
>> > Event ID: 10
>> > Date: 1/23/2007
>> > Time: 7:33:32 PM
>> > User: N/A
>> > Computer: SERVER2
>> > Description:
>> > The quota minifilter driver completed rescanning directories under
>> > quota management on volume
>> > "\Device\tsmlvsa\Volume{c2ec42f3-7bde-11db-a85c-0015600b (%3)". All
>> > quota information is up-to-date.
>>
>> > Event Type: Information
>> > Event Source: Application Popup
>> > Event Category: None
>> > Event ID: 26
>> > Date: 1/23/2007
>> > Time: 7:33:33 PM
>> > User: N/A
>> > Computer: SERVER1
>> > Description:
>> > Application popup: Windows - Delayed Write Failed : Windows was unable
>> > to save all the data for the file R:\System Volume
>> > Information\SRM\quota.md. The data has been lost. This error may be
>> > caused by a failure of your computer hardware or network connection.
>> > Please try to save this file elsewhere.
>>
>> > Event Type: Warning
>> > Event Source: Ntfs
>> > Event Category: None
>> > Event ID: 50
>> > Date: 1/23/2007
>> > Time: 7:33:33 PM
>> > User: N/A
>> > Computer: SERVER1
>> > Description:
>> > {Delayed Write Failed} Windows was unable to save all the data for the
>> > file . The data has been lost. This error may be caused by a failure of
>> > your computer hardware or network connection. Please try to save this
>> > file elsewhere.- Hide quoted text -- Show quoted text -
>

Elden wrote KB 244780, and if you have the hex data from the event ID 50,
you can use that article to decode it. An event ID 50 is the same format as
a 51..


"Tom" <usernetuser@yahoo.com> wrote in message
news:1169672254.854876.98270@j27g2000cwj.googlegroups.com...
> Thanks Chuck. I checked the drive in question & it is not dirty. I've
> seen this happening only after FSRM was installed & quota was enabled
> on a volume on that drive. Are there any patches & hotfixes that I
> should be aware of as far as FSRM & R2 clustering are concerned?
>
> On Jan 24, 3:01 pm, "Chuck Timon [Microsoft]"
> <cti...@online.microsoft.com> wrote:
>> Yea, I would be concerned about that as well. If there is file
>> corruption
>> here then the quota information for that file system may be lost as well.
>> You can run the 'chkntfs' command against the drive in question to see if
>> the dirty bit is being set. If it is, you will need to run a chkdsk
>> operation to fix the file system. Typically lost-delayed writes start
>> pointing to a hardware issue or a 3rd party app that has a handle on a
>> clustered disk and is not releasing when cluster needs to take it offline
>> for any reason.
>>
>> Chuck Timon, Jr.
>> Microsoft Corporation
>> Longhorn Readiness Team
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Tom" <usernetu...@yahoo.com> wrote in
>> messagenews:1169660193.583852.211980@a34g2000cwb.googlegroups.com...
>>
>>
>>
>> >I am receiving the following sequence of events on an R2 3-node
>> > cluster. What concerns me is the " delayed write failed" message.
>>
>> > Event Type: Information
>> > Event Source: Quota
>> > Event Category: None
>> > Event ID: 9
>> > Date: 1/23/2007
>> > Time: 7:33:32 PM
>> > User: N/A
>> > Computer: SERVER1
>> > Description:
>> > The quota minifilter driver was successfully attached to volume
>> > "\Device\tsmlvsa\Volume{c2ec42f3-7bde-11db-a85c-0015600b (%3)" but the
>> > quota usage information is possibly out of date, and the volume will be
>> > rescanned. This can typically occur as a result of a system crash,
>> > quota configuration backup/restore, and volume failover in a cluster.
>> > Once the scan completes quotas will function properly.
>>
>> > Event Type: Information
>> > Event Source: Quota
>> > Event Category: None
>> > Event ID: 10
>> > Date: 1/23/2007
>> > Time: 7:33:32 PM
>> > User: N/A
>> > Computer: SERVER2
>> > Description:
>> > The quota minifilter driver completed rescanning directories under
>> > quota management on volume
>> > "\Device\tsmlvsa\Volume{c2ec42f3-7bde-11db-a85c-0015600b (%3)". All
>> > quota information is up-to-date.
>>
>> > Event Type: Information
>> > Event Source: Application Popup
>> > Event Category: None
>> > Event ID: 26
>> > Date: 1/23/2007
>> > Time: 7:33:33 PM
>> > User: N/A
>> > Computer: SERVER1
>> > Description:
>> > Application popup: Windows - Delayed Write Failed : Windows was unable
>> > to save all the data for the file R:\System Volume
>> > Information\SRM\quota.md. The data has been lost. This error may be
>> > caused by a failure of your computer hardware or network connection.
>> > Please try to save this file elsewhere.
>>
>> > Event Type: Warning
>> > Event Source: Ntfs
>> > Event Category: None
>> > Event ID: 50
>> > Date: 1/23/2007
>> > Time: 7:33:33 PM
>> > User: N/A
>> > Computer: SERVER1
>> > Description:
>> > {Delayed Write Failed} Windows was unable to save all the data for the
>> > file . The data has been lost. This error may be caused by a failure of
>> > your computer hardware or network connection. Please try to save this
>> > file elsewhere.- Hide quoted text -- Show quoted text -
>

[slongo]

Hi, somebody can help me with this error.

Source: Quota
Event ID: 11
A quota scan on directory "\servername\share" on volume "\Device\VSPSnapshot0 (N/A)" failed unexpectedly. Error code: 0xc0000010 The quota usage for the quota on this directory and any parent directories may be incorrect. The affected quotas may not be properly enforced. You can attempt to initiate a new scan using the quota management command line tool. If the problem persists, reboot your system.

and this error

A quota scan on directory "\servername\share" on volume "\Device\VSPSnapshot0 (%5)" failed unexpectedly. Error code: 0x%3 The quota usage for the quota on this directory and any parent directories may be incorrect. The affected quotas may not be properly enforced. You can attempt to initiate a new scan using the quota management command line tool. If the problem persists, reboot your system.


Thanks,
Sergio Longo.

A "Delayed Write Failed" error typically has a corresponding event id 50 in
the system event log, which indicates that the operating system is suddenly
unable to access the physical disk resource. This could explain why the
errors that you mention were logged if we can't access the disk resources
temporarily for some reason.

However to properly troubleshoot this type of problem we would need
additional information found in the system event log around the same time
this problem occurred and possibly also from the cluster log so that we could
correlate events and get a more accurate picture of what was happening on
your cluster at the time the issue occurred.


"slongo" wrote:

>
> Hi, somebody can help me with this error.
>
> Source: Quota
> Event ID: 11
> A quota scan on directory "\servername\share" on volume
> "\Device\VSPSnapshot0 (N/A)" failed unexpectedly. Error code:
> 0xc0000010 The quota usage for the quota on this directory and any
> parent directories may be incorrect. The affected quotas may not be
> properly enforced. You can attempt to initiate a new scan using the
> quota management command line tool. If the problem persists, reboot
> your system.
>
> and this error
>
> A quota scan on directory "\servername\share" on volume
> "\Device\VSPSnapshot0 (%5)" failed unexpectedly. Error code: 0x%3 The
> quota usage for the quota on this directory and any parent directories
> may be incorrect. The affected quotas may not be properly enforced. You
> can attempt to initiate a new scan using the quota management command
> line tool. If the problem persists, reboot your system.
>
>
> Thanks,
> Sergio Longo.
>
>
> --
> slongo
> ------------------------------------------------------------------------
> slongo's Profile: http://forums.techarena.in/members/30744.htm
> View this thread: {Delayed Write Failed} message on Windows 2003 R2 Cluster
>
> http://forums.techarena.in
>
>

Hello there,

We are also encuntering the same error on our file server cluster. We have
just installed File Server Resource Manager on the server. It's a bit weird,
the error seems to pertain to "QUOTA" but we haven't implemented the folder
quota yet only the file screening feature.

thanks,

uNoKaWaL

"Mike [MSFT]" wrote:

> A "Delayed Write Failed" error typically has a corresponding event id 50 in
> the system event log, which indicates that the operating system is suddenly
> unable to access the physical disk resource. This could explain why the
> errors that you mention were logged if we can't access the disk resources
> temporarily for some reason.
>
> However to properly troubleshoot this type of problem we would need
> additional information found in the system event log around the same time
> this problem occurred and possibly also from the cluster log so that we could
> correlate events and get a more accurate picture of what was happening on
> your cluster at the time the issue occurred.
>
>
> "slongo" wrote:
>
> >
> > Hi, somebody can help me with this error.
> >
> > Source: Quota
> > Event ID: 11
> > A quota scan on directory "\servername\share" on volume
> > "\Device\VSPSnapshot0 (N/A)" failed unexpectedly. Error code:
> > 0xc0000010 The quota usage for the quota on this directory and any
> > parent directories may be incorrect. The affected quotas may not be
> > properly enforced. You can attempt to initiate a new scan using the
> > quota management command line tool. If the problem persists, reboot
> > your system.
> >
> > and this error
> >
> > A quota scan on directory "\servername\share" on volume
> > "\Device\VSPSnapshot0 (%5)" failed unexpectedly. Error code: 0x%3 The
> > quota usage for the quota on this directory and any parent directories
> > may be incorrect. The affected quotas may not be properly enforced. You
> > can attempt to initiate a new scan using the quota management command
> > line tool. If the problem persists, reboot your system.
> >
> >
> > Thanks,
> > Sergio Longo.
> >
> >
> > --
> > slongo
> > ------------------------------------------------------------------------
> > slongo's Profile: http://forums.techarena.in/members/30744.htm
> > View this thread: {Delayed Write Failed} message on Windows 2003 R2 Cluster
> >
> > http://forums.techarena.in
> >
> >