From owner-freebsd-fs@FreeBSD.ORG Mon Dec 8 17:09:54 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 02FCEA1A for ; Mon, 8 Dec 2014 17:09:54 +0000 (UTC) Received: from mail-qg0-f42.google.com (na3sys010aog105.obsmtp.com [74.125.245.78]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 85FEBF32 for ; Mon, 8 Dec 2014 17:09:53 +0000 (UTC) Received: from mail-qg0-f42.google.com ([209.85.192.42]) (using TLSv1) by na3sys010aob105.postini.com ([74.125.244.12]) with SMTP ID DSNKVIXbYLnQHa+NITh3bgkQ4UgWadTlmEfZ@postini.com; Mon, 08 Dec 2014 09:09:53 PST Received: by mail-qg0-f42.google.com with SMTP id z107so3837494qgd.1 for ; Mon, 08 Dec 2014 09:09:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=groupon.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PJYoUpUu/yxYVaOEBnl/A9Cf/weA+odE9g64jbKFMps=; b=MONHFvJafhA2Uhhu50tYttG+qdFLvACfaYRi5sSzfUWyeOVikx+Ld3SqshTcdBaC1T YWBzh4UEpLJevUIoTttjmSPtnxlDbu1P1S5kiRr9PYPM+QHQZTYNlLS9udWn2DNQAWu1 6MaiXeSxRJ8WOW/gQzs9YK3u+g4jBs9ERXDlE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=PJYoUpUu/yxYVaOEBnl/A9Cf/weA+odE9g64jbKFMps=; b=G0S7G/fRwDVdQr0Czu4DvXLa80AxRas8tOml//rD5ZvCZluEHssjeVjbiUqyPsb4yF JnigkTnA549XqC+GpINLUQ1b1UDtXhjoQckuao61mL60py6F1CM/MCMLHUOGzdI46cMi eWonGoP1vqR+xLPXvq2JjvP49M4viQvk/4htdltLp9U7XWnLk59YHYT1YdFqs9rHe+TZ cP1urie4hMeT+0QLhPDoA6NwkyyjrPE0XTWAq98RT1CXWu9GR0sLmaqpwrz8GOUem9eq O+34ynQiw+HviRvA9d7TgmPdEWbhD0DvvIctkCsMxQRah3wUxekXzj6llK4Kas/xaLra UYBA== X-Gm-Message-State: ALoCoQkV4eyk0ukqYAkw3KxwZyMYWbum8w2Qv1K7+ZmhW8P/+DoqtTlkwm8z5G/v0mIUYwJcoaXINhIZTLCg+LdxmBennFTWS06oer9gMMmZDcJ5xOcMivnTVhRnm48sGNwwR43L+W1QXTpUBzrwYtjHuhj4klCjcA== X-Received: by 10.224.4.8 with SMTP id 8mr55034719qap.77.1418058591962; Mon, 08 Dec 2014 09:09:51 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.224.4.8 with SMTP id 8mr55034688qap.77.1418058591756; Mon, 08 Dec 2014 09:09:51 -0800 (PST) Received: by 10.96.115.163 with HTTP; Mon, 8 Dec 2014 09:09:51 -0800 (PST) In-Reply-To: <5485CB35.5010608@multiplay.co.uk> References: <20141208155230.GA574@iozz.us> <5485CB35.5010608@multiplay.co.uk> Date: Mon, 8 Dec 2014 09:09:51 -0800 Message-ID: Subject: Re: ZFS scrub on new disks gives cksum errors From: Sean Chittenden To: Steven Hartland Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2014 17:09:54 -0000 I had this exact problem at home on my FreeNAS host when a box is plugged in to residential power that is "not clean." If you plug this host in to a UPS it should clear things up instantly (find a sine wave UPS, not a digital stepping supply). There's something about the fluctuating power or brownouts that ZFS is well suited to detecting (and became terrifying to me because wtf happened in the past pre-ZFS??). -sc On Mon, Dec 8, 2014 at 8:00 AM, Steven Hartland wrote: > Bad memory, cabling? > > > On 08/12/2014 15:53, Brian N wrote: > >> Hi. >> >> I have two new 3TB disks that I'm testing prior to installing in a >> production >> server. I created a zpool mirror, dumped a bunch of data to the pool and >> ran a >> scrub. I got back numerous CKSUM errors, the same number on each drive. >> I'm >> guessing this is not a problem with my 3TB drives but a controller or some >> other hardware problem. Is this a correct assumption? >> >> The PC where I'm running this test is using a GA-E7AUM-DS2H mainboard and >> non-ecc memory. >> >> ###### >> >> root@server:~ # zpool status >> pool: tank >> state: ONLINE >> status: One or more devices has experienced an error resulting in data >> corruption. Applications may be affected. >> action: Restore the file in question if possible. Otherwise restore the >> entire pool from backup. >> see: http://illumos.org/msg/ZFS-8000-8A >> scan: scrub repaired 0 in 3h57m with 23 errors on Mon Dec 8 03:05:28 >> 2014 >> config: >> >> NAME STATE READ WRITE CKSUM >> tank ONLINE 0 0 23 >> mirror-0 ONLINE 0 0 46 >> ada1 ONLINE 0 0 46 >> ada3 ONLINE 0 0 46 >> >> errors: 2 data errors, use '-v' for a list >> >> _______________________________________________ >> 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" >> > > _______________________________________________ > 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" > -- Sean Chittenden