From owner-freebsd-fs@FreeBSD.ORG Fri Mar 16 17:06:08 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5436D106564A for ; Fri, 16 Mar 2012 17:06:08 +0000 (UTC) (envelope-from peter.maloney@brockmann-consult.de) Received: from mo-p05-ob6.rzone.de (mo-p05-ob6.rzone.de [IPv6:2a01:238:20a:202:53f5::1]) by mx1.freebsd.org (Postfix) with ESMTP id AC6F48FC15 for ; Fri, 16 Mar 2012 17:06:07 +0000 (UTC) X-RZG-AUTH: :LWIKdA2leu0bPbLmhzXgqn0MTG6qiKEwQRWfNxSw4HzYIwjsnvdDt2oX8drk23mo2zRGKX0o X-RZG-CLASS-ID: mo05 Received: from [192.168.179.39] (hmbg-5f764970.pool.mediaWays.net [95.118.73.112]) by smtp.strato.de (fruni mo10) (RZmta 28.1 DYNA|AUTH) with (DHE-RSA-AES128-SHA encrypted) ESMTPA id 904941o2GFWB26 for ; Fri, 16 Mar 2012 18:06:05 +0100 (MET) Message-ID: <4F6372FC.5060507@brockmann-consult.de> Date: Fri, 16 Mar 2012 18:06:04 +0100 From: Peter Maloney User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <1397E951-AE82-4425-9338-3748E5ACC0D4@pean.org> <545ACC9D-EB12-4F8F-B8A9-5706AE57296E@pean.org> In-Reply-To: <545ACC9D-EB12-4F8F-B8A9-5706AE57296E@pean.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: Problem with corrupted file on raidz. 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, 16 Mar 2012 17:06:08 -0000 Am 14.03.2012 05:52, schrieb Peter Ankerstål: > Ok, yes. Removing the file and THEN scrub did the tricks here. But I'm still confused how this could have happened in the first place. Confused about what part? ZFS handling it, or what caused your file to get damaged despite redundancy? Did you have checksum/other errors on other devices? If multiple had damage just by chance in the same spot, it would damage a file... but did this unlikely occurance actually occur? eg. NAME STATE READ WRITE CKSUM store ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada0 ONLINE 0 0 0 ada1 ONLINE 0 0 5 ada2 ONLINE 0 0 7 Perhaps one device was offline/unavail while the file was created and damaged so the offline disk had no redundancy? eg. NAME STATE READ WRITE CKSUM store DEGRADED 0 0 0 raidz1-0 DEGRADED 0 0 0 ada0 ONLINE 0 0 0 ada1 ONLINE 0 0 5 ada2 OFFLINE 0 0 0 > Kind of worrying. > > On Mar 13, 2012, at 11:54 PM, Freddie Cash wrote: > >> Remove any snapshots pointing to the filesystem (although there >> shouldn't be any if the entire filesystem is gone). Then scrub the >> pool. That should remove the error message, as that znode/block >> pointer/whatever is removed. >> > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org"