Peter

I reconfigured my system to have this for the add_library_contents_10 and the problem did not occur with the same test: add_library 10 0 0 0 "IBM" "3584" "2160" "XYZZY_A" #...

Earlier when we had a mix of LTO-6, LTO-7, and LTO-8 drives, we saw: [root@choctaw ITDT]# ./itdt scan Scanning SCSI Bus ... #0 /dev/sg5 - [ULT3580-TD7]-[0106] S/N:XYZZY_A4 H4-B0-T4-L0 (Generic-Device) #1...

Mark, thank you. Enjoy your time off. The problem occurred both times I ran a test, so it is repeatable. Each time I had to reboot to get the system...

I got the mhvtl volumes for mhvtl_lto-6_01 and mhvtl_lto-6_05 to come back by running the `udevadm trigger` command, but why do I need to do that? I found the following...

Hi, Mark. Yes, I ran the above and then saw the complete udev rules. I had these mhvtl volumes before running the above: ``` lrwxrwxrwx 1 root root 6 Jul...

Yeah, we use `udevadm trigger` to recreate the udev paths and I think that nearly always puts back the missing paths.. However, I think some time later additional paths might...

Hi, Mark. I updated four of our test systems to have `udev_log="debug"` in the `/etc/udev/udev.conf` file. However, I don't understand why I have to disable mhvtl.target. The next time I...

We are using RHEL 8 but this problem also happens on RHEL 7 machines.

> Even though udev is in debug, but it does not appear to make it to /var/log/messages The `journalctl -f` seems to be the only way to capture the info...

Hi, Mark. Any news on updating MHVTL to handle this situation? We are seeing a lot of debug messages related to this when we use IBM LTO-6 tape drives with...