From owner-freebsd-current@FreeBSD.ORG Mon Aug 19 18:39:34 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 33C9DA3C for ; Mon, 19 Aug 2013 18:39:34 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CE9442103 for ; Mon, 19 Aug 2013 18:39:33 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 57891B91A; Mon, 19 Aug 2013 14:39:31 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Subject: Re: /etc/namedb->@ referrs to NIL after crash or typing "reboot" (not shutdown -r) Date: Mon, 19 Aug 2013 13:58:40 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p28; KDE/4.5.5; amd64; ; ) References: <20130817113636.21346cd2@thor.walstatt.dyndns.org> <20130817193517.2bf01dfe@thor.walstatt.dyndns.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201308191358.40555.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 19 Aug 2013 14:39:31 -0400 (EDT) Cc: "O. Hartmann" , Boris Samorodov X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Aug 2013 18:39:34 -0000 On Saturday, August 17, 2013 1:42:07 pm Tim Kientzle wrote: >=20 > On Aug 17, 2013, at 10:35 AM, O. Hartmann wrote: >=20 > > On Sat, 17 Aug 2013 21:10:49 +0400 > > Boris Samorodov 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 > Your broken link sounds like the expected behavior when you > do a dirty reboot shortly after the link has been created (before > the link contents have been written all the way to disk). "reboot" shouldn't be a dirty reboot in this sense though. The disks shoul= d=20 still be synced if you do a reboot. Only a panic or power failure should g= ive=20 you unsynced disks. =2D-=20 John Baldwin