On Wed, 28 May 2025, Manuel Bouyer wrote:
On Wed, May 28, 2025 at 08:51:01AM +0200, [email protected] wrote:Hello, We run a server with a large amount of disk space. The disk space for the server is provided via iSCSI. Unfortunately, the server is not very stable and crashes regularly. Attached is the last dump. Can anyone identify the cause of the problem? Thank you for your support. Regards Uwe ### Reading symbols from /netbsd... Load new symbol table from "/netbsd"? (y or n) y Reading symbols from /netbsd... 0xffffffff80236d65 in cpu_reboot (howto=howto@entry=260, bootstr=bootstr@entry=0x0) at /usr/src/sys/arch/amd64/amd64/machdep.c:717 717 dumpsys(); #0 0xffffffff80236d65 in cpu_reboot (howto=howto@entry=260, bootstr=bootstr@entry=0x0) at /usr/src/sys/arch/amd64/amd64/machdep.c:717 #1 0xffffffff80cb0b72 in kern_reboot (howto=howto@entry=260, bootstr=bootstr@entry=0x0) at /usr/src/sys/kern/kern_reboot.c:73 #2 0xffffffff80ce952f in vpanic ( fmt=fmt@entry=0xffffffff81489de8 "%s: dup alloc ino=%ld on %s: mode %o/%o gen %x/%x size %lx blocks %lx", ap=ap@entry=0xffff850ded754a98) at /usr/src/sys/kern/subr_prf.c:291Looks like a filesystem corruption. Maybe force a fsck on the affected filesystem ?
The last crashes were also a problem with the file system (ffsv2). A file system check was performed each time and the file system was repaired. In some cases, data was also lost.
The problem recurs at irregular intervals. I can only observe the problem on the server that uses a large iSCSI drive. The server is the iSCSI initiator. Therefore, I suspect it's an iSCSI problem.
> > --
Manuel Bouyer <[email protected]> NetBSD: 26 ans d'experience feront toujours la difference --
Regards Uwe
