Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 483010

Summary: sys-kernel/gentoo-sources-3.10.9 - systemd: Timed out waiting for device dev-vg1-ftp.device.
Product: Gentoo Linux Reporter: Juergen Rose <rose>
Component: [OLD] Core systemAssignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel>
Status: RESOLVED NEEDINFO    
Severity: normal CC: systemd
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: /etc/fstab

Description Juergen Rose 2013-08-30 12:54:16 UTC
Booting with 3.10.5-gentoo-r1 and systemd-206-r3 works like a charm. If I try to boot gentoo-sources-3.10.9, I come only to emergency mode. The last lines I see at the screen are:

[ TIME ] Timed out waiting for device dev-vg1-ftp.device.
[DEPEND] Dependency failed for /home/ftp
[DEPEND] Dependency failed for Local File System.
[   94.100602] systemd[1]: Job dev-vg1-var.devices/start timed out.
[   94.112...] systemd[1]: Job dev-vg1-opt.devices/start timed out.
[   94.115...] systemd[1]: Job dev-vg1-distfiles.device/start timed out.
Welcome to emergency mode!

If I login, I see than not any logical volume is mounted. But I also do not have any problem to access the logical volumes. I can fsck them and I can mount them.

The differences in .config are minimal for 3.10.5-gentoo-r1 and 3.10.9-gentoo:

root@wildcat:/usr/src(9)# diff -u linux-3.10.5-gentoo-r1/.config linux-3.10.9-gentoo/.config
--- linux-3.10.5-gentoo-r1/.config      2013-08-07 21:30:00.000000000 +0200
+++ linux-3.10.9-gentoo/.config 2013-08-30 11:30:54.000000000 +0200
@@ -1,7 +1,19 @@
 #
 # Automatically generated file; DO NOT EDIT.
-# Linux/x86 3.10.5-gentoo-r1 Kernel Configuration
+# Linux/x86 3.10.9-gentoo Kernel Configuration
 #
+
+#
+# Gentoo Linux
+#
+CONFIG_GENTOO_LINUX=y
+CONFIG_GENTOO_LINUX_UDEV=y
+
+#
+# Support for init systems, system and service managers
+#
+CONFIG_GENTOO_LINUX_INIT_SCRIPT=y
+CONFIG_GENTOO_LINUX_INIT_SYSTEMD=y
 CONFIG_64BIT=y
 CONFIG_X86_64=y
 CONFIG_X86=y


"dolvm" is part of /etc/default/grub:
root@wildcat:/usr/src(12)# grep CMD.*DEFAULT /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="dolvm root=/dev/sda3 real_init=/usr/lib/systemd/systemd rootfstype=ext4"

Both kernels have been compiled and installed with genkernel-3.4.47:
root@wildcat:/usr/src(14)# ll /boot/kernel-genkernel-x86_64-3.10.5-gentoo-r1 /boot/kernel-genkernel-x86_64-3.10.9-gentoo 
-rw-r--r-- 1 root root 3888688 Aug  7 21:38 /boot/kernel-genkernel-x86_64-3.10.5-gentoo-r1
-rw-r--r-- 1 root root 3888592 Aug 30 11:31 /boot/kernel-genkernel-x86_64-3.10.9-gentoo
root@wildcat:/usr/src(15)# genlop -t genkernel | tail -n 6
     Fri Jun  7 04:38:19 2013 >>> sys-kernel/genkernel-3.4.46.1-r1
       merge time: 29 seconds.

     Thu Jun 13 16:33:56 2013 >>> sys-kernel/genkernel-3.4.47
       merge time: 31 seconds.


I can switch with grub between 3.10.5-gentoo-r1 and 3.10.9-gentoo. 3.10.5-gentoo works every time. 3.10.9-gentoo goes every time to emergency mode.

