[Pkg-iscsi-maintainers] Bug#836135: umountiscsi.sh indiscriminately umounts all LVM based filesystems when no iSCSI sessions are found.

[Christian Seiler]

On 09/09/2016 07:08 PM, Frank Fegert wrote:
> sorry for the delayed reply!

No worries, I was busy with other stuff anyway.

>> As for "recent-ness" of backports: the rules for jessie-backports
>> are that Stretch has to be tracked. Since open-iscsi with iscsiuio
>> will migrate to Stretch tomorrow (barring a last-minute RC bug),
>> that's going to be the lowest possible version that's going to
>> land in backports. And until Stretch is released, jessie-backports
>> would get all further improvements. (Though to be honest, I don't
>> see that many major changes happening until Stretch; iscsiuio and
>> the earlier rework of the startup logic were the big ones on my
>> list, and those are done.)
> 
> Ok, can i instead ask to please add this upstream commit:
>   https://github.com/open-iscsi/open-iscsi/commit/efdd487c70269749f03be8342c4fde8fd3b59f8a
> 
> as a patch to the stretch/jessie-backports package?

Thanks for the pointer, I'll try to upload a new version to sid
today with that patch + the fix for umountiscsi.sh.

(Also, thanks for having that as an upstream pull request, I wanted
to talk to upstream soon anyway and prod them to officially release
a new version at some point - it's much easier to tell them "we have
commit XYZ in Debian atm, + pull requests A, B and C.")

>>> and still having to tweak the multipath init script.
>>
>> Could you be more specific here? What exactly do you need to do?
>> I still have an item on my TODO list to take a look at multipath
>> vs. iSCSI in Jessie (in Stretch it works), because there was a
>> bug report on debian-user about it - I just didn't manage to do
>> so yet. If you are using that and have already looked into it,
>> it would be great, then I could probably try to also get that
>> sorted. (No guarantees for 8.6 though, because that'll happen on
>> Sep. 17th, so the time window is a bit short there.)
> 
> Sorry, i had a wrong memory of this - probably too many tests and
> workarounds that in the end didn't quite work. The issue with multi-
> path wasn't with the init script itself, but actually the one de-
> scribed here:
>   https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1431650
>   https://github.com/hreinecke/multipath-tools/commit/841977fc9c3432702c296d6239e4a54291a6007a

Thanks for the pointer. Unfortunately, the window for updates for
the next Jessie point release have closed, (well, technically there
are a couple of hours left today, but I'm not the maintainer of
multipath-tools, and while I could work with them to make it happen,
it won't be in time), so this will have to wait for the point release
after that. I'll look into this issue though until then.

Regards,
Christian