Hi all, 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? -- 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
