Bug 1192393 - Swap Space Error at Boot Shown [NEEDINFO]
Summary: Swap Space Error at Boot Shown
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 21
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-13 09:49 UTC by schaefi
Modified: 2015-12-02 17:25 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-12-02 08:59:53 UTC
Type: Bug
Embargoed:
kernel-team: needinfo?


Attachments (Terms of Use)

Description schaefi 2015-02-13 09:49:08 UTC
At boot-time various error messages related to swap-space appear. The verification of swap after boot shows that swap is mounted/used correctly.

My system:
uname -a
Linux hoelderlin 3.17.4-301.fc21.x86_64 #1 SMP Thu Nov 27 19:09:10 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

My swap partitions as listed in /etc/fstab:
UUID=3acc1c2c-493e-4cb5-9ba0-b4642dd66b8e swap                    swap    defaults        0 0

The swap partion has been manually defined and created within the Fedora 21 installation process.The partition is /dev/sda10

The correct status of the swap after boot is shown:
swapon
NAME       TYPE      SIZE USED PRIO
/dev/sda16 partition 7.5G   0B   -1
/dev/sda10 partition 7.7G   0B   -2

and by checkking dmesg:
dmesg | grep swap
[   24.090247] Adding 7812092k swap on /dev/sda16.  Priority:-1 extents:1 across:7812092k FS
[   38.214418] Adding 8077308k swap on /dev/sda10.  Priority:-2 extents:1 across:8077308k FS


Analysis of the bug:
There has been a common bug in Fedora 20 (https://bugzilla.redhat.com/show_bug.cgi?id=1017509) that looks to me quite similar.
Interesting for me is that /dev/sda6 and /dev/sda10 is mounted as swap, altough at the installation only dev/sda10 has been specified.

If you need further information, please let me know.
Unfortunately I can not write down the exact error message that is displayed at boot-time since I have been unable to do this with jounralctl. If anybody could give me the command to display the message that is shown at boot time, this would be very appreciated.

Comment 1 Jóhann B. Guðmundsson 2015-02-13 10:13:56 UTC
The workaround for this ( harmless ) issue is to hash out the swap entry in /etc/fstab until cdda4aa8d20c2679cc937d40e793abe7806f17cb get's back ported

Comment 2 Jóhann B. Guðmundsson 2015-02-13 10:15:13 UTC
Just to be sure we are dealing with the same issue paste the output from 
"systemctl -a -t swap" here in the report

Comment 3 schaefi 2015-02-13 16:10:01 UTC
(In reply to Jóhann B. Guðmundsson from comment #2)
> Just to be sure we are dealing with the same issue paste the output from 
> "systemctl -a -t swap" here in the report

Hi Johann,

Thanks for your input!
Here the required information:

systemctl -a -t swap
UNIT                         LOAD   ACTIVE SUB    DESCRIPTION
dev-disk-by\x2did-ata\x2dHitachi_HTS545050A7E380_TA85113VDAABVN\x2dpart10.swap 
dev-disk-by\x2did-ata\x2dHitachi_HTS545050A7E380_TA85113VDAABVN\x2dpart16.swap 
dev-disk-by\x2did-wwn\x2d0x5000cca6f5d2ca30\x2dpart10.swap loaded active active
dev-disk-by\x2did-wwn\x2d0x5000cca6f5d2ca30\x2dpart16.swap loaded active active
dev-disk-by\x2dpartuuid-8cade4b7\x2d8c23\x2d4869\x2d9176\x2d9521698bc52a.swap l
dev-disk-by\x2dpartuuid-ab2d73d2\x2d9994\x2d4fe7\x2d8c02\x2d9850e0b03be2.swap l
dev-disk-by\x2duuid-3acc1c2c\x2d493e\x2d4cb5\x2d9ba0\x2db4642dd66b8e.swap loade
dev-disk-by\x2duuid-f6b1d998\x2d3044\x2d4cb5\x2db832\x2d7c89ac24f188.swap loade
dev-sda10.swap               loaded active active Swap Partition
dev-sda16.swap               loaded active active Swap Partition

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

10 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.

Comment 4 Fedora Kernel Team 2015-04-28 18:32:05 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 21 kernel bugs.

Fedora 21 has now been rebased to 3.19.5-200.fc21.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 22, and are still experiencing this issue, please change the version to Fedora 22.

If you experience different issues, please open a new bug report for those.

Comment 5 Fedora End Of Life 2015-11-04 12:24:03 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-12-02 09:00:00 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.