https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226295
Bug ID: 226295
Summary: [iscsi] LUN modification error: LUN X is not managed
by the block backend
Product: Base System
Version: 11.1-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: freebsd-bugs@FreeBSD.org
Reporter: e...@norma.perm.ru
Sometimes out of the vlue a "shadow LUN" appears, producing messages in logs
similar to "LUN modification error: LUN X is not managed by the block
backend".The lun mentioned is visible in the ctladm output abnd is stated to be
of a type "block". ctladm remove on it is successful but usully doesn't resolve
the problem. This usually happens on aproduction system with properly
configured targets.
The workaround is to issue ctladm remove -b block -l X statements, then comment
out all the targets that kernel complains about, issue killall -HUP ctld reload
until there will be no messages like that. Then uncomment all the targets back,
resume operations.
last time 4 targets were affected.
===Cut===
Mar 2 16:40:49 san01 ctld[560]: failed to modify lun
"iqn.2016-04.net.playkey.iscsi:gamestop-reference,lun,0", CTL lun 11
Mar 2 16:40:49 san01 ctld[560]: LUN modification warning: error opening
/dev/zvol/gamestop/worker02-ver11_662: 2
Mar 2 16:40:49 san01 ctld[560]: failed to reload configuration
Mar 2 16:41:41 san01 ctld[560]: LUN modification warning: error opening
/dev/zvol/gamestop/worker02-ver11_662: 2
Mar 2 16:49:24 san01 ctld[560]: LUN modification error: LUN 11 is not managed
by the block backend
Mar 2 16:49:24 san01 ctld[560]: failed to modify lun
"iqn.2016-04.net.playkey.iscsi:gamestop-reference,lun,0", CTL lun 11
Mar 2 16:49:24 san01 ctld[560]: failed to reload configuration
Mar 2 16:55:33 san01 ctld[560]: LUN modification error: LUN 11 is not managed
by the block backend
Mar 2 16:55:33 san01 ctld[560]: failed to modify lun
"iqn.2016-04.net.playkey.iscsi:gamestop-reference,lun,0", CTL lun 11
Mar 2 16:55:33 san01 ctld[560]: failed to reload configuration
Mar 2 16:57:34 san01 ctld[560]: LUN modification error: LUN 11 is not managed
by the block backend
Mar 2 16:57:34 san01 ctld[560]: failed to modify lun
"iqn.2016-04.net.playkey.iscsi:gamestop-reference,lun,0", CTL lun 11
Mar 2 16:57:34 san01 ctld[560]: failed to reload configuration
Mar 2 17:07:36 san01 ctld[560]: LUN modification error: LUN 11 is not managed
by the block backend
Mar 2 17:07:36 san01 ctld[560]: failed to modify lun
"iqn.2016-04.net.playkey.iscsi:gamestop-reference,lun,0", CTL lun 11
Mar 2 17:07:36 san01 ctld[560]: LUN modification error: LUN 11 is not managed
by the block backend
Mar 2 17:07:36 san01 ctld[560]: failed to modify lun
"iqn.2016-04.net.playkey.iscsi:games-worker01,lun,1", CTL lun 11
Mar 2 17:07:36 san01 ctld[560]: failed to reload configuration
Mar 2 17:09:03 san01 ctld[560]: LUN modification error: LUN 11 is not managed
by the block backend
Mar 2 17:09:03 san01 ctld[560]: failed to modify lun
"iqn.2016-04.net.playkey.iscsi:gamestop-reference,lun,0", CTL lun 11
Mar 2 17:09:03 san01 ctld[560]: LUN modification error: LUN 11 is not managed
by the block backend
Mar 2 17:09:03 san01 ctld[560]: failed to modify lun
"iqn.2016-04.net.playkey.iscsi:games-worker01,lun,1", CTL lun 11
Mar 2 17:09:03 san01 ctld[560]: LUN modification error: LUN 11 is not managed
by the block backend
Mar 2 17:09:03 san01 ctld[560]: failed to modify lun
"iqn.2016-04.net.playkey.iscsi:games-worker16,lun,1", CTL lun 11
Mar 2 17:09:04 san01 ctld[560]: failed to reload configuration
Mar 2 17:09:41 san01 ctld[560]: LUN modification error: LUN 11 is not managed
by the block backend
Mar 2 17:09:41 san01 ctld[560]: failed to modify lun
"iqn.2016-04.net.playkey.iscsi:gamestop-reference,lun,0", CTL lun 11
Mar 2 17:09:41 san01 ctld[560]: LUN modification error: LUN 11 is not managed
by the block backend
===Cut===
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
