From owner-freebsd-fs@FreeBSD.ORG Tue Apr 24 14:37:48 2012 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 353EA106566B for ; Tue, 24 Apr 2012 14:37:48 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by mx1.freebsd.org (Postfix) with ESMTP id BB3AC8FC0C for ; Tue, 24 Apr 2012 14:37:47 +0000 (UTC) Received: from [10.3.0.26] ([141.4.215.32]) by mrelayeu.kundenserver.de (node=mrbap4) with ESMTP (Nemesis) id 0LiCJf-1RrQVt07VL-00nOJ7; Tue, 24 Apr 2012 16:37:46 +0200 Message-ID: <4F96BAB9.9080303@brockmann-consult.de> Date: Tue, 24 Apr 2012 16:37:45 +0200 From: Peter Maloney User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120312 Thunderbird/11.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <20120424143014.GA2865@johnny.reilly.home> In-Reply-To: <20120424143014.GA2865@johnny.reilly.home> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:AZ6zxXU/WWIgbI5EIi3MkooTTi+vD18LV92C6qCFBT3 niH1HLhyw3l3q719+oAlMOt0p6bWb6OWXGS7omHs0kpalo6Lx1 8q+V0FZVyqvy0Em7RGg38Nb/zk1CjdgPdh+YceLr8izzz4hfpA CyIlFuFew7SrL2skPKnekCzfGPu1ArgrKLc6hd3/K24CQsRn6f UbONfi9AylT4+ruvVTiH6KMSuB4Ymeu3JOLkeGMUodQLruBPW6 aYP9p5RRgio2rk4lgKmgNU5C3OCalqZIpb0tELRM5yrPKwy4U4 BMSI0ol7zm1NHbqezPkT39piXI7QA52pvj6U3W9SVuu10cH2fQ 8Pj76BM1TXRw470d1lZB3YlHM7H1x5LjAPWYI35rU Subject: Re: Odd file system corruption in ZFS pool 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: Tue, 24 Apr 2012 14:37:48 -0000 On 04/24/2012 04:30 PM, Andrew Reilly wrote: > ZFS filesystem version 5 > ZFS storage pool version 28 Is there anything special about your pool? Was it created in an old FreeBSD and upgraded? Was it send/recv'd from OpenSolaris? etc. So far the only corruption I had was the result of installing FreeBSD on a 4 GB USB flash stick. It had no redundancy, and within a few months, some files were spontaneously broken. And in that one instance I found that move, copy, etc. on broken files reported by zpool status -v will always fail. Only "rm" worked for me. So I suggest you try rmdir or rm -r.