vSphere 5.5U1和NFS断开连接

Shuguet
UserLevel 4
徽章 +20
你好，

它昨天发布了新闻，但是如果您错过了它，VSPhere 5.5U1中似乎有一个错误影响所有NFS用户。

NetApp＆Vmware（至少也许也许还有Nutanix？）正在研究该主题。

有关更多信息，请参见下面的帖子：
http://datacenterdude.com/vmware/nfs-disconnects-vmware-vsphere/

这也可能解释了Nutanix在支持5.5U1的支持下的延迟？
你们在不工作的5.5U1支持时抓住了这一点吗？

西尔万。
Sylvain Huguet -2X Nutanix技术冠军2015-2016，法国Nutanix Connect Chapter Champion，法国VMUG首领，6倍VMware Vexpert 2011至2016
    \n
    \nIt's made the news yesterday, but in case you missed it, there seems to be a bug within vSphere 5.5U1 that affects all NFS users.
    \n
    \nNetApp & VMware (at least, maybe Nutanix too?) are working on the subject.
    \n
    \nSee the post below for more information:
    \nhttp:\/\/datacenterdude.com\/vmware\/nfs-disconnects-vmware-vsphere\/
    \n
    \nThat may also explain the delay from Nutanix in the support of the 5.5U1?
    \nDid you guys catch this while working no the 5.5U1 support?
    \n
    \nSylvain.","quoteUsername":"shuguet","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    该主题已关闭以供评论

    4个答复

    nutanix_support
    秩
    徽章 +3
    ESXI 5.5 U1 NFS数据存储断开问题都在内部和我们的客户中发生。昨天，现场咨询＃17已发送给我们的客户，建议他们推迟到ESXI 5.5的任何升级。U1。
    nutanix_support
    秩
    徽章 +3
    看起来VMware刚刚在此问题上发布了KB-2076392。

    将ESXI升级为5.5 U1（2076392）后，经常使用NFS APD
    运行ESXI 5.5更新1的症状swhen宿主经常观察到与NFS存储的连接性，而APD与NFS量失去了连通性。您会遇到这些症状：
    • 报告了NFS数据存储的间歇性APD，因此在Linux虚拟机中为Windows Virtual Machine guests和只读文件系统带来了潜在的蓝屏错误。笔记：NFS卷包括VSA数据存储。
    • 在APD条件的持续时间内，此后，该数组仍然对PING和NETCAT测试响应，也没有证据表明物理网络或NFS存储阵列问题。
    • NFS存储阵列日志和痕迹也没有表示任何明显的问题，其他主机未运行ESXI 5.5 U1继续工作，可以读取并写入NFS共享而无需任何问题。
    • 您在VOBD日志中看到条目类似：笔记：这些日志输入使用12345678-abcdefg0卷作为示例：2014-04-04-01T14：35：08.074Z：[apdcorrelator] 9413898746us：[vob.storage.storage.apd.start.] with Device or Device or Device或FilesSef with Identifier [123456456788-ABCCDGGG0]进入状态的所有路径。2014-04-01T14：35：08.075Z：[apdcorrelator] 9414268686us：[esx.problem.storage.storage.apd.start.start]设备或filesystem带有标识符[123445678-abcdefg0]已输入的。State.2014-04-01T14：36：55.274Z：vob.vmfs.nfs.nfs.server.disconnect2014-04-04-014：36：55.274Z：[vmfscorrelator] 9521467867US：[ESX.PRO.VMF.VMF.SSSSESSSSESSSSSSSESSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS..disconnect] 192.168.1.1/NFS-DS1 12345678-ABCDEFG0-0000-0000-000000000000 NFS-DS12014-04-04-01T14：37：37：28.081Z：[28.081Z：[apdcorrelator] 9553899639639US：[VOB.STRITIES] [VOB.STRITE]12345678-ABCDEFG0]在处于全路状态140秒之后，已进入所有路径停止状态。I/OS现在将快速失败。2014-04-01T14：37：28.081Z：[apdcorrelator] 95542752221us：[esx.problem.storage.storage.apd.timeout]设备或filesystem and pefileystem带有标识符[123445678-abcdefg0]已输入路径在全路状态下处于140秒状态后的路径暂停状态。I/OS现在将快速失败。
    解决方案这是一个已知的问题，影响了ESXI 5.5更新1个带有连接的NFS存储的主机。VMware正在努力为客户提供解决方案。要解决此问题，VMware建议使用ESXI 5.5 GA。
    \n
    \nFrequent NFS APDs after upgrading ESXi to 5.5 U1 (2076392)
    \nSymptomsWhen running ESXi 5.5 Update 1, the ESXi host frequently loses connectivity to NFS storage and APDs to NFS volumes are observed. You experience these symptoms:
    \n
      \n
    • Intermittent APDs for NFS datastores are reported, with consequent potential blue screen errors for Windows virtual machine guests and read-only filesystems in Linux virtual machines.Note<\/b>: NFS volumes include VSA datastores. \n
    • For the duration of the APD condition and after, the array still responds to ping and netcat tests are also successful, and there is no evidence to indicate a physical network or a NFS storage array issue. \n
    • The NFS storage array logs and traces also do not indicate any evident issue, other hosts not running ESXi 5.5 U1 continue to work and can read and write to the NFS share without issue. \n
    • You see entries in the vobd logs similar to:Note<\/b>: These log entries use the 12345678-abcdefg0 volume as an example:2014-04-01T14:35:08.074Z: [APDCorrelator] 9413898746us: [vob.storage.apd.start] Device or filesystem with identifier [12345678-abcdefg0] has entered the All Paths Down state.2014-04-01T14:35:08.075Z: [APDCorrelator] 9414268686us: [esx.problem.storage.apd.start] Device or filesystem with identifier [12345678-abcdefg0] has entered the All Paths Down state.2014-04-01T14:36:55.274Z: No correlator for vob.vmfs.nfs.server.disconnect2014-04-01T14:36:55.274Z: [vmfsCorrelator] 9521467867us: [esx.problem.vmfs.nfs.server.disconnect] 192.168.1.1\/NFS-DS1 12345678-abcdefg0-0000-000000000000 NFS-DS12014-04-01T14:37:28.081Z: [APDCorrelator] 9553899639us: [vob.storage.apd.timeout] Device or filesystem with identifier [12345678-abcdefg0] has entered the All Paths Down Timeout state after being in the All Paths Down state for 140 seconds. I\/Os will now be fast failed.2014-04-01T14:37:28.081Z: [APDCorrelator] 9554275221us: [esx.problem.storage.apd.timeout] Device or filesystem with identifier [12345678-abcdefg0] has entered the All Paths Down Timeout state after being in the All Paths Down state for 140 seconds. I\/Os will now be fast failed.<\/ul>ResolutionThis is a known issue affecting ESXi 5.5 Update 1 hosts with connected NFS storage. VMware is working towards providing a resolution to customers.To work around this issue, VMware recommends using ESXi 5.5 GA.","quoteUsername":"nutanix_support","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    Shuguet
    UserLevel 4
    徽章 +20
    谢谢，非常清楚。

    太糟糕了，我们要在下个月开始测试5.5U1以大规模推出，猜猜我们必须等待...

    西尔万。
    Sylvain Huguet -2X Nutanix技术冠军2015-2016，法国Nutanix Connect Chapter Champion，法国VMUG首领，6倍VMware Vexpert 2011至2016
    \n
    \nToo bad, we were to test the 5.5U1 just next week to rollout massively starting next month, guess we'll have to wait...
    \n
    \nSylvain.","quoteUsername":"shuguet","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
    j
    徽章 +5
    当然，您已经知道了，但是如果有人看到这个线程并且不知道，VMware本周发布了5.5U1的补丁。我相信Nutanix正在内部测试它。我们热切等待结果
    条款和条件
    Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
    Functional","cookiepolicy.modal.level2":"Normal
    Functional + analytics","cookiepolicy.modal.level3":"Complete
    Functional + analytics + social media + embedded videos"}}}">
    Baidu