Date: Sun, 18 Aug 2013 17:23:40 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Tim Kientzle <tim@kientzle.com> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, Boris Samorodov <bsam@passap.ru> Subject: Re: /etc/namedb->@ referrs to NIL after crash or typing "reboot" (not shutdown -r) Message-ID: <20130818172340.103eb39e@thor.walstatt.dyndns.org> In-Reply-To: <ABFA719B-EFF5-4F93-B3B2-28395AC164E9@kientzle.com> References: <20130817113636.21346cd2@thor.walstatt.dyndns.org> <520FAE99.8040003@passap.ru> <20130817193517.2bf01dfe@thor.walstatt.dyndns.org> <A89885AB-7819-4F0A-A98E-7C35394CD0A0@kientzle.com> <20130817201750.4cc9907b@thor.walstatt.dyndns.org> <ABFA719B-EFF5-4F93-B3B2-28395AC164E9@kientzle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/y0V=HmOQb.K14DMEdkss0+b Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Sat, 17 Aug 2013 11:41:08 -0700 Tim Kientzle <tim@kientzle.com> wrote: >=20 > On Aug 17, 2013, at 11:17 AM, O. Hartmann wrote: >=20 > > On Sat, 17 Aug 2013 10:42:07 -0700 > > Tim Kientzle <tim@kientzle.com> wrote: > >=20 > >>=20 > >> On Aug 17, 2013, at 10:35 AM, O. Hartmann wrote: > >>=20 > >>> On Sat, 17 Aug 2013 21:10:49 +0400 > >>> Boris Samorodov <bsam@passap.ru> wrote: > >>>=20 > >>>> 17.08.2013 13:36, O. Hartmann =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > >>>>=20 > >>>>> I can reproduceable truncate the link in /etc/ to be NIL by > >>>>> typing simply "reboot" when rebooting the box > >>>>=20 > >>>> Does it make any difference if you use "shutdown -r" instead? > >>>>=20 > >>>=20 > >>> Yes, when using "shutdown -r" the link isn't broken and the system > >>> reboots and operates as expected. Only if I use the "quick and > >>> dirty way" via "reboot" or after a crash when service named ahs > >>> already been started the link is dead. If a crahs occurs BEFORE > >>> service named has been started, the recovery is also operable - > >>> this is my observation. > >>=20 > >> Does "reboot" show the same problem If the system has been running > >> for a while (at least 15 minutes or so)? > >=20 > > Yes, of course. >=20 > That's not good. Addendum: The reported problem doesn't show up every "reboot". I had to do it now for three times before the broken link showed up (always waiting T > 15 min). I have also to add, that the filesystem in question resides on a SSD (Samsung 830 with 120 GB). >=20 > After 15 minutes, the link contents should have been written > all the way to disk, even on an idle system. It sounds like the > sync process might not be running except at system shutdown. >=20 > What filesystem are you using? ZFS? UFS/SU? SU+J? >=20 > Kernel version? >=20 > Can you reproduce this without named? That is: > * create a symlink,=20 > * wait 15 minutes, > * "reboot" > Is the symlink broken? >=20 > Tim >=20 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" --Sig_/y0V=HmOQb.K14DMEdkss0+b Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQEcBAEBAgAGBQJSEOcAAAoJEOgBcD7A/5N8Kr4H/jMoogDFrW4B772Lw+ffW/ta iHOIpZOfecxBv2cfsFH+OXfXueTuAwD4VqnCWAZMuH3m5jdLJWN7Am53Uuu61wkF 51buyHlFjA8S8o+bRmsQ8n1U/vyfhmQ1ClPr8WHbabeCSw4xJv6Sg9grugU201wV uIkxr6VjdgMPYCKksW00qSPVf5YpTeFgZ+tysibf7losHVmfvEV/VWOUEEOCUofr thPEFnD1lFUZ4Z6/Gl6TLNavNIMbYnsKYmTOltOMTbJBX/Idlot3c6MGXWIpNR38 NSjbQb7kjEwRIFpu4UcdR9szjpLV40YAa3XBSd8XmLdYQQgfNNBeJDE7h2eNYps= =6eXC -----END PGP SIGNATURE----- --Sig_/y0V=HmOQb.K14DMEdkss0+b--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130818172340.103eb39e>