Bug#851402: failed unmounting /var during shutdown

Michael Biebl biebl at debian.org
Wed Jan 18 10:17:11 GMT 2017


Control: forwarded -1 https://github.com/systemd/systemd/issues/867
Control: tags -1 - moreinfo
Control: severity -1 normal

Am 14.01.2017 um 16:37 schrieb Daniel Pocock:
> Package: systemd
> Version: 232-8
> Severity: important
> 
> 
> The box is running stretch, updated from jessie yesterday.
> 
> When the box shuts down, it unmounts all the filesystems.
> 
> When it gets to /var there is a warning: Failed unmounting /var
> 
> 
> I wrote a little wrapper script to put in place of /bin/umount, it calls
> lsof to show what is going on before the real umount call
> 
> The only open files on /var at the time of unmounting appear to be
> journalctl files
> 
> Is this expected?  Is some manual configuration needed to make sure /var
> is unmounted later or should systemd / journald behave better in this
> situation?

Ok this seems to be https://github.com/systemd/systemd/issues/867

Marking accordingly. As we unmount /var in the systemd-shutdown binary,
I'm downgrading the severity (as it's mostly a cosmetic issue)

-- 
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/20170118/73c18498/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list