From owner-freebsd-fs@freebsd.org  Fri Jul 14 12:08:03 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 57CA3DA026E
 for <freebsd-fs@mailman.ysv.freebsd.org>; Fri, 14 Jul 2017 12:08:03 +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 4565D6357A
 for <freebsd-fs@FreeBSD.org>; Fri, 14 Jul 2017 12:08:03 +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 v6EC83h3062119
 for <freebsd-fs@FreeBSD.org>; Fri, 14 Jul 2017 12:08:03 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 220693] head -r320570 & -r320760 (e.g.): ufs snapshot creation
 broken & leads to fsck -B related SSD-trim "freeing free block"
 panics; more
Date: Fri, 14 Jul 2017 12:08:03 +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: CURRENT
X-Bugzilla-Keywords: regression
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: pho@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-220693-3630-KnSU2LiJwU@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-220693-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-220693-3630@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-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, 14 Jul 2017 12:08:03 -0000

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

Peter Holm <pho@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pho@FreeBSD.org

--- Comment #1 from Peter Holm <pho@FreeBSD.org> ---
Just running mksnap_ffs(8) on a pristine file system triggers:
g_vfs_done():md5a[READ(offset=3D34368126976, length=3D28672)]error =3D 5
This on
FreeBSD t1.osted.lan 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r320982: Fri Jul =
14
13:16:44 CEST 2017     pho@t1.osted.lan:/usr/src/sys/amd64/compile/PHO  amd=
64

Partial script:
mdconfig -a -t swap -s 2g -u $mdstart || exit 1
bsdlabel -w md$mdstart auto
newfs -U md${mdstart}$part > /dev/null
mount /dev/md${mdstart}$part $mntpoint

while ! mksnap_ffs $mntpoint $mntpoint/.snap/stress2; do :; done

tail -5 /var/log/messages | grep "g_vfs_done():md5a" && s=3D1

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