Date: Mon, 5 Jul 2010 13:15:59 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Steve Franks <bahamasfranks@gmail.com> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: syncer hemorrhages numbers on shutdown then panics Message-ID: <alpine.BSF.2.00.1007051251530.7389@wonkity.com> In-Reply-To: <AANLkTiktvPh7MCeSC1RyEa_phS54G7QuaX-4vKExGJMg@mail.gmail.com> References: <AANLkTiktvPh7MCeSC1RyEa_phS54G7QuaX-4vKExGJMg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 Jul 2010, Steve Franks wrote: > I just did a 'new huge disk' procedure (aka dump 0aLf - | restore - > for each label). I have a script for automating it, and it usually > seems to work, but not today! Silent failures/corruptions do not make > me comfortable, especially coming from my backup tools (yes, no errors > seen in log). > > System seems to work, but it won't shutdown! syncher spits out random > numbers for 10 minutes or more then panics. Should I start over? Why > didn't dump/restore unambiguously copy my working disk to my new one? > I didn't see any expicit errors... > > Also, X won't start, complaining about inability to write something > for the keymap into /tmp; probably part of the same problem. Maybe missing permissions on /tmp? In my case, when I don't bother to copy /tmp, create a new /tmp on the target, then forget to set permissions on it. Wouldn't think that would affect sync, but when you image a system odd things are possible.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1007051251530.7389>