From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 05:18:32 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7DD8FEF3 for ; Sun, 18 May 2014 05:18:32 +0000 (UTC) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 55A7F2A57 for ; Sun, 18 May 2014 05:18:32 +0000 (UTC) Received: from torb.pix.net (torb.pix.net [IPv6:2001:470:e254:10:12dd:b1ff:febf:eca9]) (authenticated bits=0) by hydra.pix.net (8.14.8/8.14.8) with ESMTP id s4I5IUOk048641; Sun, 18 May 2014 01:18:30 -0400 (EDT) (envelope-from lidl@pix.net) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98.1 at mail.pix.net Message-ID: <537842A6.6090904@pix.net> Date: Sun, 18 May 2014 01:18:30 -0400 From: Kurt Lidl User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: hard reset impacts on ufs file system References: <53784122.8090607@elischer.org> In-Reply-To: <53784122.8090607@elischer.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 May 2014 05:18:32 -0000 On 5/18/14 1:12 AM, Julian Elischer wrote: > On 5/16/14, 10:44 PM, Ali Okan YÜKSEL wrote: >> incident: >> == >> file corruption after hard reset on FreeBSD 8.3 >> >> >> details: >> == >> Hard reset examined on freebsd 8.3. after reboot libncurses.so.8 was 0 >> byte. And I couldn't login to system. It gave me error message about >> /bin/sh - libncurses.so.8 corruption. (libncurses depens /bin/sh I guess) >> I found the problem by using fixed shell. >> >> >> solution: >> == >> I copied libncurses.so.8 from another system. When I did it problem >> solved. > Unfortunattely libraries do seem to be one of the more common > victims of this sort of thing but I have never worked out how. > However,as you said, recovery is relatively easy by booting single > user and specifying /rescue/sh as your shell. My original guess as to why this seemed to always happen to libraries was that the system damaged their entries when attempting to update the atime on the files. Two suggestions: turn off atimes, make sure any write-cache on your harddisk(s) is/are turned off. -Kurt