From owner-freebsd-current@freebsd.org  Sat Jul  8 16:38:54 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 C852AD9D8CF
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sat,  8 Jul 2017 16:38:54 +0000 (UTC)
 (envelope-from imb@protected-networks.net)
Received: from mail.protected-networks.net (mail.protected-networks.net
 [202.12.127.228])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mail.protected-networks.net",
 Issuer "Protected Networks CA" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 8B64E802
 for <freebsd-current@freebsd.org>; Sat,  8 Jul 2017 16:38:54 +0000 (UTC)
 (envelope-from imb@protected-networks.net)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=
 protected-networks.net; h=content-transfer-encoding
 :content-language:content-type:content-type:in-reply-to
 :mime-version:user-agent:date:date:message-id:from:from
 :references:subject:subject; s=201508; t=1499531930; bh=4ViuhPrW
 kK41HwVl99IH/5pmJz+4JHEPm3q/Ci1niVA=; b=gVkw2DA6tkyxYN9+6HZ45ZkN
 ZSBDB+u1NjQog2cX5pIOL8YbGX7o/9xmd798aftl88Bc368xyuBREiS2e7+ws6yf
 dMtcdC10czoRghQ1pnk11iXNP7T4f3amM3PlkTHF2+1Gi1aPxY0hn46zc4iYqs4A
 oxsCRZlk52FyFibPeTU=
Received: from toshi.auburn.protected-networks.net
 (toshi.auburn.protected-networks.net [192.168.1.10])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 (Authenticated sender: imb@mail.protected-networks.net)
 by mail.protected-networks.net (Postfix) with ESMTPSA id C54EB11710;
 Sat,  8 Jul 2017 12:38:50 -0400 (EDT)
Subject: Re: dump trying to access incorrect block numbers?
To: "Rodney W. Grimes" <freebsd-rwg@pdx.rh.CN85.dnsmgr.net>
Cc: Peter Jeremy <peter@rulingia.com>,
 freebsd-current <freebsd-current@freebsd.org>
References: <201707081628.v68GSd0i068202@pdx.rh.CN85.dnsmgr.net>
From: Michael Butler <imb@protected-networks.net>
Message-ID: <db504937-a091-f01e-5b8e-19ceebd3eab9@protected-networks.net>
Date: Sat, 8 Jul 2017 12:38:50 -0400
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <201707081628.v68GSd0i068202@pdx.rh.CN85.dnsmgr.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
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 16:38:54 -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,

	Michael