Control: severity -1 important
Control: tag -1 moreinfo
On Fri, 2017-12-08 at 13:31 -0800, Duncan Hare wrote:
> Package: nfs-common
> Version: 1:1.3.4-2.1
> Severity: grave
> Justification: renders package unusable
>
> File systems correctly mounted after "reached target network online"
>
> File systema rw in both cases.
>
> Case 1
>
> 1. I deleted resolv.conf
> 2. Root fs rw in fstab
> 3. File systems mounted by IP address
> 4. resolve.conf built by end of boot when login possible
>
> proc /proc proc defaults 0 0
> /dev/mmcblk0p1 /boot vfat defaults,ro 0 2
> #PARTUUID=62bc0a1f-02 / ext4 defaults,noatime 0 1
> 192.168.1.10:/nfsroot/r.32.test / nfs defaults,rw 0 0
> 192.168.1.10:/nfsroot/b827eb/c23849/var /var nfs defaults,rw 0 0
> 192.168.1.10:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0
> #browne.danum.local:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0
Is that a regular DNS name? The .local LTD is reserved for mDNS, so
it's not good practice to use it for regular DNS. But I doubt that has
anything to do with the problem.
As you say resolv.conf is built during boot, I assume the DNS server is
remote and is discovered through DHCP. Is that correct?
[...]
> Conclusion: name resolution, dns lookup, is not performed at fstbab mount time.
>
> This is supposed to work. Who's issue is this? systemd or mount?
It does work, in general.
The problem is likely to be in the systemd configuration. Quoting
systemd.mount(5):
· Network mount units automatically acquire After= dependencies on
remote-fs-pre.target, network.target and network-online.target.
Towards the latter a Wants= unit is added as well.
Depending on which network configuration tools you use, you might need
to define additional dependencies for network-online.target or
remote-fs-pre.target.
Ben.
--
Ben Hutchings
Quantity is no substitute for quality, but it's the only one we've got.
Attachment:
signature.asc
Description: This is a digitally signed message part