Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing

[Duncan Hare]

Michael
Full DNS is provided by an MS Windows server 2012R2.
Because it is net boot, the network in enabled before the kernel is loaded by 
u-boot,and the kernel starts and mounts the file system over NFS.
Networking parameters, including DNS servers are pass through the kernel 
parameters.
Kernel parms are (these include a lot of raspberry pi stuff), all one line no 
carriage returns

dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs 
rootfstype=nfs nfsrootdebug elevator=deadline rootwait 
nfsroot=192.168.1.10:/nfsroot/r.32.test,tcp,vers=3 
ip=192.168.1.132:192.168.1.10:192.168.1.1:255.255.255.0:abcdef::off:192.168.1.12:192.168.1.22
192,168,1,132 is the raspberry pi machine
192.168.1.10 is the linux file server192.168.1.1 is the default 
gateway255.255.255.0 is the netmaskabcdef is the hostname in this example
192.168.1.12 is one dns server192.168.1.22 is the second dns server
We don't use /dev/nfs in fstab, due to a bug in debian stretch mount command (a 
previous bug report) - which has undergone much change because of the 
introduction of fiilesystem ids replacing device names.

the parameters are completed as above by u-boot script.

U-boot does a dhcp command to get the parameters.

The Linux networking is left as configured in Debian. It can be configured as 
manual or staticin /etc/networking/interfaces with little or no change in 
behavior. If configure with dhcp Linux 
just get another lease on the same Ethernet address, because the 
mac address is the same for u-boot and linux.

In this configuration networking is the prereq to file systems because we are 
booting a ZFS machine, with as much of the file system ro as possibleto have a 
very secure system. At the application layer we plan to run Citrix which 
provides excellent application control. Duncan Hare

714 931 7952

  From: Michael Biebl 
 To: Duncan Hare ; 883...@bugs.debian.org 
 Sent: Thursday, December 7, 2017 3:49 PM
 Subject: Re: Bug#883829: systemd: Fully qualified host names in fstab results 
in mounts failing
   
Control: tags -1 moreinfo
Control: severity -1 normal

Am 08.12.2017 um 00:06 schrieb Duncan Hare:

> browne.danum.local:/nfsroot/b827eb/c23849/home /home  nfs    defaults,rw      
>               0 0    
> tmpfs                                    /tmp    tmpfs  
> nodev,nosuid,size=1%,mode=1777 0 0
> 
> After the failed scenario when boot is complete, This fails after mounting 
> the home 
> directory by shell command:
> 
> sudo mkdir /abc
> sudo mount browne:/nfsroot/b827eb/c23849/home /abc
> 
> and normally this works:
>  
> sudo mkdir /abc
> sudo mount browne:/nfsroot/b827eb/c23849/home abc
> 
> and yes, my local domain suffix is .local, becuse it is a Microsoft domain.

How exactly do you configure your network (do you use ifupdown,
network-manager, something else)? Please share those exact configuration.

How exactly do you resolve those local names? Is that really a DNS or a
MDNS name? Do you have a local resolver running?


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


   ___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: Re: Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #883829 [systemd] systemd: Fully qualified host names in fstab results in 
mounts failing
Added tag(s) moreinfo.
> severity -1 normal
Bug #883829 [systemd] systemd: Fully qualified host names in fstab results in 
mounts failing
Severity set to 'normal' from 'grave'

-- 
883829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing

[Michael Biebl]

Control: tags -1 moreinfo
Control: severity -1 normal

Am 08.12.2017 um 00:06 schrieb Duncan Hare:

> browne.danum.local:/nfsroot/b827eb/c23849/home /home   nfs defaults,rw
> 0 0 
> tmpfs/tmptmpfs   
> nodev,nosuid,size=1%,mode=1777 0 0
> 
> After the failed scenario when boot is complete, This fails after mounting 
> the home 
> directory by shell command:
> 
> sudo mkdir /abc
> sudo mount browne:/nfsroot/b827eb/c23849/home /abc
> 
> and normally this works:
>  
> sudo mkdir /abc
> sudo mount browne:/nfsroot/b827eb/c23849/home abc
> 
> and yes, my local domain suffix is .local, becuse it is a Microsoft domain.

How exactly do you configure your network (do you use ifupdown,
network-manager, something else)? Please share those exact configuration.

How exactly do you resolve those local names? Is that really a DNS or a
MDNS name? Do you have a local resolver running?


-- 
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
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

[bts-link] source package systemd

[bts-link-upstream]

#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #883380 (http://bugs.debian.org/883380)
# Bug title: systemd 235 segfaults when using BindPaths or BindReadOnlyPaths
#  * https://github.com/systemd/systemd/issues/7055
#  * remote status changed: (?) -> closed
usertags 883380 + status-closed

thanks

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers