RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

DESCRIPTION OF PROBLEM:

  See: https://github.com/systemd/systemd/commit/681c8d81bdc946360d13185632d1920ffaeb5ad9
  systemd stops swap too early in the shutdown process.
  Note that the commit and originating PR seem to me to be about dealing with multiple swapdevs, though I'm only using one.
  
VERSION-RELEASE NUMBER OF SELECTED COMPONENT (IF APPLICABLE):

  systemd-219-26.el7.x86_64
  
HOW REPRODUCIBLE:

  100%
  
STEPS TO REPRODUCE:

  1. Make sure a system has swap enabled
  2. To make life easy, enable persistent journaling (mkdir /var/log/journal; systemctl kill -s SIGUSR1 systemd-journald.service)
  3. Open the logs (journalctl -b -1) and search for "Deactiv.*swap"

ACTUAL RESULTS:

  Swap begins deactivating before multi-user.target is stopped.
  Swap appears to be deactivated before many services have stopped.
  
EXPECTED RESULTS:

  Swap should be one of the last things to be deactivated. Let all applications shut down before we page remaining swap back into RAM.
  
ADDITIONAL INFO:

  If I'm understanding this behavior correctly, well ... it seems like a really big deal. Thus, I hope I'm missing something here and if so, my apologies.

I'll provide testing packages with the patch backported.

(In reply to Jan Synacek from comment #2)
> Testing packages can be found at
> http://file.brq.redhat.com/~jsynacek/systemd/bz1379268/.

This URL does not resolve.

Are these packages publicly accessible?

Nope, sorry about the confusion. We (systemd maintainers) publicly provide backported patches for testing at https://copr.fedorainfracloud.org/coprs/lnykryn/systemd-rhel-staging. I'm not sure if this patch has already been backported, though.

This bug has already been pushed to staging in https://bugzilla.redhat.com/show_bug.cgi?id=1298355.

*** This bug has been marked as a duplicate of bug 1298355 ***

This is not a duplicate of bug 1298355. https://bugzilla.redhat.com/show_bug.cgi?id=1031158#c12

(In reply to thierry.laurion from comment #6)
> This is not a duplicate of bug 1298355.

Yes it is, the fix for both is the same.

> https://bugzilla.redhat.com/show_bug.cgi?id=1031158#c12

This is not relevant.