On 2025/09/09 22:35, H. Hartzer wrote: > Hi bugs@, > > I have a panic nearly identical to this one: > > https://marc.info/?l=openbsd-bugs&m=170874964321453&w=2 > "Subject: panic: ffs_valloc: dup alloc, usb corruption?" > > OpenBSD 7.7, x86_64, with software raid 1. Standard automatic partition > layout. > > I was running Bitcoind and syncing while extracting ports.tar.gz to > /usr. > > Before this last boot, I was also running Bitcoind, syncing the > blockchain, while extracting ports.tar.gz to /usr. The server was > unplugged. I booted and it could not automatically fsck /usr. I had to > fsck_ffs the /usr partition and I did "F" -- all, or perhaps almost all, > of the entires seemed to pertain to /usr/ports. > > So this seems very similar, and like a long lived bug that after certain > fscks, this panic is possible. > > Not sure how to proceed from here. The earlier report was about FFS on > USB and I think there were some doubts that maybe it was more to do with > USB than anything else. > > Thanks! > > -Henrich >
I suggest newfs + recreating this filesystem from your backups. A crash or power failure during active changes to the filesystem will often result in filesystem damage and fsck isn't always able to fix the problems.
