Am 08.07.2017 um 22:56 schrieb BERTRAND Joël:
> This evening, my server running NetBSD 8.0 (built from sources this
> morning) has paniced :
>
> legendre# crash -M netbsd.4.core -N netbsd.4
> Crash version 8.0_BETA, image version 8.0_BETA.
> System panicked: ffs_newvnode: dup alloc ino=1109312 on /usr: mode
> 2f20/2f20 gen 65642f6a/65642f6a size 726964747365642f blocks
> 752f3436646d612e
> Backtrace from time of crash is available.
> crash> bt
> _KERNEL_OPT_NARCNET() at 0
> ?() at fffffe84075c4000
> vpanic() at vpanic+0x149
> snprintf() at snprintf
> ffs_newvnode() at ffs_newvnode+0x530
> vcache_new() at vcache_new+0x7c
> ufs_makeinode() at ufs_makeinode+0x38
> ufs_create() at ufs_create+0x31
> VOP_CREATE() at VOP_CREATE+0x38
> vn_open() at vn_open+0x351
> do_open() at do_open+0x112
> do_sys_openat() at do_sys_openat+0x68
> sys_open() at sys_open+0x24
> syscall() at syscall+0x1bc
> --- syscall (number 5) ---
> 7f2ccc03e07a:
I have/had a very similar looking issue on shark during installation:
http://gnats.netbsd.org/52102
It was definitely not a bad disk etc.
Unfortunately I had no time to bisect this so far, and in my case it
will probably require going back between -6 and -7 to find the offender...
Cheers,
Felix
