From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 112241] Under heavy load FC TARGET going to Oops
Date: Tue, 01 Mar 2016 05:16:10 +0000 [thread overview]
Message-ID: <bug-112241-11613-1OvpsUMp0v@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-112241-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=112241
--- Comment #3 from nab <nab@linux-iscsi.org> ---
Hi Anthony,
On Mon, 2016-02-29 at 02:26 +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=112241
>
> Anthony <anthony.bloodoff@gmail.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Kernel Version|4.3.3 |4.5.0
>
> --- Comment #2 from Anthony <anthony.bloodoff@gmail.com> ---
> With kernel 4.5.0 on target, system hang after clients connects to target.
>
So there are two things going on here.
First, the BUG_ON your ESX <-> LIO FC setup triggered has been addressed
recently in v4.5-rc4 and later kernels with the following series:
http://www.spinics.net/lists/target-devel/msg11822.html
Note these patches will be making it back to earlier stable kernels over
the next weeks.
However, this specific bug is a final consequence of larger ESX v5.5u2+
host side issue of AtomicTestandSet (ATS) heartbeat being enabled (by
default) for all VMFS5 mounts:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2113956
Other folks have been hitting this recently, here's some extra
background:
http://permalink.gmane.org/gmane.linux.scsi.target.devel/11574
http://www.spinics.net/lists/target-devel/msg12124.html
Note this effects all targets w/ VAAI ATS (including EMC, IBM, 3PAR,
SolidFire, etc) and the current solution for ESX v5.5u2+ is to either:
- Explicitly disable ATS heartbeat usage on all VMFS5 mounts as
described in the VMWare -kb article, or:
- Explicitly disable all ATS logic completely from LIO using
emulate_caw=0 on all backends connected to ESX v5.5u2+ hosts
with VMFS5.
You can google for 'esx ats heartbeat bug' to see the gory details.
Thanks for reporting!
--nab
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2016-03-01 5:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 7:32 [Bug 112241] New: Under heavy load FC TARGET going to Oops bugzilla-daemon
2016-02-29 2:24 ` [Bug 112241] " bugzilla-daemon
2016-02-29 2:26 ` bugzilla-daemon
2016-03-01 5:16 ` Nicholas A. Bellinger
2016-03-01 5:16 ` bugzilla-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-112241-11613-1OvpsUMp0v@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).