Any idea?
Comment 1 Juergen Rose 2013-08-30 13:50:23 UTC
I have to correct, 3.10.5-gentoo-r1 was compiled and installed with genkernel-next-18 while gentoo-sources-3.10.9 was compiled and installed with genkernel-next-24.
Comment 2 Juergen Rose 2013-09-03 19:06:03 UTC
The same happens with gentoo-sources-3.10.10.
Comment 3 Pacho Ramos gentoo-dev 2013-09-03 20:23:26 UTC
That service file should be generated from /etc/fstab contents, have you modified it? Maybe attaching it could help. Also you could try to compile it with the old genkernel-next version to confirm it's not causing this issue
Comment 4 Juergen Rose 2013-09-04 10:39:59 UTC
Now I am again with 3.10.5-gentoo-r1, something what is strange for me happens.
'df' shows that /dev/mapper/vg1-ftp is not mounted, but 'mount' shows that /dev/mapper/vg1-ftp is mounted:

root@wildcat:/root(7)# uname -a
Linux wildcat 3.10.5-gentoo-r1 #1 SMP Wed Aug 7 21:38:32 CEST 2013 x86_64 Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz GenuineIntel GNU/Linux

root@wildcat:/root(8)# df
Filesystem                1K-blocks      Used Available Use% Mounted on
/dev/sda3                 131980772  28244860  97008644  23% /
none                        1986032       700   1985332   1% /run
none                        1986032       148   1985884   1% /dev/shm
udev                          10240         0     10240   0% /dev
tmpfs                       1986032       148   1985884   1% /dev/shm
tmpfs                       1986032         0   1986032   0% /sys/fs/cgroup
/dev/mapper/vg1-var         8256952   1389764   6447760  18% /var
/dev/mapper/vg1-data      351829148 156080320 177853816  47% /data_wildcat
/dev/mapper/vg1-distfiles  16772008   7629352   8303796  48% /usr/local/portage/distfiles_wildcat
/dev/mapper/vg1-home      257899908  96688176 148088148  40% /home_wildcat
/dev/mapper/vg1-portage     2046355    402312   1539186  21% /usr/portage_wildcat
/dev/mapper/vg1-opt         4128448    345180   3573556   9% /opt
/dev/mapper/vg1-tmp         8388348     33748   8354600   1% /tmp
/dev/mapper/vg1-vtmp       16776700   4838780  11937920  29% /var/tmp
/dev/mapper/vg1-src        16513960   4540488  11134612  29% /usr/src_wildcat

root@wildcat:/root(9)# df | grep ftp

root@wildcat:/root(10)# mount | grep ftp
/dev/mapper/vg1-ftp on /home_wildcat/ftp type xfs (rw,noatime,attr2,inode64,noquota)

root@wildcat:/root(11)# grep xfs /proc/filesystems 
        xfs
nodev   selinuxfs

root@wildcat:/root(12)# grep ftp /etc/fstab   (some spaces removed)
/dev/vg1/ftp   /home/ftp      xfs               noatime         1 2

And I can mount /dev/mapper/vg1-ftp manually like a charm:

