[systemd-devel] how disable fsck on swap+lvm
Alexey Shabalin
a.shabalin at gmail.com
Mon Feb 21 07:47:43 PST 2011
>> >> You can see in log:
>> >> Feb 16 16:04:51 host-29 kernel: [ 11.636564] Adding 524284k swap on
>> >> /dev/mapper/VG1-Swap. Priority:-1 extents:1 across:524284k
>> >> Feb 16 16:04:51 host-29 kernel: [ 11.669141] clock[1954]: Setting
>> >> system clock (localtime): succeeded
>> >> Feb 16 16:04:51 host-29 kernel: [ 11.770936] clock[1965]: Today's
>> >> date: Wed Feb 16 16:03:48 MSK 2011 succeeded
>> >> Feb 16 16:04:51 host-29 kernel: [ 68.503001] systemd[1]: Job
>> >> dev-disk-by\x2duuid-bf5d2d3e\x2d174c\x2d44ea\x2dbf89\x2dcd6ecead5f81.device/start
>> >> timed out.
>> >>
>> >> swap on lvm(VG1-Swap), and systemd run fsck on this partition.
>> >
>> > This does not show anything related to fsck?
>> >> I know that swap on lvm no good practics, but need foolproof.
>> >
>> > If you use LVM make sure to use a new version that properly installs its
>> > udev rules.
>> I used lvm-2.02.84. I don't see udev rules that run "vgchange -a y".
>
> Well, ensure you have /lib/udev/rules.d/11-dm-lvm.rules installed.
I was test two variant.
- systemd-18, udev-166, lvm2-2.02.84,mdadm-3.1.4
- dont't use rc.sysinit or any other external script (like
fedora-storage-init or fedora-swap). Only systemd services and
upstream udev rules.
First variant:
/ - on LVM, runned by initrd
swap - on LVM
Feb 21 16:21:35 host-29 kernel: [ 0.000000] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz root=/dev/mapper/VG1-root ro panic=30 splash
init=/bin/systemd systemd.log_level=debug
-- skip --
Feb 21 16:21:35 host-29 kernel: [ 10.418096] systemd[1]: Installed
new job swap.target/start as 20
Feb 21 16:21:35 host-29 kernel: [ 10.419570] systemd[1]: Installed
new job dev-disk-by\x2duuid-bf5d2d3e\x2d174c\x2d44ea\x2dbf89\x2dcd6ecead5f81.swap/start
as 21
Feb 21 16:21:35 host-29 kernel: [ 10.422231] systemd[1]: Installed
new job dev-disk-by\x2duuid-bf5d2d3e\x2d174c\x2d44ea\x2dbf89\x2dcd6ecead5f81.device/start
as 22
-- skip --
Feb 21 16:21:35 host-29 kernel: [ 12.995562] systemd[1]:
udev.service: control process exited, code=exited status=0
Feb 21 16:21:35 host-29 kernel: [ 13.004173] systemd[1]:
udev.service got final SIGCHLD for state start-post
Feb 21 16:21:35 host-29 kernel: [ 13.005934] systemd[1]:
udev.service changed start-post -> running
Feb 21 16:21:35 host-29 kernel: [ 13.007450] systemd[1]: Job
udev.service/start finished, success=yes
Feb 21 16:21:35 host-29 kernel: [ 13.014888] systemd[1]: About to
execute: /sbin/udevadm settle
Feb 21 16:21:35 host-29 kernel: [ 13.029302] systemd[1]: Forked
/sbin/udevadm as 2053
Feb 21 16:21:35 host-29 kernel: [ 13.031287] systemd[1]:
udev-settle.service changed dead -> start
Feb 21 16:21:35 host-29 kernel: [ 13.037557] systemd[1]: About to
execute: /sbin/udevadm trigger --type=failed --action=add
Feb 21 16:21:35 host-29 kernel: [ 13.044068] systemd[1]: Forked
/sbin/udevadm as 2055
Feb 21 16:21:35 host-29 kernel: [ 13.045777] systemd[1]:
udev-retry.service changed dead -> start
-- skip --
Feb 21 16:21:35 host-29 kernel: [ 13.803160] systemd[1]:
dev-disk-by\x2dpath-virtio\x2dpci\x2dvirtio2.device changed dead ->
plugged
Feb 21 16:21:35 host-29 kernel: [ 13.805666] systemd[1]:
dev-vda.device changed dead -> plugged
Feb 21 16:21:35 host-29 kernel: [ 13.807133] systemd[1]:
sys-devices-virtio\x2dpci-virtio2-block-vda.device changed dead ->
plugged
Feb 21 16:21:35 host-29 kernel: [ 14.475926] systemd[1]:
dev-disk-by\x2dpath-virtio\x2dpci\x2dvirtio2\x2dpart1.device changed
dead -> plugged
Feb 21 16:21:35 host-29 kernel: [ 14.478240] systemd[1]:
dev-vda1.device changed dead -> plugged
Feb 21 16:21:35 host-29 kernel: [ 14.479750] systemd[1]:
sys-devices-virtio\x2dpci-virtio2-block-vda-vda1.device changed dead
-> plugged
-- skip --
Feb 21 16:21:35 host-29 kernel: [ 27.344511] systemd[1]: Got D-Bus
request: org.freedesktop.DBus.Local.Disconnected() on
/org/freedesktop/DBus/Local
Feb 21 16:21:35 host-29 kernel: [ 70.422401] systemd[1]: Job
dev-disk-by\x2duuid-bf5d2d3e\x2d174c\x2d44ea\x2dbf89\x2dcd6ecead5f81.device/start
timed out.
Feb 21 16:21:35 host-29 kernel: [ 70.424801] systemd[1]: Job
dev-disk-by\x2duuid-bf5d2d3e\x2d174c\x2d44ea\x2dbf89\x2dcd6ecead5f81.device/start
finished, success=no
Feb 21 16:21:35 host-29 kernel: [ 70.427203] systemd[1]: Job
dev-disk-by\x2duuid-bf5d2d3e\x2d174c\x2d44ea\x2dbf89\x2dcd6ecead5f81.swap/start
finished, success=no
Feb 21 16:21:35 host-29 kernel: [ 70.432647] systemd[1]: swap.target
changed dead -> active
Feb 21 16:21:35 host-29 kernel: [ 70.434125] systemd[1]: Job
swap.target/start finished, success=yes
"Job swap.target/start finished, success=yes", but "device/start
finished, success=no" and swap not enabled.
Second variant:
/ - on md0 (raid1 mdadm), runned by initrd
/home - on LVM (raid1+lvm)
Feb 21 18:14:26 shabalin2 kernel: [ 3.818788] md: Autodetecting RAID arrays.
--skip--
Feb 21 18:14:26 shabalin2 kernel: [ 3.825068] md/raid1:md1: active
with 2 out of 2 mirrors
Feb 21 18:14:26 shabalin2 kernel: [ 3.829903] md/raid1:md0: active
with 2 out of 2 mirrors
Feb 21 18:14:26 shabalin2 kernel: [ 4.513273] EXT4-fs (md0):
mounted filesystem with ordered data mode. Opts: (null)
--skip--
Feb 21 18:14:26 shabalin2 kernel: [ 23.213353] systemd[1]: Got D-Bus
request: org.freedesktop.DBus.Local.Disconnected() on
/org/freedesktop/DBus/Local
Feb 21 18:14:26 shabalin2 kernel: [ 67.938433] systemd[1]: Job
dev-disk-by\x2duuid-a1d69a60\x2d3654\x2d4c22\x2da307\x2d13af8d94732e.device/start
timed out.
Feb 21 18:14:26 shabalin2 kernel: [ 67.938819] systemd[1]: Job
dev-disk-by\x2duuid-a1d69a60\x2d3654\x2d4c22\x2da307\x2d13af8d94732e.device/start
finished,success=no
Feb 21 18:14:26 shabalin2 kernel: [ 67.939158] systemd[1]: Job
home.mount/start finished, success=no
Feb 21 18:14:26 shabalin2 kernel: [ 67.939892] systemd[1]: Job
fsck at dev-disk-by\x2duuid-a1d69a60\x2d3654\x2d4c22\x2da307\x2d13af8d94732e.service/start
finished, success=no
"Job home.mount/start finished, success=no" and i have not mounted /home
I need manual run:
vgchange -a y
mount /home
systemd+udev can't replace rc.sysinit(or external script like
fedora-storage-init) now. :(
--
Alexey Shabalin
More information about the systemd-devel
mailing list