New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
95resume: Do not resume on iSCSI #329
Conversation
Can one of the admins verify this patch? |
@centos-ci ok to test |
@haraldh Can you give me the magic power to trigger CI runs? |
@danimo you now have the power :) May the force be with you :) |
@centos-ci ok to test |
What, if the swap partition is local? |
Back from vacation. Fair point. Is there a reliable way to tell if all swap storage is truly local? |
Wouldn't it be better to just tell the user not to place |
Ah, Suse is compiling that in the initramfs. So the resume dracut module should skip network block devices. |
Does dracut already have a function to drill down && check for the type of the underlying block device? |
Nothing globally yet.
|
Any suggestion on how to avoid code dupes? {iscsi,nbd}-lib.sh will not work, as they cannot be sourced from the module-setup.sh that installs them. |
well, put those functions in dracut-functions.sh, create a function |
will you or should I? |
this looks related to #480 - can someone confirm? |
@danimo ping |
1aa9d8a
to
8b54b19
Compare
8b54b19
to
00383c0
Compare
please rebase |
Done. But the |
correct |
Done. |
@danimo It looks good, but can you rebase on current master? |
The iSCSI configuration is started after dracut checks for resume, so we run into a timeout here. Additionally it's questionable if resume on iSCSI makes sense (or is even supported on the platform). Same holds true for Network Block Devices and FcOE, cover those as well References: bsc#999663 Original-patch-by: Hannes Reinecke <hare@suse.com> Signed-off-by: Daniel Molkentin <daniel.molkentin@suse.com>
@Conan-Kudo done. |
The iSCSI configuration is started after dracut checks for resume,
so we run into a timeout here. Additionally it's questionable if
resume on iSCSI makes sense (or is even supported on the platform),
so disable it for now.
References: bsc#999663
Signed-off-by: Hannes Reinecke hare@suse.com