Bug#850436: mounting var at boot: Mount point is not empty

[Michael Biebl]

Am 29.04.2017 um 08:45 schrieb Daniel Pocock:
> 
> 
> On 06/01/17 15:24, Michael Biebl 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?
>>
> 
> No, I don't know when they are created.
> 

Can you check the timestamps and correlate that with a shutdown or boot?

>> 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?
>>
> 
> 
> Can you propose a way to test this or tell me what other data to
> submit to help analyze the problem?
> 
> I can do another reboot test on this machine, but probably not until
> after my next trip.

I would clean up the files to check if they are re-created, this should
also let you answer the question above, i.e. when the files are created.
In this case, attach a journal log from the boot (or shutdown).


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20170429/9324533d/attachment-0002.sig>