From owner-freebsd-questions@FreeBSD.ORG Wed Jul 29 08:36:54 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 4BAEE106564A for ; Wed, 29 Jul 2009 08:36:54 +0000 (UTC) (envelope-from mirror176@cox.net) Received: from fed1rmmtao103.cox.net (fed1rmmtao103.cox.net [68.230.241.43]) by mx1.freebsd.org (Postfix) with ESMTP id 0E7498FC1A for ; Wed, 29 Jul 2009 08:36:53 +0000 (UTC) (envelope-from mirror176@cox.net) Received: from fed1rmimpo01.cox.net ([70.169.32.71]) by fed1rmmtao103.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20090729083653.XRF1223.fed1rmmtao103.cox.net@fed1rmimpo01.cox.net> for ; Wed, 29 Jul 2009 04:36:53 -0400 Received: from darkstar.l.net ([98.165.138.223]) by fed1rmimpo01.cox.net with bizsmtp id Mkct1c0034pNzHu03kctX8; Wed, 29 Jul 2009 04:36:53 -0400 X-VR-Score: -60.00 X-Authority-Analysis: v=1.0 c=1 a=6wBvBrFavHgA:10 a=L9Rxc1bb2t7P2rEVOt0A:9 a=bn9W0kg0Vki5rGVp603EXLHZmXIA:4 X-CM-Score: 0.00 Received: from localhost (localhost [127.0.0.1]) (uid 1001) by darkstar.l.net with local; Wed, 29 Jul 2009 01:36:52 -0700 id 00017A53.4A700A24.0000F905 From: "Edward Sanford Sutton, III" To: freebsd-questions@freebsd.org Date: Wed, 29 Jul 2009 01:36:52 -0700 User-Agent: KMail/1.9.10 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200907290136.52614.mirror176@cox.net> Subject: fsck and dump freeze freebsd. any ideas? 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: Wed, 29 Jul 2009 08:36:54 -0000 The smartctl tests on the three drives came back saying they were checked 100% without error; bad sectors have always caused an error and an aborted scan at the point of trouble for me in the past. I 'thought' I recalled seeing a panic along the lines of ffs_free or something related to free blocks or something at one point; maybe that was an error with fsck on the live system when manually ran. I will try to reproduce. Otherwise I do not know that fsck crashes; the entire system locks. I will see if I can reproduce the problem as a panic. There were some errors fsck seems to think it cleaned. A couple still exist indicating wrong counts about '12 should be 4' or '4 should be 0' type stuff. One error had a ridiculously large seven digit or so number that fsck said should be reduced. I had made a many terabyte file with a dd write to the end of a file of the largest size it would let me create and have since deleted the file; maybe that was what the reference was to. After fixing some errors, the fsck still causes a freeze and at what seems to be about the same point. The filesystem was unmounted for the dump and fsck has been attempted both mounted and unmounted. The filesystem has (ufs, NFS exported, local, soft-updates) reported for features by mount under normal operation. The freeze with dump did occur during a snapshot creation, which I found I cannot kill with a -9 (kill attempted minutes before the crash which still would not stop the creation). The powerdown question is more for how to handle an unsafe powerdown/crash on an active system. If I need to read from a partition, would read only leave it completely clean? Is there a way to operate on a file system which is treated as more of a ramdisk of changes and keeps the real partition unmodified (giving results like Faronics deepfreeze software or qemu disks in snapshot mode)? Would a zfs mirror configuration handle the unexpected crash/powerdown? Would it just report and fix the corruption, mention what files/structures weror impacted, offer restore of that data from a recent snapshot, or just say it is time to restore from a backup? Thanks again for the feedback, Ed Sutton