From owner-freebsd-current@freebsd.org Sat Jul 8 02:57:18 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 921B8D87AAE for ; Sat, 8 Jul 2017 02:57:18 +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 5F65770BEA for ; Sat, 8 Jul 2017 02:57:18 +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=1499482636; bh=vOvEjK/B 7Ufvezd5Z4w0yg+TtSoF9f7i50LIAdmktrQ=; b=je+dCca7QbUydFItCN7BrT7X JPOXoBvGKGDbZ9vVQEoWJCkIaE91c/fXiRFwFViq2CpDTatbe6K94pthKpAYYHnt 9rxiUQyXebBp+DU5Bz4lZt2/ZdW3uGoSLdCtczOAFfOx/2lrt+3p0LNkRMSKxIol OyazlI1uycWSciIMP9o= 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 8DE46EDC2; Fri, 7 Jul 2017 22:57:16 -0400 (EDT) Subject: Re: dump trying to access incorrect block numbers? To: Peter Jeremy Cc: freebsd-current References: <59e89e5b-ddff-2405-7a0c-6de59d32438f@protected-networks.net> <20170708015323.GA13323@server.rulingia.com> From: Michael Butler Message-ID: Date: Fri, 7 Jul 2017 22:57:16 -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: <20170708015323.GA13323@server.rulingia.com> Content-Type: text/plain; charset=windows-1252; 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: Sat, 08 Jul 2017 02:57:18 -0000 On 07/07/17 21:53, Peter Jeremy wrote: > On 2017-Jul-07 10:44:36 -0400, Michael Butler wrote: >> Recent builds doing a backup (dump) cause nonsensical errors in syslog: > > I can't directly offer any ideas but some more background might help: > When did you first notice this (what SVN revision)? I was stuck on SVN r319721 on the i386 machine while the socket/union issue was addressed. That version did not display the problem. > Do you know what the last good SVN revision was? > Is this a new or old filesystem? old - it's been years since this system was rebuilt. > Is the filesystem mounted/active or not when you dump it? Mounted and active. > What are the relevant parameters for the filesystem on ada0s3a? imb@toshi:/home/imb> dumpfs / magic 19540119 (UFS2) time Fri Jul 7 22:43:49 2017 superblock location 65536 id [ 56c8bf68 1a8b12b5 ] ncg 516 size 82575360 blocks 79978821 bsize 32768 shift 15 mask 0xffff8000 fsize 4096 shift 12 mask 0xfffff000 frag 8 shift 3 fsbtodb 3 minfree 8% optim time symlinklen 120 maxbsize 32768 maxbpg 4096 maxcontig 4 contigsumsize 4 nbfree 3965346 ndir 98169 nifree 40196026 nffree 453383 bpg 20035 fpg 160280 ipg 80256 unrefs 0 nindir 4096 inopb 128 maxfilesize 2252349704110079 sbsize 4096 cgsize 32768 csaddr 5056 cssize 12288 sblkno 24 cblkno 32 iblkno 40 dblkno 5056 cgrotor 253 fmod 0 ronly 0 clean 0 metaspace 6408 avgfpdir 64 avgfilesize 16384 flags soft-updates fsmnt / volname swuid 0 providersize 82575360 [ .. ] > Are you running softupdates, journalling etc? soft-updates only. > Which dump(8) phase is reporting the errors? The errors occur before the "date of the last level x dump" message - presumably, this is while creating the snapshot. > What are the exact dump and fsck commands you ran? /sbin/dump 0Lauf - -C 32 / none of the following report any (unexpected) errors: fsck -f / fsck -f -r / fsck -f -Z / > >> I now have two UFS-based systems showing the same symptoms - what's up >> with this? > > Was there anything you did on either filesystem that might have triggered it? Other than update the kernel, no. Michael