-
Notifications
You must be signed in to change notification settings - Fork 37
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
LUN discovery problem on 16/32Gb cards on linux client #128
Comments
Hi, Could you try Thanks, |
Hi Gleb, thanks for the answer, but it didn't help. The paths did not appear even 10 minutes after the reboot. Moreover, the state of the links was not defined as Online.
this is link state with
this is link state with
log with
|
@lnocturno is there anything interesting in the logs? maybe i can try something else? |
Sorry for the long response.
You can try the master branch with the latest qla2x00t-32gbit driver. You can also try
|
BUT, is it a bug or not, what works in the enabled mode but does not work in other modes? and will there be any problems when using this mode? |
I got the same issue with QLE2742, QLA2772 too. no problem for "enabled" mode but wait for few minutes for the LUNs to show up once uing "exclusive" or "dual" mode. |
Test using master branch, on Rocky Linux 8.8 (kernel 4.18.0-477.27.1.el8_8.x86_64) logs when using "dual" mode (similar for exclusive) |
more detail logs for "enabled" and "exclusive" mode (ql2xextended_error_logging=0x5e408000) |
Hi!
Ubuntu 18.04/20.04
Kernel 4.19.107/5.15
Scst 3.4.0/3.6.0/3.7.0
I have two cards in the system(let's call it client), one 8Gb works in target mode, the second 16/32Gb works in initiator mode
I connect LUN from storage and it shows up right after rescan on this client. if I do a client reboot, then after it loads the LUN appears after about 4-5 minutes. I want to note that I tried to build the Linux kernel with the default QLA driver, without scst, and this was not observed there, after the client loads, the LUN is immediately visible. We tried to use 8Gb cards as initiator and it worked well, the problem described as with 16/32 did not observed. I also tried to add a parameter, ql2xnvmeenable=0, it did not help
If you need anything else tell me.
driver loaded with parameters:
logs without debug mode(scst 3.4.0):
The text was updated successfully, but these errors were encountered: