Re: kern/55362: bad inodes created after dump|restore

[Robert Elz <kre%munnari.OZ.AU@localhost>]

The following reply was made to PR kern/55362; it has been noted by GNATS.

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/55362: bad inodes created after dump|restore
Date: Thu, 11 Jun 2020 00:02:46 +0700

     Date:        Wed, 10 Jun 2020 14:35:01 +0000 (UTC)
     From:        Patrick Welche <prlw1%cam.ac.uk@localhost>
     Message-ID:  <20200610143501.CE8BB1A921E%mollari.NetBSD.org@localhost>
 
   |  If it were the disks, could I expect
 
 On the off chance  it is, you could simply compare the data
 portions (all except the raid header) of the two partitions that
 make up the raid1 on which the filesystem was created - assuming that
 raid1 init has finished, the two should be, and remain, identical
 (at least when not in active use, so do it with the filesystem(s)
 unmounted).   (You cold just compare the entire partitions, and
 ignore differences in the first 64 blocks).
 
 If the two differ, then either there really is some hardware issue, or
 raidframe isn't working properly.
 
   |  - for MLH not to have had a similar observation with a >=  9.99.64 kernel
 
 It isn't clear that they are the same problem.   It might be, or
 that could be different - the history of that filesystem wasn't
 made clear.
 
 kre