Your message dated Fri, 28 Apr 2017 22:03:18 +0200
with message-id <cdc4b431-d16f-8773-11f9-716fba6f1...@debian.org>
and subject line Re: Bug#850436: mounting var at boot: Mount point is not empty
has caused the Debian Bug report #850436,
regarding mounting var at boot: Mount point is not empty
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
850436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 215-17+deb8u5
When my system is booting, I see the following:
systemd[1]: var.mount: Directory /var to mount over is not empty,
mounting anyway.
-- Subject: Mount point is not empty
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The directory /var 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.
I mounted the root filesystem a second time in a different location:
mkdir /tmp/root-fs
mount /dev/mapper/vg00-root /tmp/root-fs
cd /tmp/root-fs
and looked at what exists under var:
root-fs/var
root-fs/var/lib
root-fs/var/lib/systemd
root-fs/var/lib/systemd/random-seed
root-fs/var/log
root-fs/var/log/unattended-upgrades
root-fs/var/log/unattended-upgrades/unattended-upgrades-shutdown.log
root-fs/var/run
root-fs/var/run/avahi-daemon
root-fs/var/run/unattended-upgrades.lock
I went to single user mode, unmounted /var, removed those files and they
problem occurs again on the next boot, they are being created again.
Are any of these files important? Do I need to change anything in the
way I mount my filesystems?
This is in /etc/fstab:
/dev/mapper/vg00-root / ext4 errors=remount-ro,noatime
0 1
/dev/mapper/vg00-var /var ext4 defaults 0 2
--- End Message ---
--- Begin Message ---
On Fri, 6 Jan 2017 15:24:14 +0100 Michael Biebl <bi...@debian.org> wrote:
> Am 06.01.2017 um 15:12 schrieb Daniel Pocock:
> > root-fs/var/lib/systemd/random-seed
>
>
> > root-fs/var/log/unattended-upgrades/unattended-upgrades-shutdown.log
>
> > root-fs/var/run/avahi-daemon
> > root-fs/var/run/unattended-upgrades.lock
>
>
> Do you know, when those files are created?
>
> E.g. systemd-random-seed.service has
> RequiresMountsFor=/var/lib/systemd/random-seed
>
> So it should only be started after /var has been mounted.
> Is this maybe an issue during shutdown, where /var is umounted too early?
>
Since we didn't get further feedback, I'm closing this bug report.
Please reopen if you are available to further debug this.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
