From owner-freebsd-current@freebsd.org  Sat Jul  8 18:13:29 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 CCE39D9FC13
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sat,  8 Jul 2017 18:13:29 +0000 (UTC)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140])
 (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 9F6A164398
 for <freebsd-current@freebsd.org>; Sat,  8 Jul 2017 18:13:29 +0000 (UTC)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1])
 by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id v68IDSUb068637;
 Sat, 8 Jul 2017 11:13:28 -0700 (PDT)
 (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net)
Received: (from freebsd-rwg@localhost)
 by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id v68IDR7Y068636;
 Sat, 8 Jul 2017 11:13:27 -0700 (PDT) (envelope-from freebsd-rwg)
From: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>
Message-Id: <201707081813.v68IDR7Y068636@pdx.rh.CN85.dnsmgr.net>
Subject: Re: dump trying to access incorrect block numbers?
In-Reply-To: <db504937-a091-f01e-5b8e-19ceebd3eab9@protected-networks.net>
To: Michael Butler <imb@protected-networks.net>
Date: Sat, 8 Jul 2017 11:13:27 -0700 (PDT)
CC: Peter Jeremy <peter@rulingia.com>,
 freebsd-current <freebsd-current@freebsd.org>
X-Mailer: ELM [version 2.4ME+ PL121h (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
X-Mailman-Approved-At: Sat, 08 Jul 2017 21:38:48 +0000
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jul 2017 18:13:29 -0000

> On 07/08/17 12:28, Rodney W. Grimes wrote:
> 
> > Since it has been speculated that this is occuring during the
> > creation of the snapshot, could you try just creating a snapshot
> > using mksnap_ffs and see if any errors occur?
> 
> After a short pause with disk activity, the same sorts of errors are 
> logged when using "mksnap_ffs /.snap2" where .snap2 did  not previously 
> exist,

Ok, so this simplifies what needs to be looked at, this is no
longer a dump(8) issue, but now a snapshot ufs issue.

This should be much easier for more people to try out.  

-- 
Rod Grimes                                                 rgrimes@freebsd.org