none
ESENT Event 508 when Shadow Copies are enabled RRS feed

  • Question

  • Recently set up a new file server (VM running Server 2012 R2). Server has separate OS and Data partitions (each on different physical disk array) and I've enabled Shadow Copies on the Data volume. Server is also running DFS/DFSR and replicating the files on the Data volume with other file servers. The VM is running on Hyper-V host, which is also Server 2012 R2.  

    Each day, when a shadow copy snapshot is taken, the file server generates an ESENT Event ID 508 similar to the following:

    DFSRs (1192) \\.\D:\System Volume Information\DFSR\database_5464_BC1C_64BC_2B2\dfsr.db: A request to write to the file "\\.\D:\System Volume Information\DFSR\database_5464_BC1C_64BC_2B2\fsr.log" at offset 4075520 (0x00000000003e3000) for 4096 (0x00001000) bytes succeeded, but took an abnormally long time (25 seconds) to be serviced by the OS. This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

    So first thought was maybe I do have faulty hardware. But I set up a second file server (on separate physical host with identical hardware) and am seeing the same behavior on that server as well. The odds of both servers having faulty hardware are pretty low, so it must be my configuration.

    I noticed the Shadow Copy storage area was set to the same volume as the snapshot being taken, so I changed that to use the OS volume instead, but that didn't fix it:

    Then I tried turning off Windows write-cache buffer flushing on the Data volume, but that didn't help:

    Tried allocating more (and static) memory to the server, rather than having it use Dynamic Memory, but no change there either. 

    Using Hyper-V manager, tried moving the vhdx file from IDE controller to SCSI, but no change there.

    Anyone else have any suggestions/insight into what the problem might be or how I can fix it?


    Shaun



    • Edited by Shaunm001 Thursday, May 5, 2016 6:34 PM
    Thursday, May 5, 2016 2:34 PM

All replies

  • Hi Shaun,

    Thanks for your post.

    If the event is just one odd occurrence,  then it may be just a transient problem. If it happens on regular basis then the specified drive should be checked for problems (run chkdsk,  make sure you have enough free space and physical memory - running low on memory may affect all the disk operations).        

    http://www.eventid.net/display-eventid-508-source-ESENT-eventno-5580-phase-1.htm

    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

    I've seen before is sometimes caused by an insufficient (or potentially even just low) amount of unused space on your currently running Operating System's HDD/SSD. You might could try to enlarge/cleared up more space to have a check.

    Best Regards,

    Mary Dong


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, May 6, 2016 3:24 AM
    Moderator
  • Thanks, it's more than transient, happens twice a day (each time a VSS snapshot is taken). The volume is 50% utilized, so don't think space is an issue. The volume is a dynamically expanding vhdx, so that could be impacting performance. Maybe this question would be better served in the Hyper-V forums?

    Shaun

    Friday, May 6, 2016 5:51 PM
  • Hi Shaun,

    >The volume is a dynamically expanding vhdx, so that could be impacting performance

    That could be one possible. But as I'm not familiar with the details configuration of hyper-v, not exactly sure.

    Best Regards,

    Mary


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, May 10, 2016 12:48 AM
    Moderator