On 03/06/2016 11:33 PM, Thijs Cramer wrote:
2016-03-06 18:25 GMT+01:00 Andy Grover <agrover@xxxxxxxxxx>:
On 03/06/2016 02:06 AM, Thijs Cramer wrote:
I've noticed some weird behaviour on the targetcli upon restarting.
For testing wirespeeds of different settings, i've created a ramdisk using
tmpfs in /mnt/ramdisk (mount -t tmpfs tmpfs /mnt/ramdisk).
After which i've created a "lun" (dd if=/dev/zero of=16G.ramdisk bs=16M
count=1024).
In targetcli i've added this file in backstores/fileio and added it as a
lun under several Fibre Channel ACL's and LUN's.
So far so good, and everything works fine. Until i reboot.
Which of course makes sense, because the ramdisk and thus the file are
gone.
But the weird thing is, the entire targetcli configuration is *empty*.
The expeceted behaviour here, would be that Targetcli unmaps the missing
LUN from the configuration, but leaves the rest of the configuration
intact. And not destroy my whole configuration.
Can anyone shed some light on this?
What kernel version and targetcli version? -- Andy
[fixed top-posting]
> Fedora 23 latest so: Kernel 4.4.3 & TargetCLI version 2.1.fb42-3.fc23.
Step one would be verify that target.service is enabled. This is needed
to restore settings on restart:
sudo systemctl enable target.service
sudo reboot
...still broken?
2) verify /etc/target/saveconfig.json looks ok
3) try 'targetctl clear' and 'targetctl restore' without rebooting to
see if that works, or any error messages produced
4) open a Fedora bug and attach saveconfig.json
Thanks -- Andy
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
