(0.686.4)
I defined 2 iscsi-initiators and with them I defined a software raid1 disk.
My raid1 consited of disk da1 (iqn.2004.freebsd:target0 ) and
disk da2 (iqn.2008.cluster01:disk0). This raid1 is fully functional.
When I define another 2 iscsi initiators from targets on the same machines as the previous ones (iqn.2004.freebsd:target1 and
iqn.2008.cluster01:disk1), a new raid1 config attempts to use the two new disk da3 and da4 but fails to complete. When I look at the diskconfiguration, I get
the following:
da1: iqn.2004.freebsd:target0
da2: iqn.2004.freebsd:target1
da3: iqn.2008.cluster01:disk0
da4: iqn.2008.cluster01:disk1
in stead of the expected
da1: iqn.2004.freebsd:target0
da2: iqn.2008.cluster01:disk0
da3: iqn.2004.freebsd:target1
da4: iqn.2008.cluster01:disk1
This is a first indicator that things go wrong but the iscsi tools still report the right configuration for the existing raid1.
After a reboot the system seems to 'reshuffle' the configuration and the first raid1 is not workings anymore and is assumed to consist of da1 and da3.
To me it seems that after adding an iscsi-initiator the system rescans the target
server and incorrectly re-assigns disk numbers in numeric order PER target address.
While assiging the new iscsi-initiators I noticed a different text on the console messages compared to the GUI info.
Possible other bug:
After playing around with new raid1 disknames the console messages keep reporting the first-ever used raid1-name in stead of the new name. That first-ever used diskname returns miraculously even after returning to the factory default settings!!?
