Date: Wed, 14 Mar 2012 01:02:37 -0400 From: Mark Murawski <markm-lists@intellasoft.net> To: freebsd-fs@freebsd.org Subject: Re: ZFS file corruption problem Message-ID: <4F60266D.1090302@intellasoft.net> In-Reply-To: <4F5F97A4.6070000@brockmann-consult.de> References: <4F5F7116.3020400@intellasoft.net> <4F5F97A4.6070000@brockmann-consult.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/13/12 14:53, Peter Maloney wrote: > Am 13.03.2012 17:08, schrieb Mark Murawski: >> So I have this zpool with corrupted files running on freebsd 9-release >> amd64. The corrupted files can go away, that's not a big deal >> >> Here's the problem. >> >> $ ls -al /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 >> <infinite wait ensues> > Since this is one of the corrupt files, I guess ZFS would like to block > until it can return a good copy (such as if you put the mirror disk back > in)... so to fix this, you need to remove the file or restore from > backup (or add that mirror disk back in, which I will assume you can't): > > rm /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 > (in the case of a file that should exist empty instead of being removed, > eg. a log where the log writer does not have write permission to the > directory, do touch also) > > or maybe this works: > > mv /somewhere_with_backup/IMG_5576.CR2 > /storage/zfs/0-Pics/2012-03-01-peterskill/155CANON/IMG_5576.CR2 > > > And if there are more errors, you probably need to scrub to expand the > pool or for "zpool clear" to work. > Oh wow. For some reason I never thought of rm. That works on getting rid of the file. Why would the whole pool now become available upon access to a bad file?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F60266D.1090302>