System Error - VolSnap - flush and hold

JohnBick · **Posted:** Fri Jan 04, 2008 10:00 am

I received the following error once, about a week after a factory reset on my MSS. Can anyone explain this? It is interesting that, for Server 2003, the initial link directs the user to a knowledge base article that references Shadow Copies and disk fragmentation. (I have not copied the article into here but did make sure the link was included below.)

The event details:

Quote:

Category: None

The flush and hold operation for volume C:\fs\E was aborted because of low available system memory.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp

And from that link:

Quote:

Details
Product: Windows Operating System
ID: 21
Source: VolSnap
Version: 5.2.3790.1830
Message: Volume Snapshot Driver: The system may be low on resources.

Explanation
This event indicates that Volume Snapshot Driver was not able to allocate enough system resources to perform an operation.
Cause
Possible causes include:
• The system is low on memory.
• The system is low on CPU resources.
• The system has a high disk I/O load.

User Action
Do one or more of the following:
• Monitor the system resources (CPU usage and disk I/O performance) to identify what is causing the system to be low on resources.
• Schedule Volume Shadow Copy Service or other operations during the least busy periods for the system.
• Move the Diff Area to a different, dedicated volume.

Related Knowledge Base articles
You can find additional information on this topic in the following Microsoft Knowledge Base articles:
• Event ID 21 is logged when you create a shadow copy backup on a Windows Server 2003-based computer ( http://support.microsoft.com/kb/907875/en-us )

Describes the problem where Event ID 21 is logged in the System log when you create a shadow copy backup on a Windows Server 2003-based computer. Provides a resolution and a workaround for this problem.

I have NOT attempted the work-around suggested and am, for the moment, somewhat hesitant to do so. Could this be the "problem" with Shadow Copies on the MSS?

yakuza · **Posted:** Fri Jan 04, 2008 10:24 am

My understanding is that discussed lack of VSS is simply due to it being disabled on the HP boxes, not a failing service.

GryfonHPS · **Posted:** Mon Jun 02, 2008 8:07 am

As I, and possibly others too, are still getting this VolSnap error every few days or so, does anyone know if there is a 'fix' in the pipeline as part of the HP update that was pulled last week, or is this going to remain an issue? Mine has reported an issue on 29/5 (twice), 30/5, and 2/6 requiring a 'repair' being run each time on the System drive.

The message always refers to the Flush & Hold being aborted due to low System Memory

Is it being caused by lack of memory in the device (i.e. 512MB is too small) or what?

Oddly it seems to occur at between 00:00:20 and 00:01:40 on the days it does fail when no other hardware is running on my LAN.

JohnBick · **Posted:** Mon Jun 02, 2008 9:32 am

It is interesting that I have not seen this error since I upgraded my memory to 2 GB (and the CPU to LE-1640).

Maybe more accurate to say I do not RECALL seeing the error. It is not currently showing in my event logs anywhere, but those were cleared a few weeks ago.

System Error - VolSnap - flush and hold

Who is online