From owner-freebsd-fs@freebsd.org  Fri Sep 22 08:48:09 2017
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0ED3E1F17A
 for <freebsd-fs@mailman.ysv.freebsd.org>; Fri, 22 Sep 2017 08:48:09 +0000 (UTC)
 (envelope-from avg@FreeBSD.org)
Received: from citapm.icyb.net.ua (citapm.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id EB1A71C1D
 for <freebsd-fs@FreeBSD.org>; Fri, 22 Sep 2017 08:48:08 +0000 (UTC)
 (envelope-from avg@FreeBSD.org)
Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua
 [212.40.38.100])
 by citapm.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA11305;
 Fri, 22 Sep 2017 11:48:06 +0300 (EEST)
 (envelope-from avg@FreeBSD.org)
Received: from localhost ([127.0.0.1])
 by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD))
 id 1dvJd0-0008ab-7C; Fri, 22 Sep 2017 11:48:06 +0300
Subject: Re: ZVOL with volblocksize=64k+ results in data corruption [was Re:
 Resolving errors with ZVOL-s]
To: Wiktor Niesiobedzki <bsd@vink.pl>, freebsd-fs <freebsd-fs@FreeBSD.org>
References: <CAH17caX=10DsuQo3KQnR31B+2M54-yj0RUtz6WQBivqfBokWdw@mail.gmail.com>
From: Andriy Gapon <avg@FreeBSD.org>
Message-ID: <062dfcf9-b56e-c6c4-4039-c48bf7bdd610@FreeBSD.org>
Date: Fri, 22 Sep 2017 11:46:44 +0300
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CAH17caX=10DsuQo3KQnR31B+2M54-yj0RUtz6WQBivqfBokWdw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Sep 2017 08:48:09 -0000

On 21/09/2017 23:00, Wiktor Niesiobedzki wrote:
> I've conducted additional tests. It looks like when I create volumes with
> following commands:
> # zfs create -V50g -o volmode=dev -o volblocksize=64k -o compression=off -o
> com.sun:auto-snapshot=false tank/test
> # zfs create -V50g -o volmode=dev -o volblocksize=128k -o compression=off
> -o com.sun:auto-snapshot=false tank/test
> 
> I'm able to get checksum errors quite reliably in 2-12h of normal work of
> the volume. I tested also different volbocksizes:
> # zfs create -V50g -o volmode=dev -o volblocksize=32k -o compression=off -o
> com.sun:auto-snapshot=false tank/test
> # zfs create -V50g -o volmode=dev -o volblocksize=8k -o compression=off -o
> com.sun:auto-snapshot=false tank/test
> # zfs create -V50g -o volmode=dev -o volblocksize=4k -o compression=off -o
> com.sun:auto-snapshot=false tank/test
> 
> And gave them more than 24h of work with no apparent errors (I also moved
> other volumes to 4k and they did not show any checksum errors for more than
> 2 weeks).
> 
> I was running with volblocksize=128k from January this year. The problem
> started to appear only after I updated from 11.0 to 11.1.
> 
> Should I file bug report for this? What additional information should I
> gather?

Are you able to patch your version of FreeBSD?
Could you please try https://svnweb.freebsd.org/changeset/base/323918
and see if it makes things better?

Thanks!
-- 
Andriy Gapon