I have a /dev/md3 software raid device that doesn't work via the MS iSNS Server when locating the target. If you enter the IP of the server that is running ietd and do not use the iSNS server to locate targets then it all works ok. I am using the ebuild for iscsitarget0.4.15 that I downloaded from this bug report: http://bugs.gentoo.org/show_bug.cgi?id=159587 Is there an issue with talking to MS iSNS servers? Reproducible: Always Steps to Reproduce: 1.create a software raid device 2.export that via ietd.conf 3.look in MS iSNS console for the target and it will be listed as unknown rather than Initiator or Target as the others are.
Don't report bugs about stuff that's not in the official tree. Thanks. *** This bug has been marked as a duplicate of bug 159587 ***
ok, fair point, but please be aware that this is also an issue for the previous iscsitarget-0.4.14 I wanted to try the latest 0.4.15 to see if this had fixed the bug!
richard.scott: does an export md device show up in open-iscsi or the open source iSNS apps? I haven't got a usable iSCSI test environment at the moment (that's actually been my delay in bumping iSCSI packages), but last time I did, I had absolutely no trouble exporting a md device, and using it with open-iscsi from another machine.
(In reply to comment #3) > richard.scott: does an export md device show up in open-iscsi or the open > source iSNS apps? I've just downloaded and tried this: http://sourceforge.net/projects/linuxisns when I run isnsd I get the following: src/iSNSrcv.c 196: Error forwarding fsm message (xid 0) so I guess the answer is no, it doesn't work ;-(
and when you use pure open-iscsi and no iSNS? i think you should probably pursue this with upstream.
(In reply to comment #5) > and when you use pure open-iscsi and no iSNS? > i think you should probably pursue this with upstream. Connecting to a device exported via ietd works ok for both MD and HD/SD devices, so its just the listing in iSNS that is wrong. it's not important for me to persue this upstream at the moment,so I'll sit and wait as I'm sure others must have noticed this problem??? I guess we could either close this as we (the Gentoo community) can't do anything about it.
I'll close as upstream. If you could please just report it to them.