From owner-freebsd-hackers@FreeBSD.ORG Sun May 18 05:12:15 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 A2D07D84; Sun, 18 May 2014 05:12:15 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E3B22A34; Sun, 18 May 2014 05:12:14 +0000 (UTC) Received: from jre-mbp.elischer.org (ppp121-45-232-70.lns20.per1.internode.on.net [121.45.232.70]) (authenticated bits=0) by vps1.elischer.org (8.14.8/8.14.8) with ESMTP id s4I5C8vb053752 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sat, 17 May 2014 22:12:12 -0700 (PDT) (envelope-from julian@elischer.org) Message-ID: <53784122.8090607@elischer.org> Date: Sun, 18 May 2014 13:12:02 +0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: =?UTF-8?B?QWxpIE9rYW4gWcOcS1NFTA==?= , freebsd-hackers@freebsd.org Subject: Re: hard reset impacts on ufs file system References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: fs@freebsd.org 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:12:15 -0000 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. > > > question: > == > Is it known situation? Did you ever live a problem like this? yeas I have seen similar. I don't know why libraries are in that state though. > > > > Kind regards, > Ali Okan Yüksel > > > >