Hello Christian,
On Tue, Aug 30, 2016 at 10:24:22PM +0200, Christian Seiler wrote:
> While not having tested this, from just looking at the code with
> your explanation in mind, yes, you're right about that.
thanks for your confirmation!
> Your fix is also correct, but I'm not sure I like the endless
> list of -o -n repeats... I'll think about it for a while and if
> I can't find a better solution, I'll commit your fix to git.
> (And if I find a better solution, I'll commit that. ;-))
By all means, please do! I'm also not particularly happy with this
temporary fix, but "it did get the job done"[TM] ;-)
> Speaking of: you appear to be interested in a backport of
> open-iscsi into Jessie because you want to use offloading via
> iscsiuio. I've been thinking about uploading open-isns and
> open-iscsi to jessie-backports myself (precisely to have iscsiuio
> support available for Jessie users), but was unsure whether
> there's enough people who'd be interested in that. Would that be
> something you'd use yourself? Or would you want to continue to
> use your special backported version instead? Since you're
> actively using iscsiuio, I'd like to hear your opinion on that
> first.
No, i'd definitely prefer an "official" backported version of the
package, provided it's based on reasonably recent open-iscsi upstream
sources - there are several important fixes as of late not covered by
the current Jessie package sources. I particularly like your idea of
putting iscsiuio into its own package.
What's a real pain though, is the whole hassle with "_netdev", "LVM-
GROUPS", and still having to tweak the multipath init script. Well,
that's at least what i ended up with to get the order of things at
boot time at least almost right :-( Compared to the straightforward
use of targets through full iSOEs like e.g. the QME8262 cards, this
just feels awkward. Maybe it's just me doing something terribly wrong
;-)
Thanks & best regards,
Frank
