>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.
to continue what Ted said: "result of *previous* disk corruption" the kernel ffs code operates transactionally when handling certain tricky operations. most fsck repairs are based on understanding what transition the filesystem was in the midst of when it failed. but there is the possibility of stray operations causing damage beyond that as a result, fsck is not able to repair all types of damage. it cannot even see them. as a result you could crash later. this problem is not unique to openbsd.
