[systemd-devel] How to set a limit for mounting roofs?
Chris Murphy
lists at colorremedies.com
Tue Jul 5 16:22:50 UTC 2016
pre-mount:/# cat /run/systemd/generator/dev-vda2.device.d/timeout.conf
[Unit]
JobTimeoutSec=0
This is virsh console output during boot:
https://drive.google.com/open?id=0B_2Asp8DGjJ9RlN1cGJTTEtHcjg
Here is journalctl -b -o short-monotonic output from the pre-mount
shell using Command line:
BOOT_IMAGE=/vmlinuz-3.10.0-327.22.2.el7.x86_64 root=/dev/vda2 ro
rootflags=subvol=root,degraded vconsole.keymap=us crashkernel=auto
vconsole.font=latarcyrheb-sun16 rhgb quiet LANG=en_US.UTF-8
systemd.log_level=debug rd.udev.debug rd.debug
systemd.log_target=console console=ttyS0,38400 rd.break=pre-mount
https://drive.google.com/open?id=0B_2Asp8DGjJ9OThvS2Q3X3pWT3c
What I'm getting from the journal is...
[ 2.939557] localhost.localdomain kernel: virtio-pci 0000:00:05.0:
irq 27 for MSI/MSI-X
[ 2.939595] localhost.localdomain kernel: virtio-pci 0000:00:05.0:
irq 28 for MSI/MSI-X
[ 2.939849] localhost.localdomain kernel: vda: vda1 vda2
OK so the kernel sees the drive and the partitions.
[ 3.043274] localhost.localdomain kernel: Btrfs loaded
[ 3.043836] localhost.localdomain kernel: BTRFS: device label
centos devid 1 transid 55 /dev/vda2
It sees the file system on /dev/vda2 (raid1, missing device vdb1)
But then I hit pre-mount so I don't actually find out why it won't
mount. If there were a problem with degraded mounts, the mount should
explicitly fail, and then systemd would drop to a shell if rd.shell is
used. But it doesn't. It just hangs. So the mount isn't hard failing,
it's like some kind of soft fail where systemd just waits for some
reason.
Chris Murphy
More information about the systemd-devel
mailing list