On Sun, Oct 11, 2020 at 03:47:31PM +0200, Reinoud Zandijk wrote: > As for without -snapshot, i haven't dug into that yet It reports a clean FS but when using `fsck -f' on the file when its attached through vnd i get: > sudo fsck -f /dev/dk0 ** /dev/rdk0 ** File system is already clean ** Last Mounted on / ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames UNALLOCATED I=68864 OWNER=0 MODE=0 SIZE=0 MTIME=Oct 11 15:58 2020 NAME=/var/run/dev.cdb ... BAD INODE NUMBER FOR '.' I=68907 OWNER=0 MODE=40755 SIZE=512 MTIME=Oct 11 15:58 2020 DIR=/var/run/resolvconf etc... The input image was flawless (double checked its backup copy) and all I did was booting the VM and then executing `dhcpcd' before shutting down with `shutdown -p now'. This is with NetBSD/amd64 version 6.99.69 running in qemu 5.0.0nb5 on 9.0_STABLE (4 october) with the image over NFS. The invocation used is: qemu-system-x86_64 -m 4096 -accel nvmm -smp cpus=2 -drive \ file=work/wd0.img,format=raw -nographic -gdb tcp::1234 -net nic -net \ tap,ifname=tap0,script=no Now is this an qemu related problem? I am a bit hessistent to try the -current kernel out on real hardware but i've ran a couple minor version on real hardware without any issue so far. With regards, Reinoud
Attachment:
signature.asc
Description: PGP signature