Comment # 4 on bug 1011127 from
(In reply to Michael from Offenbach Germany from comment #0)
> upgrade my small vserver from 42.1 latest patches to 42.2.
> no errors during zypper dup, smooth and easy.
> but reboot stops in emergency mode
> 
> journalctl -xb appended.
> 
> I'm not deeply familiar in reading journalctl entries, but there seems to be
> a major issue. line 1249 and following:
> 
> -----------------------------------------------------------------------------
> -------------------
> Nov 19 13:41:28 vserver systemd[1]: var-mail.mount: Mount on symlink
> /var/mail not allowed.
> -- Subject: Mount point is not empty
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> -- 
> -- The directory /var/mail is specified as the mount point (second field in
> -- /etc/fstab or Where= field in systemd unit file) and is not empty.
> -- This does not interfere with mounting, but the pre-exisiting files in
> -- this directory become inaccessible. To see those over-mounted files,
> -- please manually mount the underlying file system to a secondary
> -- location.
> Nov 19 13:41:28 vserver systemd[1]: var-mail.mount: Failed to run 'mount'
> task: Too many levels of symbolic links
> Nov 19 13:41:28 vserver systemd[1]: Failed to mount /var/mail.
> -- Subject: Unit var-mail.mount has failed
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> -- 
> -- Unit var-mail.mount has failed.
> -- 
> -- The result is failed.
> -----------------------------------------------------------------------------
> -------------------
> 
> a) /var/mail is empty, for 100%. Only peculiarity is that "." has a "t"
> instead of "x" for execute bit for "other". Probably because as an OpenSuse
> out-of-the-box-default a link between /var/mail and /var/spool/mail exists.
> 
> b) fstab is as follows:
> 
> -----------------------------------------------------------------------------
> -------------------
> UUID=2f60420d-d128-460d-977e-999ed7fbb956 swap                 swap      
> defaults              0 0
> UUID=5dd1c047-069d-4227-938a-2129e710bb02 /                    ext4      
> acl,user_xattr        1 1 
> UUID=912b8a4f-73bc-47f9-bbce-560858eaac59 /boot                ext4      
> acl,user_xattr        1 2
> /dev/vg_vserver/lv_home		/home	ext4	acl,user_xattr	0	2
> /dev/vg_vserver/lv_srv		/srv	ext4	acl,user_xattr	0	2
> /dev/vg_vserver/lv_var		/var	ext4	acl,user_xattr	0	2
> /dev/vg_vserver/lv_tmp		/tmp	ext4	acl,user_xattr	0	2
> /dev/vg_vserver/lv_mail		/var/mail	ext4	acl,user_xattr	0	2
> -----------------------------------------------------------------------------
> -------------------

What are the devices under /, swap and /boot? All of them use normal disks not
lv, right?

I'd like to try the same setup in local, and it would be better if you can show
the outputs of pvs/vgs/lvs, thanks.


You are receiving this mail because: