Date: Fri, 16 Mar 2012 18:06:04 +0100 From: Peter Maloney <peter.maloney@brockmann-consult.de> To: freebsd-fs@freebsd.org Subject: Re: Problem with corrupted file on raidz. Message-ID: <4F6372FC.5060507@brockmann-consult.de> In-Reply-To: <545ACC9D-EB12-4F8F-B8A9-5706AE57296E@pean.org> References: <1397E951-AE82-4425-9338-3748E5ACC0D4@pean.org> <CAOjFWZ6H071is9gABAq-pWU33XX4Ene0yESYiTpTx=Q79bwzag@mail.gmail.com> <545ACC9D-EB12-4F8F-B8A9-5706AE57296E@pean.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F6372FC.5060507>