(I hope it's ok quote that from your logs, if so I'd bounce them to the bug report)
Am 21.07.2014 um 23:39 schrieb Michael Biebl:
> Am 21.07.2014 14:39, schrieb Martin Steigerwald:
>> Package: systemd
>> Version: 208-1
>> Severity: important
>>
>> Dear Maintainer,
>>
>> after booting with systemd 208-1 the more important one of two NFS exports
>> is not mounted. /home (on NetApp FAS) is not mounted, while /somenfs
>> (on Linux NFS server) is:
>>
>
>
> Please include your network configuration.
>
> Please also attach the output of systemd-analyze dump
>
The journalctl output shows, that the failing nfs mount is attempted
before networking.service/network.target has finished.
Looking at the systemd-analyse dump, specifically the relevant units,
then one sess that Unit datengrab.mount misses an ordering against
network.target
After: systemd-journald.socket
After: local-fs-pre.target
After: system.slice
After: -.mount
Looking at the reverse, i.e Unit network.target, it has
Before: home.mount
Before: mnt-gruppen.mount
Before: mnt-linuximages.mount
I.e. datengrab.mount is missing there, as well.
It looks like datengrab.mount is not detected as remote file system.
You can make that explicit, by adding "_netdev" to the mount options.
May guess is, that it's due to the usage of "nfs,sec=sys" as fs type.
To me this looks like a misconfiguration "sec=sys" should be listed
under mount options, not under fstype.
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
