/etc/namedb->@ referrs to NIL after crash or typing "reboot" (not shutdown -r)

[John Baldwin]

On Saturday, August 17, 2013 1:42:07 pm Tim Kientzle wrote:
> 
> On Aug 17, 2013, at 10:35 AM, O. Hartmann wrote:
> 
> > On Sat, 17 Aug 2013 21:10:49 +0400
> > Boris Samorodov <bsam at passap.ru> wrote:
> > 
> >> 17.08.2013 13:36, O. Hartmann пишет:
> >> 
> >>> I can reproduceable truncate the link in /etc/ to be NIL by typing
> >>> simply "reboot" when rebooting the box
> >> 
> >> Does it make any difference if you use "shutdown -r" instead?
> >> 
> > 
> > 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.
> 
> Does "reboot" show the same problem If the system has been running
> for a while (at least 15 minutes or so)?
> 
> 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 should 
still be synced if you do a reboot.  Only a panic or power failure should give 
you unsynced disks.

-- 
John Baldwin