Martin Possible in this case the file system was created on an earlier netbsd than 5. I have recently upgraded between each major release starting at 1.0. When I went from 7.2 to 8.2 I had problems - 8.2 will not mount the root file system. I had to reboot single user with a 7.2 kernel and tune the file systems with fsck_ffs -c 4 (Again it’s possible this is because the file system was older - possibly created on 1.5.4). C > On 21 Aug 2022, at 02:58, Martin Husemann <martin%duskware.de@localhost> wrote: > > On Sat, Aug 20, 2022 at 07:08:07PM -0500, Christopher Pinnock wrote: >> There is a change of file system superblock format between 7 and 8 >> iirc which may need some attention. > > I would like to hear details of this (as we are currently struggling > with a similar issue for the NetBSD 10 branch). > > The only thing I found is in CHANGES-7.1: > > sbin/fsdb/fsdb.c 1.49 > sys/ufs/ffs/ffs_vfsops.c 1.340 > usr.sbin/quot/quot.c 1.34 > > The superblock field that distinguishes between 4.2BSD and > 4.4BSD inodes is really only relevant on a UFS1 file system. > Make sure that it is a UFS1 fs before using fs_old_inodefmt. > > Note that the NetBSD newfs and mkfs utilities initialize > fs_old_inodefmt even for UFS2, so problems were apparent only > on file systems created by other operating systems, for example, > FreeBSD. > > > Martin
Attachment:
smime.p7s
Description: S/MIME cryptographic signature