-
Notifications
You must be signed in to change notification settings - Fork 66
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
Server reboot stucked due to unkillable mhvtl (SCSI Target: 15) #108
Comments
Thanks for the bug report. I'm on holidays without access to a computer for next 3 weeks. Looks like the kernel module oops, so when user space daemons call ioctl(), it never returns. daemons won't receive kill signal until the syscall() returns - hence are unkillable I'll look into it more when back from leave. Any chance for 'uname -r' as well |
|
A look over the kernel module src (kernel/mhvtl.c) line 331 show SCSI ID 15 assigned to the mhvtl hba. https://github.com/markh794/mhvtl/blob/master/kernel/mhvtl.c .this_id = 15 Try commenting out this line (leave unassigned) or set to a large value such as 4096 and recompile the kernel module. I'll try it out when back in front of a computer (in the next couple of weeks) |
Results in oops and hung user space daemon if a target is spun up using same SCSI ID as initiator. #108 Reported-by: https://github.com/smajl87 Signed-off-by: Mark Harvey <markh794@gmail.com>
Commit 4f36ea7 will fix this. |
Hi,
after configuring 2 libraries and multiple drives I rebooted server (after installing IBM lin_tape). All library/tape properly detected by OS. However since next reboot it gets stucked every time,w aiting for vtltape&vtllibrary processes to terminate (unless I do
reboot -f now
).I tried to bring up all vtltape/vtllibrary services up one by one, and then stop them one by one while watching logs (debug enabled in mhvtl.conf)
I saw tapes polling in
journalctl -f
until this occured:Not able to kill any of vtl* processes:
I tried to stop vtltape from 11..40 and also from 40..11 so identify the one with ID 38 to cause issues.
The offending tape drive is defined as follows:
After I changed target from 15 to 16, problem is gone
Current (working) state:
Q: What's wrong with TARGET:15?
QEMU VM running Ubuntu 20.04.5 LTS
The text was updated successfully, but these errors were encountered: