BERTRAND Joël a écrit :
J. Hannken-Illjes a écrit :
On 8. Jul 2017, at 22:56, BERTRAND Joël <joel.bertr...@systella.fr>
wrote:
Hello,
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
Looks like a corrupted file system, we expect inode 1109312 on /usr
to be unallocated but reading it from disk results in an inode with
mode 0x2f20 (chr, sticky, suid, sgid, mode rr-), looks like garbage.
I suppose fsck will not complain about unallocated garbage inodes.
fsck doesn't complain.
Is the /usr file system UFS1 or UFS2, output of dumpfs could help.
FFSv2 with log (and async flag).
legendre# dumpfs /dev/rraid0e
file system: /dev/rraid0e
format FFSv2
endian little-endian
location 65536 (-b 128)
magic 19540119 time Sat Jul 8 22:38:09 2017
superblock location 65536 id [ 56a3c85f 6ea5c015 ]
cylgrp dynamic inodes FFSv2 sblock FFSv2 fslevel 5
nbfree 3425158 ndir 18415 nifree 7887148 nffree 16574
ncg 355 size 33554432 blocks 32529149
bsize 16384 shift 14 mask 0xffffc000
fsize 2048 shift 11 mask 0xfffff800
frag 8 shift 3 fsbtodb 2
bpg 11815 fpg 94520 ipg 22976
minfree 5% optim time maxcontig 4 maxbpg 2048
symlinklen 120 contigsumsize 4
maxfilesize 0x000080100202ffff
nindir 2048 inopb 64
avgfilesize 16384 avgfpdir 64
sblkno 40 cblkno 48 iblkno 56 dblkno 2928
sbsize 2048 cgsize 16384
csaddr 2928 cssize 6144
cgrotor 0 fmod 0 ronly 0 clean 0x02
wapbl version 0x1 location 2 flags 0x0
wapbl loc0 66931968 loc1 127040 loc2 512 loc3 855
flags wapbl
fsmnt /usr
volname swuid 0
Full output is very large...
Regards,
JKB
Maybe related :
I've found a lot of /usr disk corruptions with obvious "fts_read: No
such file or directory" messages.
I've seen this kind of issue with early NetBSD 7.0 but 7.0.1 and 7.0.2
worked fine.
Best regards,
JKB
