From owner-freebsd-bugs@freebsd.org  Thu Jun 22 11:31:43 2017
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 1F7F3D8A25B
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu, 22 Jun 2017 11:31:43 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0DED177F32
 for <freebsd-bugs@FreeBSD.org>; Thu, 22 Jun 2017 11:31:43 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v5MBVglf075526
 for <freebsd-bugs@FreeBSD.org>; Thu, 22 Jun 2017 11:31:42 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 220203] [zfs] [panic] in dmu_objset_do_userquota_updates on mount
Date: Thu, 22 Jun 2017 11:31:43 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: avg@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-220203-8-SOKDc5pw2T@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-220203-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-220203-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jun 2017 11:31:43 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220203

--- Comment #4 from Andriy Gapon <avg@FreeBSD.org> ---
(In reply to neovortex from comment #2)
Some thoughts / comments.

The block layout is exactly the same between mirror members.
It's quite unlikely that both drives would give errors for the same blocks =
at
the same time.

The problem can be potentially caused by the checksum being incorrectly
calculated when the data is written, but such a bug is not very likely too =
(but
not impossible).

Perhaps running "zdb -dddddd system-ssd/storage/ezjail/jailname -2" would g=
ive
some additional clues...

--=20
You are receiving this mail because:
You are the assignee for the bug.=