Thanks a lot Rafael. Unlike bug #1877617, I don't have a fix to propose for the regression on LP: #1755858, sorry!
Disabling services is a workaround for me... but definitely not a fix! My initial "enhancement" report was a little bit more specific, and not sure it will be fixed. iscsi services work normally in 2 situations: - you have some LUNs you need mounted at startup (in this case you HAVE to wait anyway) - you have no nodes at all... that's where LP: #1755858 should have fixed things and not triggered the "slow bits". I am in a third situation - I have some nodes, but none in automatic (ie not needed at startup). Would the new auto-scan help (not sure to completely understand what it does!)? I am in the exact same situation with my NFS mounts (also on my NAS), they are defined in /etc/fstab, but with the options 'noauto' and 'user' meaning they are NOT needed at startup, the the user can mount them later. With that config in /etc/fstab, NFS runs its service (RPCbind) without damaging the boot performance. As soon as I declare one of the NFS mounts as 'auto' instead, I observe the same delay on the boot, but it's normal since we now expect some NFS mounts to be there at startup. Ideally, the same would suit me for iscsi! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882986 Title: open-iscsi is slowing down the boot process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1882986/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
