From owner-freebsd-questions@FreeBSD.ORG Mon Jul 5 19:16:01 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 316A1106564A for ; Mon, 5 Jul 2010 19:16:01 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id E07768FC13 for ; Mon, 5 Jul 2010 19:16:00 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id o65JG0YP007506; Mon, 5 Jul 2010 13:16:00 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id o65JFxQb007503; Mon, 5 Jul 2010 13:16:00 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 5 Jul 2010 13:15:59 -0600 (MDT) From: Warren Block To: Steve Franks In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.5 (wonkity.com [127.0.0.1]); Mon, 05 Jul 2010 13:16:00 -0600 (MDT) Cc: FreeBSD Mailing List Subject: Re: syncer hemorrhages numbers on shutdown then panics X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2010 19:16:01 -0000 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.