root@wildcat:/root(13)# mount /dev/mapper/vg1-ftp /home/ftp/
root@wildcat:/root(14)# df | tail
/dev/mapper/vg1-var         8256952   1408980   6428544  18% /var
/dev/mapper/vg1-data      351829148 156080320 177853816  47% /data_wildcat
/dev/mapper/vg1-distfiles  16772008   7629352   8303796  48% /usr/local/portage/distfiles_wildcat
/dev/mapper/vg1-home      257899908  96688176 148088148  40% /home_wildcat
/dev/mapper/vg1-portage     2046355    402312   1539186  21% /usr/portage_wildcat
/dev/mapper/vg1-opt         4128448    345180   3573556   9% /opt
/dev/mapper/vg1-tmp         8388348     33748   8354600   1% /tmp
/dev/mapper/vg1-vtmp       16776700   4929772  11846928  30% /var/tmp
/dev/mapper/vg1-src        16513960   4540488  11134612  29% /usr/src_wildcat
/dev/mapper/vg1-ftp       136248320   2209012 134039308   2% /home_wildcat/ftp
Comment 5 Juergen Rose 2013-09-04 10:41:15 UTC
Created attachment 357834 [details]
/etc/fstab
Comment 6 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2013-09-04 10:44:54 UTC
mtab symlinked to /proc/self/mounts?
Comment 7 Juergen Rose 2013-09-04 11:27:30 UTC
(In reply to Michał Górny from comment #6)
> mtab symlinked to /proc/self/mounts?

Yes:

root@wildcat:/usr/src/linux(26)# ll /etc/mtab
lrwxrwxrwx 1 root root 17 Aug 23 12:16 /etc/mtab -> /proc/self/mounts
Comment 8 Juergen Rose 2013-09-04 12:15:35 UTC
(In reply to Pacho Ramos from comment #3)
> That service file should be generated from /etc/fstab contents, have you
> modified it? Maybe attaching it could help. Also you could try to compile it
> with the old genkernel-next version to confirm it's not causing this issue

I reinstalled the old genkernel-next-18:

root@wildcat:/root(2)# genlop -t genkernel-next | tail -n6
     Tue Aug 27 12:16:25 2013 >>> sys-kernel/genkernel-next-24
       merge time: 54 seconds.

     Wed Sep  4 12:45:34 2013 >>> sys-kernel/genkernel-next-18
       merge time: 1 minute and 37 seconds.

Then I reinstalled 3.10.10-gentoo:

root@wildcat:/root(5)# ll -t /boot/kernel-genkernel-x86_64-3.* | head -n3
-rw-r--r-- 1 root root 3890480 Sep  4 13:15 /boot/kernel-genkernel-x86_64-3.10.10-gentoo
-rw-r--r-- 1 root root 3888592 Aug 30 11:31 /boot/kernel-genkernel-x86_64-3.10.9-gentoo
-rw-r--r-- 1 root root 3888688 Aug  7 21:38 /boot/kernel-genkernel-x86_64-3.10.5-gentoo-r1

I get the same issue. I thought, maybe the xfs filesystem of logical volume vg1-ftp is responsible for the problem. I commented it out from /etc/fstab.
The next reboot fails with:
...
 TIME ] Timed out waiting for /usr/src_wildcat
[DEPEND] Dependency failed for /usr/src_wildcat
[DEPEND] Dependency failed for Local File Systems.
[   94.017***] systemd[1]: Job dev-vg1-data.device/start timed out.
[   94.018***] systemd[1]: Job dev-vg1-vtmp.device/start timed out.
[   94.020***] systemd[1]: Job dev-vg1-var.device/start timed out.
[   94.022***] systemd[1]: Job dev-vg1-tmp.device/start timed out.
[   94.025***] systemd[1]: Job dev-vg1-home.device/start timed out.
[   94.028***] systemd[1]: Job dev-vg1-portage.device/start timed out.
[   94.033***] systemd[1]: Job dev-vg1-portage.device/start timed out.
Wellcome to emergency mode! After logging in, ...


I logged inti the emergency mode and had no problems to mount a logical volume:

root@wildcat:/root(16)# mount /dev/mapper/vg1-data /data_wildcat

[  591.928****] EXT4-fs (dm-9): mounted filesystem withordered data mode. Opts: (null)
root@wildcat:/root(17)# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda3            131980772  28243824  97009680  23% /
none                   1986032      1932   1984100   1% /run
none                   1986032         0   1986032   0% /dev/shm
udev                     10240         4     10236   1% /dev
tmpfs                  1986032         0   1986032   0% /dev/shm
tmpfs                  1986032         0   1986032   0% /sys/fs/cgroup
/dev/mapper/vg1-data 351829148 156080320 177853816  47% /data_wildcat
Comment 9 Juergen Rose 2013-09-06 10:25:35 UTC
The same happens with gentoo-sources-3.10.7.
Comment 10 Fabio Erculiani (RETIRED) gentoo-dev 2013-09-06 10:33:37 UTC
You should run genkernel with the --udev flag.
Comment 11 Juergen Rose 2013-09-06 18:45:32 UTC
(In reply to Fabio Erculiani from comment #10)
> You should run genkernel with the --udev flag.

Thanks Fabio, that works.
Comment 12 Tom Wijsman (TomWij) (RETIRED) gentoo-dev 2013-09-06 22:53:31 UTC
(In reply to Fabio Erculiani from comment #10)
> You should run genkernel with the --udev flag.

What do manual users have to do in this case; or, well, do manual users don't experience this due to something genkernel does in particular?

I just want to know if this is still a kernel bug or not.