Symptoms
You deploy a VMware vSphere Data Protection (VDP) appliance on a server that is running Windows Storage Server 2008 R2 or Windows Storage Server 2012. When the deployment accesses the Network File System (NFS) shares on the server, the deployment fails, and you receive the following error message:
Error writing to disk.
Additionally, messages that resemble the following are logged to the "/var/log/vmkernel.log" file during the failure:
# tail –f /var/log/vmkernel.log
2013-03-15T09:30:03.820Z cpu2:9466)BC: 3115: Blocking due to no free buffers. nDirty = 995 nWaiters = 1 2013-03-15T09:30:03.940Z cpu2:9466)BC: 3115: Blocking due to no free buffers. nDirty = 988 nWaiters = 1 2013-03-15T09:30:04.110Z cpu2:9466)BC: 3115: Blocking due to no free buffers. nDirty = 988 nWaiters = 1 2013-03-15T09:30:04.220Z cpu2:9466)BC: 3115: Blocking due to no free buffers. nDirty = 982 nWaiters = 1 2013-03-15T09:30:04.400Z cpu2:9466)BC: 3115: Blocking due to no free buffers. nDirty = 988 nWaiters = 1 2013-03-15T09:30:04.520Z cpu2:9466)BC: 3115: Blocking due to no free buffers. nDirty = 920 nWaiters = 1 2013-03-15T09:31:34.300Z cpu22:9466)BC: 3115: Blocking due to no free buffers. n Dirty = 905 nWaiters = 1 2013-03-15T09:33:07.710Z cpu18:9466)BC: 3115: Blocking due to no free buffers. nDirty = 975 nWaiters = 1 2013-03-15T09:34:45.030Z cpu8:9466)BC: 3115: Blocking due to no free buffers. nDirty = 970 nWaiters = 1 2013-03-15T09:35:17.139Z cpu22:10713)WARNING: UserLinux: 1331: unsupported: (void) 2013-03-15T09:36:16.959Z cpu4:9466)BC: 3115: Blocking due to no free buffers. nDirty = 961 nWaiters = 1 2013-03-15T09:38:30.167Z cpu2:9466)BC: 3115: Blocking due to no free buffers. nDirty = 977 nWaitrs = 1 2013-03-15T09:40:18.908Z cpu0:9466)BC: 3115: Blocking due to no free buffers. nDirty = 977 nWaitrs = 1 2013-03-15T09:42:04.068Z cpu0:8221)NFSLock: 610: Stop accessing fd 0x41000ad83078 3 2013-03-15T09:42:11.082Z cpu2:8194)StorageApdHandler: 248: APD Timer started for ident [e22d08a3-f45c4254] 2013-03-15T09:42:11.082Z cpu2:8194)StorageApdHandler: 395: Device or filesystem with identifier [e22d08a3-f45c4254] has entered the All Paths Down state. 2013-03-15T09:42:11.082Z cpu2:8194)StorageApdHandler: 846: APD Start for ident [e22d08a3-f45c4254]! 2013-03-15T09:43:03.972Z cpu2:8194)NFSLock: 570: Start accessing fd 0x41000ad83078 againNote After the failure occurs and the vSphere client is updated, the NFS data store comes back online.Cause
This problem occurs specifically at 99 percent of progress during the VDP deployment. When the second disk is about to be deployed, the NFS data store becomes inaccessible to an ESX host, and the deployment fails with the error message "Error writing to disk." VMware backups to a network access server (NAS) cannot finish when the NFS server cannot set file sparse on the files that are created by the ESX client.
As soon as the failure is logged to the Vmkernel.log file, you receive the "Error writing to disk" error message.Resolution
This hotfix is also available at Microsoft Update Catalog.
Hotfix information
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
To apply this hotfix, you must be running Windows Server 2008 R2 Service Pack 1 (SP1) or Windows Server 2012. Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2.
For information about how to obtain a Windows Server 2008 R2 service pack, seeRestart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notesImportant Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Version
Product
SR_Level
Service branch
6.1.760
1. 18xxxWindows Server 2008 R2
SP1
GDR
6.1.760
1. 22xxxWindows Server 2008 R2
SP1
LDR
-
GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Msnfsflt.mof |
Not applicable |
4,460 |
05-Nov-2010 |
02:11 |
Not applicable |
Nfs-servercore-ppdlic.xrm-ms |
Not applicable |
3,001 |
06-May-2013 |
06:21 |
Not applicable |
Nfssvr.mof |
Not applicable |
6,195 |
05-Nov-2010 |
02:11 |
Not applicable |
Nfssvr.sys |
6.1.7601.18147 |
736,256 |
06-May-2013 |
03:17 |
x64 |
Msnfsflt.mof |
Not applicable |
4,460 |
05-Nov-2010 |
02:11 |
Not applicable |
Nfs-servercore-ppdlic.xrm-ms |
Not applicable |
3,001 |
06-May-2013 |
05:44 |
Not applicable |
Nfssvc.exe |
6.1.7601.22318 |
41,472 |
06-May-2013 |
03:01 |
x64 |
Nfssvr.mof |
Not applicable |
6,195 |
05-Nov-2010 |
02:11 |
Not applicable |
Nfssvr.sys |
6.1.7601.22318 |
737,280 |
06-May-2013 |
03:02 |
x64 |
For all supported IA-64-based versions of Windows Server 2008 R2
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Msnfsflt.mof |
Not applicable |
4,460 |
05-Nov-2010 |
02:11 |
Not applicable |
Nfs-servercore-ppdlic.xrm-ms |
Not applicable |
3,001 |
06-May-2013 |
04:55 |
Not applicable |
Nfssvr.mof |
Not applicable |
6,195 |
05-Nov-2010 |
02:11 |
Not applicable |
Nfssvr.sys |
6.1.7601.18147 |
1,591,296 |
06-May-2013 |
02:25 |
IA-64 |
Msnfsflt.mof |
Not applicable |
4,460 |
05-Nov-2010 |
02:11 |
Not applicable |
Nfs-servercore-ppdlic.xrm-ms |
Not applicable |
3,001 |
06-May-2013 |
04:46 |
Not applicable |
Nfssvc.exe |
6.1.7601.22318 |
90,624 |
06-May-2013 |
02:29 |
IA-64 |
Nfssvr.mof |
Not applicable |
6,195 |
05-Nov-2010 |
02:11 |
Not applicable |
Nfssvr.sys |
6.1.7601.22318 |
1,593,344 |
06-May-2013 |
02:30 |
IA-64 |
Windows Server 2012 file information notesImportant Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, milestone (RTM,SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.2.920 0.16 xxx
Windows Server 2012
RTM
GDR
6.2.920 0.20 xxx
Windows Server 2012
RTM
LDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Msnfsflt.sys |
6.2.9200.16453 |
32,256 |
08-Nov-2012 |
04:00 |
x64 |
Nfs-servercore-ppdlic.xrm-ms |
Not Applicable |
2,893 |
11-May-2013 |
09:15 |
Not Applicable |
Nfssvc.exe |
6.2.9200.16453 |
67,584 |
08-Nov-2012 |
04:22 |
x64 |
Nfssvr.mof |
Not Applicable |
6,233 |
06-Jul-2012 |
20:34 |
Not Applicable |
Nfssvr.sys |
6.2.9200.16610 |
1,249,792 |
11-May-2013 |
06:10 |
x64 |
Nfs-servercore-ppdlic.xrm-ms |
Not Applicable |
2,893 |
11-May-2013 |
09:19 |
Not Applicable |
Nfssvr.sys |
6.2.9200.20714 |
1,249,792 |
11-May-2013 |
06:26 |
x64 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
See Description of the standard terminology that is used to describe Microsoft software updates.
Additional file information for Windows Server 2008 R2
Additional files for all supported x64-based versions of Windows Server 2008 R2
File name |
Amd64_18c890acc496fc62c9501b032c476751_31bf3856ad364e35_6.1.7601.18147_none_8e067325ff11cf1d.manifest |
File version |
Not applicable |
File size |
706 |
Date (UTC) |
07-May-2013 |
Time (UTC) |
16:13 |
Platform |
Not applicable |
File name |
Amd64_ffe5b07b28994942dde0701ddc81c973_31bf3856ad364e35_6.1.7601.22318_none_94ed31fada6cc6df.manifest |
File version |
Not applicable |
File size |
706 |
Date (UTC) |
07-May-2013 |
Time (UTC) |
16:13 |
Platform |
Not applicable |
File name |
Amd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.1.7601.18147_none_b9ad209d1e01021c.manifest |
File version |
Not applicable |
File size |
41,883 |
Date (UTC) |
07-May-2013 |
Time (UTC) |
16:15 |
Platform |
Not applicable |
File name |
Amd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.1.7601.22318_none_ba582f5c37056491.manifest |
File version |
Not applicable |
File size |
41,883 |
Date (UTC) |
07-May-2013 |
Time (UTC) |
16:15 |
Platform |
Not applicable |
File name |
Update-bf.mum |
File version |
Not applicable |
File size |
1,655 |
Date (UTC) |
07-May-2013 |
Time (UTC) |
16:13 |
Platform |
Not applicable |
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File name |
Ia64_40ae35579ad92f787709ba59c40892b9_31bf3856ad364e35_6.1.7601.18147_none_97c46197d327fac4.manifest |
File version |
Not applicable |
File size |
704 |
Date (UTC) |
07-May-2013 |
Time (UTC) |
16:13 |
Platform |
Not applicable |
File name |
Ia64_df7b1328370ef9512543b247d3348aea_31bf3856ad364e35_6.1.7601.22318_none_01bd2aadcfca38bb.manifest |
File version |
Not applicable |
File size |
704 |
Date (UTC) |
07-May-2013 |
Time (UTC) |
16:13 |
Platform |
Not applicable |
File name |
Ia64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.1.7601.18147_none_5d90290f65a199e2.manifest |
File version |
Not applicable |
File size |
41,881 |
Date (UTC) |
07-May-2013 |
Time (UTC) |
16:13 |
Platform |
Not applicable |
File name |
Ia64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.1.7601.22318_none_5e3b37ce7ea5fc57.manifest |
File version |
Not applicable |
File size |
41,881 |
Date (UTC) |
07-May-2013 |
Time (UTC) |
16:13 |
Platform |
Not applicable |
File name |
Update-bf.mum |
File version |
Not applicable |
File size |
1,445 |
Date (UTC) |
07-May-2013 |
Time (UTC) |
16:13 |
Platform |
Not applicable |
Additional file information for Windows Server 2012
Additional files for all supported x64-based versions of Windows Server 2012
File name |
Amd64_3f31bffb95ff31878b4d587bf2b5a002_31bf3856ad364e35_6.2.9200.16610_none_be0b478ce33c03c2.manifest |
File version |
Not Applicable |
File size |
706 |
Date (UTC) |
11-May-2013 |
Time (UTC) |
19:18 |
Platform |
Not Applicable |
File name |
Amd64_c09dd585e2d93057c330e6c15dda2538_31bf3856ad364e35_6.2.9200.20714_none_aace85ff8c731f03.manifest |
File version |
Not Applicable |
File size |
706 |
Date (UTC) |
11-May-2013 |
Time (UTC) |
19:18 |
Platform |
Not Applicable |
File name |
Amd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.2.9200.16610_none_b4b603d690dab777.manifest |
File version |
Not Applicable |
File size |
38,339 |
Date (UTC) |
11-May-2013 |
Time (UTC) |
19:18 |
Platform |
Not Applicable |
File name |
Amd64_microsoft-windows-nfs-servercore_31bf3856ad364e35_6.2.9200.20714_none_b543a1c9a9f4bc9d.manifest |
File version |
Not Applicable |
File size |
38,339 |
Date (UTC) |
11-May-2013 |
Time (UTC) |
19:18 |
Platform |
Not Applicable |
File name |
Package_1_for_kb2846602_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum |
File version |
Not Applicable |
File size |
1,796 |
Date (UTC) |
11-May-2013 |
Time (UTC) |
19:18 |
Platform |
Not Applicable |
File name |
Package_1_for_kb2846602~31bf3856ad364e35~amd64~~6.2.1.0.mum |
File version |
Not Applicable |
File size |
2,509 |
Date (UTC) |
11-May-2013 |
Time (UTC) |
19:18 |
Platform |
Not Applicable |
File name |
Package_for_kb2846602_rtm_bf~31bf3856ad364e35~amd64~~6.2.1.0.mum |
File version |
Not Applicable |
File size |
1,451 |
Date (UTC) |
11-May-2013 |
Time (UTC) |
19:18 |
Platform |
Not Applicable |
File name |
Package_for_kb2846602_rtm~31bf3856ad364e35~amd64~~6.2.1.0.mum |
File version |
Not Applicable |
File size |
1,470 |
Date (UTC) |
11-May-2013 |
Time (UTC) |
19:18 |
Platform |
Not Applicable |
File name |
Update-bf.mum |
File version |
Not Applicable |
File size |
1,584 |
Date (UTC) |
11-May-2013 |
Time (UTC) |
19:18 |
Platform |
Not Applicable |
File name |
Update.mum |
File version |
Not Applicable |
File size |
1,609 |
Date (UTC) |
11-May-2013 |
Time (UTC) |
19:18 |
Platform |
Not Applicable |
References
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.