Hello, I try to reproduce a bug in VMware ESX using Linux target. My setup is the following: /> ls o- / ......................................................................................................................... [...] o- backstores .............................................................................................................. [...] | o- block .................................................................................................. [Storage Objects: 0] | o- fileio ................................................................................................. [Storage Objects: 1] | | o- shared-01.v102.tuvl.de .................................... [/iscsi1/shared-01.v102.tuvl.de (0 bytes) write-back activated] | o- pscsi .................................................................................................. [Storage Objects: 0] | o- ramdisk ................................................................................................ [Storage Objects: 0] o- iscsi ............................................................................................................ [Targets: 1] | o- iqn.2013-03.de.tuvl.v102.storage:shared-01.v102.tuvl.de ........................................................... [TPGs: 2] | o- tpg1 .................................................................................................. [gen-acls, no-auth] | | o- acls .......................................................................................................... [ACLs: 0] | | o- luns .......................................................................................................... [LUNs: 1] | | | o- lun10 ................................................ [fileio/shared-01.v102.tuvl.de (/iscsi1/shared-01.v102.tuvl.de)] | | o- portals .................................................................................................... [Portals: 1] | | o- 10.102.227.145:3260 .............................................................................................. [OK] | o- tpg2 .................................................................................................. [gen-acls, no-auth] | o- acls .......................................................................................................... [ACLs: 0] | o- luns .......................................................................................................... [LUNs: 1] | | o- lun10 ................................................ [fileio/shared-01.v102.tuvl.de (/iscsi1/shared-01.v102.tuvl.de)] | o- portals .................................................................................................... [Portals: 1] | o- 10.102.1.0:3260 .................................................................................................. [OK] o- loopback ......................................................................................................... [Targets: 0] o- vhost ............................................................................................................ [Targets: 0] I have one file sparse write back file which I present as LUN 10 over to different tpgs/portals. Currently both are active optimized, I want one of the two standby. I'm talking about ALUA states (TPGS). Looking at configfs I see that I currently have one default alua group and both tpgs are targets of that one group. So what is the best way under Debian 9 strech to create a second alua group, set it to standby and set one of the two tpgs to the new alua group while removing it from the default group? I googled and found tcm_node.py which apparently can do what I want, but it seems to be discontinued: (debian) [~] git clone git://git.kernel.org/pub/scm/linux/storage/lio/lio-utils.git lio-utils.git Cloning into 'lio-utils.git'... fatal: remote error: access denied or repository not exported: /pub/scm/linux/storage/lio/lio-utils.git Is there another easy way to obtain what I want or can someone give me some clues, how to obtain what I want? Cheers, Thomas -- 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
