From owner-freebsd-current@freebsd.org Fri Jul 7 23:49:29 2017 Return-Path: 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 6FD3EDAD78B for ; Fri, 7 Jul 2017 23:49:29 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (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 3F17067099 for ; Fri, 7 Jul 2017 23:49:29 +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=1499471359; bh=8th1Er/2 YRsSUCNeCndlyACoXT6+vJFnBmKEW4GDLVM=; b=XN5/JqDlZ1oS+wf8lPj1PWDJ MRnRy7R76aP5t3X+FrrtRn7lQOCoRNjrPQBnT6Oa4qdcqeITv1s2w+xQln/yhKtr Irvmo5MErCpieF9jn3DQrIG39tKbJzLgjzHIQFt/yL1+UJ2VwJWHHMuABW51sRRl 3y1TDz32EPp279dBYMs= 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 64742DAC0; Fri, 7 Jul 2017 19:49:19 -0400 (EDT) Subject: Re: dump trying to access incorrect block numbers? [It is not just dump that can get such] To: Mark Millard , FreeBSD Current References: From: Michael Butler Message-ID: Date: Fri, 7 Jul 2017 19:49:19 -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: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2017 23:49:29 -0000 On 07/07/17 19:02, Mark Millard wrote: > Michael Butler imb at protected-networks.net wrote on > Fri Jul 7 14:45:12 UTC 2017 : > >> Recent builds doing a backup (dump) cause nonsensical errors in syslog: >> >> Jul 7 00:10:24 toshi kernel: >> g_vfs_done():ada0s3a[READ(offset=6050375794688, length=32768)]error = 5 >> Jul 7 00:10:24 toshi kernel: >> g_vfs_done():ada0s3a[READ(offset=546222112768, length=32768)]error = 5 >> Jul 7 00:10:24 toshi kernel: [ snip ] > Both dump and fsck likely are using snapshots > so the issue is likely ties to ufs snapshots. > May be it has a INO64 incompleteness that > gives the huge offsets. (Wild guess.) > > If your context was more typical then the issue > spans little-endian and big-endian since the > powerpc context is big-endian but most usage > is little endian. I'm seeing this on both amd64 and i386 builds (@SVN r320760) when dump tries to build a snap-shot. These are both non-debug, non-invariant production boxes, Michael