<html><head></head><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:10px"><div id="yui_3_16_0_ym19_1_1512765432224_6323">Michael</div><div id="yui_3_16_0_ym19_1_1512765432224_6322"><br></div><div id="yui_3_16_0_ym19_1_1512765432224_6692">File systems correctly mounted after "reached target network online"</div><div id="yui_3_16_0_ym19_1_1512765432224_6746"><br></div><div>File systema rw in both cases.<br></div><div id="yui_3_16_0_ym19_1_1512765432224_6744"><br></div><div id="yui_3_16_0_ym19_1_1512765432224_6224">Case 1<br></div><div id="yui_3_16_0_ym19_1_1512765432224_6303"><br></div><div id="yui_3_16_0_ym19_1_1512765432224_6324">1. I deleted resolv.conf</div><div id="yui_3_16_0_ym19_1_1512765432224_6242">2. Root fs rw in fstab</div><div id="yui_3_16_0_ym19_1_1512765432224_6325">3. File systems mounted by IP address<br></div><div id="yui_3_16_0_ym19_1_1512765432224_6326">4. resolve.conf built by end of boot when login possible</div><div id="yui_3_16_0_ym19_1_1512765432224_6537"><br></div><div id="yui_3_16_0_ym19_1_1512765432224_6569" dir="ltr">proc /proc proc defaults 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6587">/dev/mmcblk0p1 /boot vfat defaults,ro 0 2<br id="yui_3_16_0_ym19_1_1512765432224_6588">#PARTUUID=62bc0a1f-02 / ext4 defaults,noatime 0 1<br id="yui_3_16_0_ym19_1_1512765432224_6589">192.168.1.10:/nfsroot/r.32.test / nfs defaults,rw 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6590">192.168.1.10:/nfsroot/b827eb/c23849/var /var nfs defaults,rw 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6591">192.168.1.10:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6592">#browne.danum.local:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6593">tmpfs /tmp tmpfs nodev,nosuid,size=1%,mode=1777 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6594"><br></div><div id="yui_3_16_0_ym19_1_1512765432224_6336">Case 2</div><div id="yui_3_16_0_ym19_1_1512765432224_6338"><br></div><div id="yui_3_16_0_ym19_1_1512765432224_6347">1. I deleted resolv.conf</div><div id="yui_3_16_0_ym19_1_1512765432224_6348">2. Root fs rw in fstab</div><div id="yui_3_16_0_ym19_1_1512765432224_6349">3. File systems mounted by server name<br id="yui_3_16_0_ym19_1_1512765432224_6350"></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512765432224_6351">4. Mount failed.</div><div dir="ltr" id="yui_3_16_0_ym19_1_1512765432224_6595"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512765432224_6611">proc /proc proc defaults 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6628">/dev/mmcblk0p1 /boot vfat defaults,ro 0 2<br id="yui_3_16_0_ym19_1_1512765432224_6629">#PARTUUID=62bc0a1f-02 / ext4 defaults,noatime 0 1<br id="yui_3_16_0_ym19_1_1512765432224_6630">192.168.1.10:/nfsroot/r.32.test / nfs defaults,rw 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6631">192.168.1.10:/nfsroot/b827eb/c23849/var /var nfs defaults,rw 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6632">#192.168.1.10:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6633">browne.danum.local:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6634">tmpfs /tmp tmpfs nodev,nosuid,size=1%,mode=1777 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6635"></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512765432224_6829"><br></div><div id="yui_3_16_0_ym19_1_1512765432224_6849">Case 2</div><div id="yui_3_16_0_ym19_1_1512765432224_6850"><br id="yui_3_16_0_ym19_1_1512765432224_6851"></div><div id="yui_3_16_0_ym19_1_1512765432224_6852">1. resolv.conf not deleted.<br></div><div id="yui_3_16_0_ym19_1_1512765432224_6853">2. Root fs rw in fstab</div><div id="yui_3_16_0_ym19_1_1512765432224_6854">3. File systems mounted by server name<br id="yui_3_16_0_ym19_1_1512765432224_6855"></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512765432224_6856">4. Mount failed.</div><div dir="ltr" id="yui_3_16_0_ym19_1_1512765432224_6857"><br id="yui_3_16_0_ym19_1_1512765432224_6858"></div>proc /proc proc defaults 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6859">/dev/mmcblk0p1 /boot vfat defaults,ro 0 2<br id="yui_3_16_0_ym19_1_1512765432224_6860">#PARTUUID=62bc0a1f-02 / ext4 defaults,noatime 0 1<br id="yui_3_16_0_ym19_1_1512765432224_6861">192.168.1.10:/nfsroot/r.32.test / nfs defaults,rw 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6862">192.168.1.10:/nfsroot/b827eb/c23849/var /var nfs defaults,rw 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6863">#192.168.1.10:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6864">browne.danum.local:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0<br id="yui_3_16_0_ym19_1_1512765432224_6865">tmpfs /tmp tmpfs nodev,nosuid,size=1%,mode=1777 0 0<div dir="ltr" id="yui_3_16_0_ym19_1_1512765432224_6596"><br></div><div dir="ltr" id="yui_3_16_0_ym19_1_1512765432224_6597">Conclusion: name resolution, dns lookup, is not performed at fstbab mount time.<br></div><div id="yui_3_16_0_ym19_1_1512765432224_6331"><br></div><div id="yui_3_16_0_ym19_1_1512765432224_6676">This is supposed to work. Who's issue is this? systemd or mount?</div><div id="yui_3_16_0_ym19_1_1512765432224_6677"><br></div><div id="yui_3_16_0_ym19_1_1512765432224_6678">Thanks<br></div><div id="yui_3_16_0_ym19_1_1512765432224_6143"> </div><div class="signature" id="yui_3_16_0_ym19_1_1512765432224_6144">Duncan Hare<br><br>714 931 7952</div><div class="qtdSeparateBR" id="yui_3_16_0_ym19_1_1512765432224_6216"><br><br></div><div class="yahoo_quoted" id="yui_3_16_0_ym19_1_1512765432224_6220" style="display: block;"> <div style="font-family: verdana, helvetica, sans-serif; font-size: 10px;" id="yui_3_16_0_ym19_1_1512765432224_6219"> <div style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;" id="yui_3_16_0_ym19_1_1512765432224_6218"> <div dir="ltr" id="yui_3_16_0_ym19_1_1512765432224_6217"> <font id="yui_3_16_0_ym19_1_1512765432224_6223" face="Arial" size="2"> <hr id="yui_3_16_0_ym19_1_1512765432224_6222" size="1"> <b><span style="font-weight:bold;">From:</span></b> Debian Bug Tracking System <owner@bugs.debian.org><br> <b><span style="font-weight: bold;">To:</span></b> Duncan Hare <dh@synoia.com> <br> <b><span style="font-weight: bold;">Sent:</span></b> Friday, December 8, 2017 12:30 PM<br> <b><span style="font-weight: bold;">Subject:</span></b> Bug#883829 closed by Michael Biebl <biebl@debian.org> (Re: Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing)<br> </font> </div> <div class="y_msg_container" id="yui_3_16_0_ym19_1_1512765432224_6812"><br>This is an automatic notification regarding your Bug report<br>which was filed against the systemd package:<br><br>#883829: systemd: Fully qualified host names in fstab results in mounts failing<br><br>It has been closed by Michael Biebl <<a ymailto="mailto:biebl@debian.org" href="mailto:biebl@debian.org">biebl@debian.org</a>>.<br><br>Their explanation is attached below along with your original report.<br>If this explanation is unsatisfactory and you have not received a<br>better one in a separate message then please contact Michael Biebl <<a ymailto="mailto:biebl@debian.org" href="mailto:biebl@debian.org">biebl@debian.org</a>> by<br>replying to this email.<br><br><br>-- <br>883829: <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883829" target="_blank">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883829</a><br>Debian Bug Tracking System<br>Contact <a ymailto="mailto:owner@bugs.debian.org" href="mailto:owner@bugs.debian.org">owner@bugs.debian.org</a> with problems<div id="ymsg04743" class="ymsg1849035851" src="mid://ACOUxAoAABQeWir2UQP_cKS318g/2"><div dir="ltr">Am 08.12.2017 um 20:43 schrieb Duncan Hare:<br></div><div dir="ltr">> Michael<br></div><div dir="ltr">> <br></div><div dir="ltr">> u-boot is a bootloader. The u-boot script load the kernel from a<br></div><div dir="ltr">> server,, constructs the kernel commandline,<br></div><div dir="ltr">> and the u-boot script is complete when the kernel starts, well before<br></div><div dir="ltr">> these failures.<br></div><div dir="ltr">> <br></div><div dir="ltr">> In the kernel command line there is a dns server address, 192.168.1.12<br></div><div dir="ltr">> passed to the linux kernel on the kernel command line. <br></div><div dir="ltr">> <br></div><div dir="ltr">> How the DNS server address is passed to resolveconf by the kernal I do<br></div><div dir="ltr">> not know. That's an interface between the kernel and systemd.<br></div><div dir="ltr">> <br></div><div dir="ltr"><br></div><div dir="ltr">Nope, systemd is not directly involved in this.<br></div><div dir="ltr">In any case, this is nothing systemd can fix for you, thus closing.<br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr"><br></div><div dir="ltr">-- <br></div><div dir="ltr">Why is it that all of the instruments seeking intelligent life in the<br></div><div dir="ltr">universe are pointed away from Earth?<br></div></div><div id="ymsg04988" class="ymsg1849035851" src="mid://ACOUxAoAABQeWir2UQP_cKS318g/3">Package: systemd<br>Version: 232-25+deb9u1<br>Severity: grave<br>Justification: causes non-serious data loss<br><br>This works, the home directory gets mounted<br><br>proc /proc proc defaults 0 0<br>/dev/mmcblk0p1 /boot vfat defaults,ro 0 2<br>#PARTUUID=62bc0a1f-02 / ext4 defaults,noatime 0 1<br>192.168.1.10:/nfsroot/r.32.test / nfs defaults,rw 0 0<br>192.168.1.10:/nfsroot/b827eb/c23849/var /var nfs defaults,rw 0 0<br>192.168.1.10:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0 <br>tmpfs /tmp tmpfs nodev,nosuid,size=1%,mode=1777 0 0<br><br>This /home mount fails, probably becuse no dns lookup is performed. It is supposed to work:<br><br><br>proc /proc proc defaults 0 0<br>/dev/mmcblk0p1 /boot vfat defaults,ro 0 2<br>#PARTUUID=62bc0a1f-02 / ext4 defaults,noatime 0 1<br>192.168.1.10:/nfsroot/r.32.test / nfs defaults,rw 0 0<br>192.168.1.10:/nfsroot/b827eb/c23849/var /var nfs defaults,rw 0 0<br>browne.danum.local:/nfsroot/b827eb/c23849/home /home nfs defaults,rw 0 0 <br>tmpfs /tmp tmpfs nodev,nosuid,size=1%,mode=1777 0 0<br><br>After the failed scenario when boot is complete, This fails after mounting the home <br>directory by shell command:<br><br>sudo mkdir /abc<br>sudo mount browne:/nfsroot/b827eb/c23849/home /abc<br><br>and normally this works:<br> <br>sudo mkdir /abc<br>sudo mount browne:/nfsroot/b827eb/c23849/home abc<br><br>and yes, my local domain suffix is .local, becuse it is a Microsoft domain.<br><br><br><br>-- Package-specific info:<br><br>-- System Information:<br>Distributor ID: Raspbian<br>Description: Raspbian GNU/Linux 9.1 (stretch)<br>Release: 9.1<br>Codename: stretch<br>Architecture: armv7l<br><br>Kernel: Linux 4.9.59-v7+ (SMP w/4 CPU cores)<br>Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)<br>Shell: /bin/sh linked to /bin/dash<br>Init: systemd (via /run/systemd/system)<br><br>Versions of packages systemd depends on:<br>ii adduser 3.115<br>ii libacl1 2.2.52-3<br>ii libapparmor1 2.11.0-3<br>ii libaudit1 1:2.6.7-2<br>ii libblkid1 2.29.2-1<br>ii libc6 2.24-11+deb9u1<br>ii libcap2 1:2.25-1<br>ii libcryptsetup4 2:1.7.3-4<br>ii libgcc1 1:6.3.0-18+rpi1<br>ii libgcrypt20 1.7.6-2+deb9u2<br>ii libgpg-error0 1.26-2<br>ii libidn11 1.33-1<br>ii libip4tc0 1.6.0+snapshot20161117-6<br>ii libkmod2 23-2<br>ii liblz4-1 0.0~r131-2<br>ii liblzma5 5.2.2-1.2<br>ii libmount1 2.29.2-1<br>ii libpam0g 1.1.8-3.6+rpi1<br>ii libseccomp2 2.3.1-2.1<br>ii libselinux1 2.6-3<br>ii libsystemd0 232-25+deb9u1<br>ii mount 2.29.2-1<br>ii procps 2:3.3.12-3<br>ii util-linux 2.29.2-1<br><br>Versions of packages systemd recommends:<br>ii dbus 1.10.22-0+deb9u1<br>ii libpam-systemd 232-25+deb9u1<br><br>Versions of packages systemd suggests:<br>ii policykit-1 0.105-18<br>pn systemd-container <none><br>pn systemd-ui <none><br><br>Versions of packages systemd is related to:<br>pn dracut <none><br>ii initramfs-tools 0.130<br>ii udev 232-25+deb9u1<br><br>-- no debconf information<br></div><br><br></div> </div> </div> </div></div></body></html>