Re: one remaining mystery about the FreeBSD domU failure on NetBSD XEN3_DOM0

[RVP <rvp%SDF.ORG@localhost>]

On Sun, 11 Apr 2021, Greg A. Woods wrote:

> Anyway this does something slightly different (and better, or worse) on
> the FreeBSD side, but still ends up with a corrupted filesystem, as seen
> from both sides, though maybe not so bad from NetBSD's point of view:
>
> # mount /dev/da1
> mount: /dev/da1: unknown special file or file system
> ...
> # umount /mnt
> # fsck /dev/da1
> ** /dev/da1
> ** Last Mounted on /mnt
> ** Phase 1 - Check Blocks and Sizes
> PARTIALLY TRUNCATED INODE I=325128
> SALVAGE? [yn] n
>
> PARTIALLY TRUNCATED INODE I=877864
> SALVAGE? [yn] n
>
> PARTIALLY TRUNCATED INODE I=877866
> SALVAGE? [yn] n
>
> PARTIALLY TRUNCATED INODE I=877879
> SALVAGE? [yn] ^C
>
> ***** FILE SYSTEM MARKED DIRTY *****

Don't see that on a standard block device (USB stick):

$ sudo gpart add -t freebsd-ufs da0
da0p1 added
$ sudo newfs -O1 /dev/da0p1
/dev/da0p1: 496.0MB (1015728 sectors) block size 32768, fragment size 4096
        using 4 cylinder groups of 124.00MB, 3968 blks, 15872 inodes.
super-block backups (for fsck_ffs -b #) at:
 64, 254016, 507968, 761920
$ sudo fsck_ufs -EfrZz da0p1
** /dev/da0p1
** Last Mounted on
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
2 files, 2 used, 124907 free (27 frags, 15610 blocks, 0.0% fragmentation)

***** FILE SYSTEM IS CLEAN *****
$ sudo mount /dev/da0p1 /media
$ sudo umount /media
$

-RVP