>Mike Christie [] wrote:
>> If the ibft implementation uses one session, but exports all the 
>> targets in the ibft info, then in RHEL 5.3 the installer only picks
>> the session used for the ibft boot up, but the initrd root-boot code 
>> used after the install should log into all the targets in ibft
>> they were used for the ibft boot or not. There different behavior is
>> result of the installer goofing up where is used the wrong api.
>It is quite likely that my iBFT implementation uses&exports a single

My bad! Malahal has fixed the issue I guess.
But it does seem like we will hit an issue if the iBFT does export
multiple sessions and iscsiadm doesn't use them in the installer to find
multiple paths.


You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to