Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#28632 - activating swap fails under util-linux 2.21-1

Attached to Project: Arch Linux
Opened by Hussam Al-Tayeb (hussam) - Friday, 24 February 2012, 18:48 GMT
Last edited by Tom Gundersen (tomegun) - Saturday, 25 February 2012, 13:27 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

activating swap at boot fails with util-linux 2.21-1
however free commands shows the swap was actually activated.
This worked in 2.20

rolling back mkinitcpio and util-linux to 2.20 (and regenrating boot image fix it)
This task depends upon

Closed by  Tom Gundersen (tomegun)
Saturday, 25 February 2012, 13:27 GMT
Reason for closing:  Fixed
Additional comments about closing:  by util-linux-2.21-2
Comment by Dave Reisner (falconindy) - Friday, 24 February 2012, 19:05 GMT
Based on the changelog for swapon since 2.20.1, you'll need to provide more than just anecdotal evidence.
Comment by Hussam Al-Tayeb (hussam) - Friday, 24 February 2012, 19:14 GMT
which means?
Anyway, before the update it didn't say failed. after the update, it says failed although swap gets activated. rolling back makes it succeed again. In both cases, swap is getting activated.
Comment by Dave Reisner (falconindy) - Friday, 24 February 2012, 19:21 GMT
I would consider /var/log/boot and your /etc/fstab to be the bare minimum.
Comment by Tom Gundersen (tomegun) - Friday, 24 February 2012, 19:28 GMT
@hussam: please also attach your dmesg. Thanks!
Comment by Hussam Al-Tayeb (hussam) - Friday, 24 February 2012, 19:44 GMT
cat /var/log/boot
outputs nothing.

cat /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0

/dev/mapper/root / ext4 defaults,user_xattr 0 1
/dev/sda1 /boot ext4 defaults,user_xattr 0 1
/dev/sda2 none swap defaults 0 0
/dev/mapper/home /home ext4 defaults,user_xattr 0 1

   dmesg.log (43.7 KiB)
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 24 February 2012, 20:06 GMT
I guess that is not swap, see lines with more detail (off-by-one visual eye error :P), its the issue with "Mounting Local Filesystems", in other words with mount -a [#1]

http://mailman.archlinux.org/pipermail/arch-projects/2012-February/002494.html
Comment by Tom Gundersen (tomegun) - Friday, 24 February 2012, 20:10 GMT
@djgera: most probably. I'm trying to get it verified with Karel that this is indeed intentional (I don't like it), and that the bug was in the old mount.
Comment by Tom Gundersen (tomegun) - Saturday, 25 February 2012, 10:45 GMT
@hussam: could you try util-linux-2.21-2 in testing? It should have fixed this issue (assuming the problem was with mount and not with swapon).
Comment by Hussam Al-Tayeb (hussam) - Saturday, 25 February 2012, 13:22 GMT
It is fixed in util-linux 2.21-2

Yes, it was the mount and not swapon. I must be getting too old ;)

Thank you very much :)
Comment by Tom Gundersen (tomegun) - Saturday, 25 February 2012, 13:27 GMT
Thanks!

Loading...