linenoise Posted June 17, 2015 Share #1 Posted June 17, 2015 I built a new xpenology server last night using XPEnoboot 5.2-5565.2 and the 5.2 pat (Then, I updated to current release via DSM) HW is a HP Proliant ML 10. Installed without issue. Everything seemed to work fine. Installed NFS VAAI plugin via vib onto esxi 6 (works without issue on old virtualized xpenolgy system. Clone & vMotion fail with "Error caused by file. /vmfs/volumes/xxxxxxxx/" I was able to manually copy the files using datastore browser without issue (so I do not assume a permissions issue.) I can create new Virtual Machines. I uninstalled the NFS VAAI Vib, rebooted and tested no issue performing vMotion or clone. Anyone have simular experence. Thoughts? Ideas? etc. Thanks, Quote Link to comment Share on other sites More sharing options...
benok Posted June 29, 2015 Share #2 Posted June 29, 2015 Recently, I've setup 2 new xpenology servers with xpenoboot 5.2-5565.2. One is bare metal, and the other is virtual one on esxi. Everything works fine, but NFS VAAI doesn't work. I'm new to NFS datastore with VAAI. (I used iSCSI before.) I tried to install with a similar procedure like the page below. (but I give vib's url to esxcli directly.) Install Synology NFS VAAI Plug-in for VMware - Mike Tabor https://miketabor.com/synology-nfs-vaai-plugin/ After reboot, I confirmed but doesn't seems to work on both cases below. (it says "Not Supported".) case1: esxi5.1 & baremetal5.2 ~ # esxcli software vib list | grep -i syno esx-nfsplugin 1.0-1 Synology VMwareAccepted 2015-06-28 ~ # esxcli storage nfs list Volume Name Host Share Accessible Mounted Read-Only Hardware Acceleration ----------- ---------- ------------------ ---------- ------- --------- --------------------- ds1-nfs 10.24.100.1 /volume1/datastore true true false Not Supported case2: esxi6 & virtual5.2 [root@esxi3:~] esxcli software vib list | grep -i syno esx-nfsplugin 1.0-1 Synology VMwareAccepted 2015-06-26 [root@esxi3:~] esxcli storage nfs list Volume Name Host Share Accessible Mounted Read-Only isPE Hardware Acceleration ----------- -------------- ------------------- ---------- ------- --------- ----- --------------------- datastore1 10.21.100.1 /volume2/datastore1 true true false false Not Supported ssd128x2 10.21.100.1 /volume3/ssd128x2 true true false false Not Supported So I googled with 'xpenology vaai nfs' and found your post on top. I found NFS datastore is very convenient, and especially is if VAAI works, but it seems to be broken, at the moment. Any suggestions ? Quote Link to comment Share on other sites More sharing options...
benok Posted June 29, 2015 Share #3 Posted June 29, 2015 Found errors on hostd.log. hostd.log:2015-06-26T13:23:54.512Z info hostd[4CA80B70] [Originator@6876 sub=Libs] SynologyNasPlugin: session request for 10.21.100.1 /volume2/datastore1 /vmfs/volumes/809a7328-3a50ea07 NFS 1 hostd.log:2015-06-26T13:23:54.513Z info hostd[4CA80B70] [Originator@6876 sub=Libs] SynologyNasPlugin: mounted /volume2/datastore1 on host 172.21.200.241 hostd.log:2015-06-26T13:23:54.513Z info hostd[4CA80B70] [Originator@6876 sub=Libs] SynologyNasPlugin: Checking support status hostd.log:2015-06-26T13:23:54.513Z info hostd[4CA80B70] [Originator@6876 sub=Libs] SynologyNasPlugin: Remote machine does not support hardware offload hostd.log:2015-06-26T13:23:54.513Z info hostd[4CA80B70] [Originator@6876 sub=Libs] SynologyNasPlugin: Checking support status hostd.log:2015-06-26T13:23:54.513Z info hostd[4CA80B70] [Originator@6876 sub=Libs] SynologyNasPlugin: Remote machine does not support hardware offload hostd.log:2015-06-26T13:23:54.513Z info hostd[4CA80B70] [Originator@6876 sub=Libs] SynologyNasPlugin: Checking support status hostd.log:2015-06-26T13:23:54.513Z info hostd[4CA80B70] [Originator@6876 sub=Libs] SynologyNasPlugin: Remote machine does not support hardware offload Perhaps, we have to dump packets with wireshark and compare conversations with works version (XPenology 5.1 ?). But anyway, could you check the modules behind NFS & VAAI, please ? > Core dev team Can we solve this problem like iSCSI one ? Quote Link to comment Share on other sites More sharing options...
benok Posted June 29, 2015 Share #4 Posted June 29, 2015 I confirmed DSM5.1-5055 works from my esxi6 host. Perhaps, it's a problem of 5.2 confirmed nfs share from 5.1 is VAAI supported (last one) [root@sd-esxi3:/var/log] esxcli storage nfs list Volume Name Host Share Accessible Mounted Read-Only isPE Hardware Acceleration ----------- -------------- ------------------- ---------- ------- --------- ----- --------------------- datastore1 10.21.100.1 /volume2/datastore1 true true false false Not Supported ssd128x2 10.21.100.1 /volume3/ssd128x2 true true false false Not Supported nfs-test 10.21.0.22 /volume2/iso true true false false Supported success access log from hostd.log 2015-06-29T09:20:28.867Z info hostd[43281B70] [Originator@6876 sub=Libs] SynologyNasPlugin: session request for 10.21.0.22 /volume2/iso /vmfs/volumes/bc0a7e1c-9d181d3b NFS 1 2015-06-29T09:20:28.870Z info hostd[43281B70] [Originator@6876 sub=Libs] SynologyNasPlugin: mounted /volume2/iso on host 10.21.0.22 2015-06-29T09:20:28.870Z info hostd[43281B70] [Originator@6876 sub=Libs] SynologyNasPlugin: Checking support status 2015-06-29T09:20:28.871Z info hostd[43281B70] [Originator@6876 sub=Libs] SynologyNasPlugin: Checking support status 2015-06-29T09:20:28.871Z info hostd[43281B70] [Originator@6876 sub=Libs] SynologyNasPlugin: Checking support status 2015-06-29T09:20:28.875Z info hostd[43281B70] [Originator@6876 sub=Libs] SynologyNasPlugin: session request for 10.21.0.22 /volume2/iso /vmfs/volumes/bc0a7e1c-9d181d3b NFS 1 2015-06-29T09:20:28.878Z info hostd[43281B70] [Originator@6876 sub=Libs] SynologyNasPlugin: mounted /volume2/iso on host 10.21.0.22 2015-06-29T09:20:28.878Z info hostd[43281B70] [Originator@6876 sub=Libs] SynologyNasPlugin: Checking support status 2015-06-29T09:20:28.878Z info hostd[43281B70] [Originator@6876 sub=Libs] SynologyNasPlugin: Checking support status 2015-06-29T09:20:28.878Z info hostd[43281B70] [Originator@6876 sub=Libs] SynologyNasPlugin: Checking support status Quote Link to comment Share on other sites More sharing options...
AMizil Posted July 4, 2015 Share #5 Posted July 4, 2015 Benok, Are u using VMware vSphere 6.0 ( full version of the hypervisor) or the free version of ESXi 6.0 ? Regards, Adrian Quote Link to comment Share on other sites More sharing options...
fafner Posted July 6, 2015 Share #6 Posted July 6, 2015 I can confirm it's broken in XPEnoboot 5.2-5565.2 with vSphere 5.5. Quote Link to comment Share on other sites More sharing options...
Majinbelail Posted July 6, 2015 Share #7 Posted July 6, 2015 I can also confirm it's broken. vSphere 5.5. Quote Link to comment Share on other sites More sharing options...
benok Posted July 7, 2015 Share #8 Posted July 7, 2015 Benok, Are u using VMware vSphere 6.0 ( full version of the hypervisor) or the free version of ESXi 6.0 ? Adrian vSphere5.1 & ESXi6.0. (also checked direct connection to ESXi5.1 from C# client.) Quote Link to comment Share on other sites More sharing options...
vemey Posted July 7, 2015 Share #9 Posted July 7, 2015 Hi, to me it looks more as an issue with XPE than a Synology Problem with DSM 5.2 and ESXI 6.0. As you can see the NFS connection with my DS415+ (DSM 5.2-5592) is using hardware acc. vs my DS3615 (XPE on DSM 5.2-5565 Update 2) is not. - esxcli software vib list | grep -i syno esx-nfsplugin 1.0-1 Synology VMwareAccepted 2015-06-21 - esxcli storage nfs list Volume Name Host Share Accessible Mounted Read-Only isPE Hardware Acceleration ----------- ------------- ------------ ---------- ------- --------- ----- --------------------- ISO DS415 192.168.42.54 /volume1/iso true true true false Supported VM DS415 192.168.42.54 /volume2/vm true true false false Supported VM DS3615 192.168.42.52 /volume2/vm true true false false Not Supported Quote Link to comment Share on other sites More sharing options...
vemey Posted July 7, 2015 Share #10 Posted July 7, 2015 Hi, to me it looks more as an issue with XPE than a Synology Problem with DSM 5.2 and ESXI 6.0. As you can see the NFS connection with my DS415+ (DSM 5.2-5592) is using hardware acc. vs my DS3615 (XPE on DSM 5.2-5565 Update 2) is not. - esxcli software vib list | grep -i syno esx-nfsplugin 1.0-1 Synology VMwareAccepted 2015-06-21 - esxcli storage nfs list Volume Name Host Share Accessible Mounted Read-Only isPE Hardware Acceleration ----------- ------------- ------------ ---------- ------- --------- ----- --------------------- ISO DS415 192.168.42.54 /volume1/iso true true true false Supported VM DS415 192.168.42.54 /volume2/vm true true false false Supported VM DS3615 192.168.42.52 /volume2/vm true true false false Not Supported Quote Link to comment Share on other sites More sharing options...
benok Posted July 8, 2015 Share #11 Posted July 8, 2015 Hi, to me it looks more as an issue with XPE than a Synology Problem with DSM 5.2 and ESXI 6.0. As you can see the NFS connection with my DS415+ (DSM 5.2-5592) is using hardware acc. vs my DS3615 (XPE on DSM 5.2-5565 Update 2) is not. You think DSM 5.2-5565 has problem, but 5592 doesn't, right ? But it is not related on release note of 5592. If your DS415+ version were 5.2-5565, and your plugin status is "Not supported", we can hope it will be fixed on 5592. Quote Link to comment Share on other sites More sharing options...
fafner Posted July 8, 2015 Share #12 Posted July 8, 2015 Hi, to me it looks more as an issue with XPE than a Synology Problem with DSM 5.2 and ESXI 6.0. As you can see the NFS connection with my DS415+ (DSM 5.2-5592) is using hardware acc. vs my DS3615 (XPE on DSM 5.2-5565 Update 2) is not. You think DSM 5.2-5565 has problem, but 5592 doesn't, right ? No. XPEnology is broken. It's not a matter of DSM. I have 5592 on a DS412+ and there it's working. Quote Link to comment Share on other sites More sharing options...
Majinbelail Posted July 8, 2015 Share #13 Posted July 8, 2015 Hi, to me it looks more as an issue with XPE than a Synology Problem with DSM 5.2 and ESXI 6.0. As you can see the NFS connection with my DS415+ (DSM 5.2-5592) is using hardware acc. vs my DS3615 (XPE on DSM 5.2-5565 Update 2) is not. You think DSM 5.2-5565 has problem, but 5592 doesn't, right ? No. XPEnology is broken. It's not a matter of DSM. I have 5592 on a DS412+ and there it's working. The problem is you are testing with 2 different versions. You have for the HW the actual version and for XPEnology only the 5565 U2. If it's possible test the DS415+/DS412+ with 5.2-5565 Update 2 and see if there is also no problem. Quote Link to comment Share on other sites More sharing options...
Majinbelail Posted July 8, 2015 Share #14 Posted July 8, 2015 Hi, to me it looks more as an issue with XPE than a Synology Problem with DSM 5.2 and ESXI 6.0. As you can see the NFS connection with my DS415+ (DSM 5.2-5592) is using hardware acc. vs my DS3615 (XPE on DSM 5.2-5565 Update 2) is not. You think DSM 5.2-5565 has problem, but 5592 doesn't, right ? No. XPEnology is broken. It's not a matter of DSM. I have 5592 on a DS412+ and there it's working. The problem is you are testing with 2 different versions. You have for the HW the actual version and for XPEnology only 5.2-5565 Update 2. If it's possible test the DS415+/DS412+ with 5.2-5565 Update 2 and see if there is also no problem. So you can't say with 100% accuracy that XPEnology is broken. It's only an assumption. Quote Link to comment Share on other sites More sharing options...
fafner Posted July 9, 2015 Share #15 Posted July 9, 2015 The problem is you are testing with 2 different versions. You have for the HW the actual version and for XPEnology only 5.2-5565 Update 2. If it's possible test the DS415+/DS412+ with 5.2-5565 Update 2 and see if there is also no problem. So you can't say with 100% accuracy that XPEnology is broken. It's only an assumption. I've been running the DS412+ for month with NFS-VAAI including 5562U2 before 5592 and it was working all the time. So I am sure XPEnology is broken here. Quote Link to comment Share on other sites More sharing options...
benok Posted July 13, 2015 Share #16 Posted July 13, 2015 I've been running the DS412+ for month with NFS-VAAI including 5562U2 before 5592 and it was working all the time. So I am sure XPEnology is broken here. Thank you for your info. So, we confirmed that XPEnology 5.2's NFS VAAI support is broken. I hope dev team to take care of this problem. Quote Link to comment Share on other sites More sharing options...
willrun4fun Posted July 13, 2015 Share #17 Posted July 13, 2015 I ran into this trying to copy a vmotion a vm back from my NFS attached xpenology back to a local datastore. Has this been submitted as a bug officially then? I am going to move to ISCSI and give that a shot for the time being. Quote Link to comment Share on other sites More sharing options...
fafner Posted July 13, 2015 Share #18 Posted July 13, 2015 I am going to move to ISCSI and give that a shot for the time being.iSCSI seems to work here so far... Quote Link to comment Share on other sites More sharing options...
linenoise Posted July 30, 2015 Author Share #19 Posted July 30, 2015 updated to 5.2-5592 and tested VAAI with NFS. Still not working. Quote Link to comment Share on other sites More sharing options...
fafner Posted July 31, 2015 Share #20 Posted July 31, 2015 Not surprised. Probably no one is working on this. Sticking with iSCSI so far. Quote Link to comment Share on other sites More sharing options...
b0fh Posted August 4, 2015 Share #21 Posted August 4, 2015 Has there been any update on this? I am ready to upgrade my servers but I don't want to lose this functionality or switch to iSCSI at this time. Also, I am using fully up to date esxi 5.5, does moving to ESXi 6.0 change anything for those who have already upgraded ESXi? Does the existing plugin work in 6.0 if you don't update to current xpenology builds? Quote Link to comment Share on other sites More sharing options...
b0fh Posted August 6, 2015 Share #22 Posted August 6, 2015 Bump - anyone? Quote Link to comment Share on other sites More sharing options...
b0fh Posted August 7, 2015 Share #23 Posted August 7, 2015 Okay, I jumped to 5592-update 2 with my ISO server and it is no longer reporting acceleration, so it is still broken. I will hold back my vm storage until this is fixed or until I give up and move to iSCSI. Quote Link to comment Share on other sites More sharing options...
b0fh Posted August 20, 2015 Share #24 Posted August 20, 2015 Anyone looking at this at all? Any ideas why it appears to be broken? Quote Link to comment Share on other sites More sharing options...
benok Posted August 21, 2015 Share #25 Posted August 21, 2015 I think not only VAAI but NFS itself is unstable on 5.2. I tried NFS datastore without VAAI, it looks not so bad, but with heavy load (direct CIFS copy from local Win10 VM's USB3 harddrive (via passthroughed USB3I/F & VMXNet3), esxi got lost vm temporally, because of NFS mount error.(see vmkernel.log below) 2015-08-21T12:12:19.148Z cpu2:33147)WARNING: NFS: 221: Got error 13 from mount call 2015-08-21T12:12:50.536Z cpu6:33822)Config: 679: "SIOControlFlag1" = 33822, Old Value: 0, (Status: 0x0) 2015-08-21T12:12:51.144Z cpu2:36774)WARNING: NFS: 221: Got error 13 from mount call 2015-08-21T12:13:28.314Z cpu2:51281)FSS: 6146: Failed to open file '************.vmdk'; Requested flags 0x4001, world: 51281 [sdrsInjector], (Existing flags 0x4008, world: 36793 [vmx]): Busy 2015-08-21T12:13:28.316Z cpu2:51281)FSS: 6146: Failed to open file '************.vswp'; Requested flags 0x4001, world: 51281 [sdrsInjector], (Existing flags 0x8, world: 36793 [vmx]): Busy 2015-08-21T12:13:28.378Z cpu2:51281)FSS: 6146: Failed to open file '*****.vmdk'; Requested flags 0x4001, world: 51281 [sdrsInjector], (Existing flags 0x4008, world: 36773 [vmx]): Busy 2015-08-21T12:13:28.382Z cpu2:51281)FSS: 6146: Failed to open file '*****-2375d83f.vswp'; Requested flags 0x4001, world: 51281 [sdrsInjector], (Existing flags 0x8, world: 36773 [vmx]): Busy 2015-08-21T12:13:31.044Z cpu3:51281)FSS: 6146: Failed to open file '*****-000002-delta.vmdk'; Requested flags 0x4001, world: 51281 [sdrsInjector], (Existing flags 0x4008, world: 37725 [vmx]): Busy 2015-08-21T12:13:31.076Z cpu3:51281)FSS: 6146: Failed to open file '*******-1885038055-1.vswp'; Requested flags 0x4001, world: 51281 [sdrsInjector], (Existing flags 0x8, world: 34668 [hostd-worker]): Busy I also may have to choose iSCSI again... p.s. I finally got success working SSD cache on 5.2. (with 5.1, VM hang up with esxi without PSOD.) I'll post about that later on SSD cache thread. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.