From owner-freebsd-questions@FreeBSD.ORG Wed Jul 29 06:38:36 2009 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 794A0106564A for ; Wed, 29 Jul 2009 06:38:36 +0000 (UTC) (envelope-from D.Forsyth@ru.ac.za) Received: from b.mail.ru.ac.za (b.mail.ru.ac.za [IPv6:2001:4200:1010::25:2]) by mx1.freebsd.org (Postfix) with ESMTP id B8A668FC14 for ; Wed, 29 Jul 2009 06:38:35 +0000 (UTC) (envelope-from D.Forsyth@ru.ac.za) Received: from iwr.ru.ac.za ([146.231.64.249]:57081) by b.mail.ru.ac.za with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MW2o4-000GbP-LF; Wed, 29 Jul 2009 08:38:32 +0200 Received: from iwdf-5.iwr.ru.ac.za ([146.231.64.28]) by iwr.ru.ac.za with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MW2o4-000812-JZ; Wed, 29 Jul 2009 08:38:32 +0200 From: "DA Forsyth" Organization: IWR To: freebsd-questions@freebsd.org Date: Wed, 29 Jul 2009 08:38:32 +0200 MIME-Version: 1.0 Message-ID: <4A700A88.15248.4747C6A@d.forsyth.ru.ac.za> Priority: normal In-reply-to: <20090729055906.DB1051065696@hub.freebsd.org> References: <20090729055906.DB1051065696@hub.freebsd.org> X-mailer: Pegasus Mail for Windows (4.41) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: b.mail.ru.ac.za (146.231.129.34) Cc: mirror176@cox.net Subject: Re: fsck and dump freeze freebsd. any ideas? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d.forsyth@ru.ac.za List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jul 2009 06:38:36 -0000 On 29 Jul 2009 , freebsd-questions-request@freebsd.org entreated about "freebsd-questions Digest, Vol 269, Issue 6": > After one of the last crashes, the system would lock up a short time > after rebooting. I found the problem caused by background fsck locking > up the system. I took the partition out of the startup check for now. > I 'think' I was installing a port during the last crash, but it has > been a while. I performed a fsck and a dump (to /dev/null) confirming > that both do crash the freebsd 7.2 and 6.2 (which I booted off of a > separate drive). A tar to /dev/null did run successfully, but I recall > reading that that is not a recommended way to backup/move a > filesystem. The /usr partition where it causes trouble is in a raid5 > geom_vinum three drive array. I did not yet have the array rebuild the My experience has been that dump *with snapshot* of a live filesystem will crash if the filesystem is 'large'. MY solution is to umount the partition. This happens with my 800GB /home which is part of a 4 drive raid5 array (ar driver with hardware setup). It used to happen with the previous 320GB mirror array too, just with /home which is the biggest partition. This is one reason I moved away from tape backup to a secondary server full of harddrives as backup target, the tape took far too long with /home unmounted and users were affected. As for the fsck crashing, I'm lost. Maybe a faulty drive? -- DA Fo rsyth Network Supervisor Principal Technical Officer -- Institute for Water Research http://www.ru.ac.za/institutes/iwr/