From owner-freebsd-fs@FreeBSD.ORG Fri Dec 7 14:45:33 2007 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB6F716A417 for ; Fri, 7 Dec 2007 14:45:33 +0000 (UTC) (envelope-from julien.bellang@free.fr) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by mx1.freebsd.org (Postfix) with ESMTP id 7E86913C4EA for ; Fri, 7 Dec 2007 14:45:33 +0000 (UTC) (envelope-from julien.bellang@free.fr) Received: from smtp1-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp1-g19.free.fr (Postfix) with ESMTP id 6E5EE1AB2B1; Fri, 7 Dec 2007 15:45:32 +0100 (CET) Received: from [127.0.0.1] (vil35-2-82-227-204-7.fbx.proxad.net [82.227.204.7]) by smtp1-g19.free.fr (Postfix) with ESMTP id 0BD351AB2FC; Fri, 7 Dec 2007 15:45:31 +0100 (CET) Message-ID: <47595C8C.6060203@free.fr> Date: Fri, 07 Dec 2007 15:45:32 +0100 From: julien User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Jim Rees References: <1196788551.47558b47ee317@imp.free.fr> <86d4tiu0ui.fsf@ds4.des.no> <20071207125852.GC6665@citi.umich.edu> In-Reply-To: <20071207125852.GC6665@citi.umich.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 071206-0, 06/12/2007), Outbound message X-Antivirus-Status: Clean Cc: freebsd-fs@freebsd.org, =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= Subject: Re: FSCK failed does'nt correct file size when INCORRECT BLOCK COUNT is found X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Dec 2007 14:45:33 -0000 I can't get a UPS in my environment. I already tested with the write cache desactivated, but the problem still the same, I obtain files with holes and incorrect size and blockcount. The only difference is that there is less holes and performance are falling down. The problem is really easy to reproduce, you have just to copy several big files and shutdown the power in the midle of the copy. Jim Rees a écrit : > Dag-Erling Smørgrav wrote: > > Get a UPS. > > We should strive to prevent data corruption in the face of unexpected system > shutdown. Having a user who loses power several times a week seems useful > for testing, especially when he is willing to delve into fsck sources and > figure out what's going on. My recommendation would be to turn off caching > in the disk and report back in a couple of weeks. > > >