Hi William, On Tue, 2017-03-07 at 10:48 -0500, William Thompson wrote: > Please keep me in CC, I am not subscribed. > > Sorry for the delay in replying. > > On Sun, Feb 19, 2017 at 10:23:53PM -0800, Nicholas A. Bellinger wrote: > > On Thu, 2017-02-16 at 07:30 -0500, William Thompson wrote: > > > Kernel is: > > > Linux it-iscsi 4.6.0-1-amd64 #1 SMP Debian 4.6.2-2 (2016-06-25) x86_64 GNU/Linux > > > > > > > Thanks for your bug-report. > > > > Using a v4.6.x kernel, I think there are two issues to consider. > > First, note v4.6.x is not a long term stable kernel, so it's missing a > > number of regression bug-fixes from the past year that you'll likely > > encounter against ESX hosts with VAAI enabled. > > > > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/target?h=linux-4.4.y&id=60ba156dda2c11ff7a44d78ec64abd21b9813115 > > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/target?h=linux-4.4.y&id=f318588b758514c35f0a9227195178a3b2b4b733 > > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/target?h=linux-4.4.y&id=56661d2b89b2a549be04f37dcf824c39d7aca9c6 > > Debian kernel, I just upgraded to 4.9.x Great. To confirm, which v4.9.x kernel are you using..? > > > These three are the minimum patches to v4.6.y that you'll need. > > However, considering v4.6.y is not a long-term stable kernel, I'd very > > much recommend instead you use the latest v4.1.y, v4.4.y or anything >= > > v4.8.y in order to get the full set of bug-fixes from upstream. > > > > Second, there is a well known ESX 5.5u2+ bug with VMFS5 that is > > triggered by targets that support VAAI AtomicTestandSet (emulate_caw=1 > > in LIO backend attribute speak). > > > > https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2113956 > > http://cormachogan.com/2015/04/17/heads-up-ats-miscompare-detected-between-test-and-set-hb-images/ > > http://www.thevirtualist.org/alert-application-outages-using-vaai-ats-on-vsphere-5-5-update2-vsphere-6-0/ > > https://www-304.ibm.com/support/docview.wss?uid=ssg1S1005201 > > http://h20565.www2.hpe.com/hpsc/doc/public/display?sp4ts.oid=75953&docId=mmr_sf-EN_US000005979&lang=en-us&cc=us&docLocale=en_US > > > > The result is that data stores will eventually go offline, if the ATS > > heartbeat logic for VMFS5 is not explicitly disabled on all ESX hosts. > > There have many, many users who have hit this, and based on the > > recommendation of all the other vendors above, it's a must disable in > > order to get a stable working ESX 5.5u2+ + VAAI setup. > > If it keeps up with 4.9.x, I'll take a look at this. > Just a heads up. The second issue mentioned here is *not* a LIO target issue, but a well-known ESX host side issue that requires users to manually disable ATS heartbeat on all your ESX hosts using VAAI. Note this is required in order to get a stable setup. The ESX side instructions for doing this are: # esxcli system settings advanced set -i 0 -o /VMFS3/UseATSForHBOnVMFS5 # esxcli system settings advanced list -o /VMFS3/UseATSForHBonVMFS5 Path: /VMFS3/UseATSForHBOnVMFS5 Type: integer Int Value: 0 Default Int Value: 1 Min Value: 0 Max Value: 1 String Value: Default String Value: Valid Characters: Description: Use ATS for HB on ATS supported VMFS5 volumes -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
