Date: Sun, 01 Jul 2018 16:18:19 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: =?UTF-8?B?W0J1ZyAyMjk0NTRdIFN5c3RlbSBlbmFibGVkIGZvciBGQyB0YXJn?= =?UTF-8?B?ZXQgbW9kZSB1c2luZyBRTE9HSUMgSEJBIHBhbmljcyB3aXRoIOKAnGZhdWx0?= =?UTF-8?B?IGNvZGUgPSBzdXBlcnZpc29yIHdyaXRlIGRhdGEsIHBhZ2Ugbm90IHByZXNl?= =?UTF-8?B?bnQgLSBGYXRhbCB0cmFwIDEyOiBwYWdlIGZhdWx0IHdoaWxlIGluIGtlcm5l?= =?UTF-8?B?bCBtb2Rl4oCd?= Message-ID: <bug-229454-227-gTeunpQGSd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229454-227@https.bugs.freebsd.org/bugzilla/> References: <bug-229454-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229454 --- Comment #1 from Setsquare <setsquare@gmail.com> --- In Addition to the above sometimes I have also noticed that the FC target L= UNs show as dead from the initiator but the FreeBSD server has not panic'd. The= re doesn't seem to be anything I can do on the FreeBSD FC target to bring them back up. Only option I have had is to restart the FreeBSD server. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229454-227-gTeunpQGSd>