Re: dump trying to access incorrect block numbers? [It is not just dump that can get such]

From: Michael Butler <imb_at_protected-networks.net> Date: Fri, 7 Jul 2017 19:49:19 -0400 · This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:12 UTC

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 (_at_SVN r320760) when dump 
tries to build a snap-shot. These are both non-debug, non-invariant 
production boxes,

	Michael