Discussion:
[Bug 226295] [iscsi] LUN modification error: LUN X is not managed by the block backend
(too old to reply)
b***@freebsd.org
2022-04-18 18:32:51 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226295

Alan Somers <***@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #1 from Alan Somers <***@FreeBSD.org> ---
*** Bug 252425 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are the assignee for the bug.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
b***@freebsd.org
2022-04-18 19:14:54 UTC
Permalink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226295

--- Comment #2 from Alan Somers <***@FreeBSD.org> ---
I encountered the same problem in a build based on stable/13 from last
September. But in my case "ctladm remove" did not work; it failed with the
same error. And since there are only two backends to choose from, I tried "-b
ramdisk" as well, which failed with the same error again. There was also one
remaining iSCSI session, connected to the faulty LUN, but "ctladm isterminate
-a" had no effect. I could only resolve the problem by rebooting.

$ sudo ctladm remove -b block -l 133
ctladm: LUN removal error: LUN 133 is not managed by the block backend
--
You are receiving this mail because:
You are the assignee for the bug.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Loading...