New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing SCSI device handler modules lead to suboptimal iSCSI modes of operation #2281

Closed
redbaron opened this Issue Dec 7, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@redbaron

redbaron commented Dec 7, 2017

Bug

multipathd cannot load expected SCSI device handlers and therefore operates in suboptimal mode. In my case ALUA configuration is unavailable when accessing SAN.

Container Linux Version

NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1576.3.0
VERSION_ID=1576.3.0
BUILD_ID=2017-11-30-1716
PRETTY_NAME="Container Linux by CoreOS 1576.3.0 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

Other Information

Shipped multipathd attempts to load modules:

   Loaded: loaded (/usr/lib/systemd/system/multipathd.service; disabled; vendor preset: disabled)
   Active: active (running) since Thu 2017-12-07 14:18:46 UTC; 23min ago
  Process: 7705 ExecStartPre=/sbin/modprobe -a scsi_dh_alua scsi_dh_emc scsi_dh_rdac dm-multipath (code=exited, status=1/FAILURE)
 Main PID: 7721 (multipathd)
   Status: "idle"
    Tasks: 7 (limit: 32768)
   Memory: 13.3M
      CPU: 369ms
   CGroup: /system.slice/multipathd.service
           └─7721 /sbin/multipathd -d -s

But kernel is compiled without them:

zcat  /proc/config.gz | grep SCSI_DH
CONFIG_SCSI_DH=y
# CONFIG_SCSI_DH_RDAC is not set
# CONFIG_SCSI_DH_HP_SW is not set
# CONFIG_SCSI_DH_EMC is not set
# CONFIG_SCSI_DH_ALUA is not set
@bgilbert

This comment has been minimized.

Show comment
Hide comment
@bgilbert

bgilbert Dec 19, 2017

Member

Should be fixed in alpha 1632.0.0, due shortly. Thanks for the report and PR!

Member

bgilbert commented Dec 19, 2017

Should be fixed in alpha 1632.0.0, due shortly. Thanks for the report and PR!

@bgilbert bgilbert closed this Dec 19, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment