Igor Boehm wrote: > > > On 7 Sep 2016, at 15:20, Ted Unangst <[email protected]> wrote: > > > > Igor Boehm wrote: > >> Here some additional information on the issue: > >> > >> Stack-trace core0 converted from > >> [http://bytelabs.org/openbsd-6.0-bug-report/0-panic.png] using OCR: > >>> OpenBSD/amd64 (openbsd.bytelabs.org) (ttyC0) > >>> login: mode = 0100644, inum = 9348113, fs = /home > >>> panic: ffs_valloc: dup alloc > > > > dup alloc panics are most often the result of disk corruption. > > Thanks for having a look at this. > > The machine I am running this on is a virtual server with SSDs where OpenBSD > 6.0 is the guest. I believe VirtIO is used for HD virtualisation. > > Would you have any hints on how I can further debug the true cause of the > problem or are there any known issues with SSDs, VirtIO, etc. >
Not really. It's hard to find out when corruption happened after the fact. I'd start over with a new install to ensure the filesystems are recreated cleanly. Running fsck -f may also detect more errors. My first suspect is that virtio or the VM is not flushing data to disk properly. You install, reboot, and some data doesn't get saved. This is somewhat easy, if annoying to test. Just write a bunch of data and reboot. Don't necessarily need to reinstall everytime. Just create a file, fill it with non-zero data, and reboot immediately after. Check contents after.
