Salı 26 Ekim 2010 günü (saat 01:15:50) Lennart Poettering şunları yazmıştı: > On Sun, 17.10.10 13:39, Ozan Çağlayan ([email protected]) wrote: > > Heya, > > > 1. swap.target always fails during boot. But once triggered after boot > > with systemctl restart, it succesfully enables the /.swap file. .swap > > file is on the rootfs which is an ext4 filesystem. I'm not too > > powerful with systemd but can this be caused by a read-only rootfs (so > > before remount-rootfs.target) while trying to enable swap.target? > > Unlikely. > > Could you boot with systemd.log_target=kmsg systemd.log_level=debug on > the kernel cmdline please? Then, try to reproduce this and submit the > output of "dmesg" here!
I now tried with v13 and still the issue persists. BTW, running systemctl start .swap.swap or systemctl start swap.target correctly works after the system is booted. Here's the dmesg output: Installed new job swap.target/start as 22 Installed new job .swap.swap/start as 23 About to execute: /sbin/swapon -p 0 /.swap Forked /sbin/swapon as 143 .swap.swap changed dead -> activating Got SIGCHLD for process 143 (swapon) Child 143 belongs to .swap.swap .swap.swap swap process exited, code=exited status=255 .swap.swap changed activating -> failed Job .swap.swap/start finished, success=no Unit .swap.swap entered failed state. swap.target changed dead -> active Job swap.target/start finished, success=yes # systemctl | grep swap .swap.swap loaded failed failed /.swap swap.target loaded active active Swap --- Ozan Çağlayan TUBITAK/UEKAE - Pardus Linux http://www.pardus.org.tr/eng _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
