Date: Wed, 14 Mar 2012 05:52:58 +0100 From: =?iso-8859-1?Q?Peter_Ankerst=E5l?= <peter@pean.org> To: Freddie Cash <fjwcash@gmail.com> Cc: fs@freebsd.org Subject: Re: Problem with corrupted file on raidz. Message-ID: <545ACC9D-EB12-4F8F-B8A9-5706AE57296E@pean.org> In-Reply-To: <CAOjFWZ6H071is9gABAq-pWU33XX4Ene0yESYiTpTx=Q79bwzag@mail.gmail.com> References: <1397E951-AE82-4425-9338-3748E5ACC0D4@pean.org> <CAOjFWZ6H071is9gABAq-pWU33XX4Ene0yESYiTpTx=Q79bwzag@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=20 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. >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?545ACC9D-EB12-4F8F-B8A9-5706AE57296E>