------- Comment From [email protected] 2018-02-22 11:02 EDT------- (In reply to comment #7) > Hi > in tests we regularly create iscsi targets and mount them so it generally > works. Thereby it is important how you exactly setup, create, pass and scan > them. Only then can your specific issue be (hopefully) reproduced so that > one can e.g. bisect on the changes to bisect on scripts/rescan-scsi-bus.sh > > So it would be great to have > 1. on Host to set up my iscsi disks I did ... > 2. to make them available to the guest I did ... > 3.1 then I resacn with ... but it fails like ... > 3.2 if I use the script from git it works like ... > > For 3.1 and 3.2 it might be useful to track kernel events (dmesg -w) and > udev ((sudo udevadm monitor) and providing those as log files for each of > the two cases (3.1 and 3.2).
Sure, I will try these out. I don't have a setup handy as of now, will do the steps again and provide the logs. ------- Comment From [email protected] 2018-02-22 11:04 EDT------- (In reply to comment #8) > > Let me know if you need any other details. > > Please provide full steps to reproduce this issue. Here are the steps to reproduce: 1. Create a volume on a iscsi target and map it to Ubuntu host. 2. Run rescan_iscsi_bus.sh script to identify that volume mounted on the host in form of the device and add it to multipath devices. 3. See the multipath available in "multipath -ll" output. The script couldn't identify the new device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750774 Title: Replace rescan_scsi_bus script with the latest one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1750774/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
