Date: Fri, 7 Jul 2017 19:49:19 -0400 From: Michael Butler <imb@protected-networks.net> To: Mark Millard <markmi@dsl-only.net>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: dump trying to access incorrect block numbers? [It is not just dump that can get such] Message-ID: <fa0a2aed-e5c7-1d72-e988-64b2683dbb12@protected-networks.net> In-Reply-To: <B76117D2-F3E5-4DC6-8CE8-D39405B6ED47@dsl-only.net> References: <B76117D2-F3E5-4DC6-8CE8-D39405B6ED47@dsl-only.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fa0a2aed-e5c7-1d72-e988-64b2683dbb12>