Date: Fri, 22 Jun 2012 10:54:36 +0300 From: Daniel Kalchev <daniel@digsys.bg> To: freebsd-fs@freebsd.org Subject: Re: ZFS Checksum errors Message-ID: <4FE424BC.5090000@digsys.bg> In-Reply-To: <467652020.30738.1340325033684.JavaMail.root@sz0192a.westchester.pa.mail.comcast.net> References: <467652020.30738.1340325033684.JavaMail.root@sz0192a.westchester.pa.mail.comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22.06.12 03:30, rondzierwa@comcast.net wrote: > the problem was created by a disk error, that is no longer happening, but now I have this corrupted file. how do i clean up the mess? the scrub takes hours, and there are folks that are watching. i'm working on the third iteration of clear and scrub, how many times should it take? I can be patient, but it would be nice if i had an answer for the folks that keep asking "are we there yet?". The easiest fix to your problem is to - backup all data - destroy the ZFS pool - destroy the RAID volume - create single-disk volumes for each disk or just export disks as JBOD - create your ZFS pool using the individual drives (*) - restore all data - run your tests again You will be able to identify which disk is having problems. Sometimes, problems that you describe are caused by faulty disk. Re-seating the cables (or unplugging and plugging again the hot-swap disk) seem to fix it.. but that is only temporary. Such disks rarely show as 'bad' to "hardware RAID" controllers, but ZFS detects them always. Another "fix" is to stop using ZFS altogether, use some other file system. Do not see any errors anymore. Silently corrupt data. It is your data, your choice. I wouldn't do that. (*) If you have large number of disks, you may wish to label them and use labels instead of 'raw' drive names. You could use either glabel(8) or gpart(8) to create the labels, then use these to build the zpool. If for example you label the disks by their position in the chassis, then you can easily find out which disk to replace from the zpool output. Daniel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FE424BC.5090000>