Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Jul 2018 10:15:49 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 229958] ctld / zfs deadlock
Message-ID:  <bug-229958-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229958

            Bug ID: 229958
           Summary: ctld / zfs deadlock
           Product: Base System
           Version: 11.2-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: bugzilla.freebsd@omnilan.de

Hello,

'zfs rename poolA/iscsivolumeX poolA/iscsiVOLx' locks up the ZFS pool poolA=
, if
/dev/zvol/poolA/iscsivolumeX is used as target LUN path in ctld(8).

The machine is still operational and datasets from other pools are accessab=
le,
but no dataset of poolA.
Reboot doesn't succeed, machine hangs after "Syncing disks, vnodes remainin=
g...
1 1 1 0 0 ..... done"
"All buffers synced."
  HANG

I'm quiet sure the pool lockup wasn't an issue in FreeBSD 10, since I often
forgot to disable zvol ctld(8) backends before renaming the dataset.

Is this in any way related to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220175 ???

And perhaps my other big ctld(8) problem might be related too?
https://lists.freebsd.org/pipermail/freebsd-stable/2018-July/089268.html

Sorry for combining problem descriptions, but I'm observing severe iSCSI
regressions on all systems I updated to 11.2.  Unfortunately initiators were
updated too, so the root cause is not clear.

Thanks,

-harry

--=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-229958-227>