Re: kern/50707: rm: fts_read: No such file or directory

[BERTRAND Joël <joel.bertrand%systella.fr@localhost>]

	Hello,

	I have replaced disks by new ones with the same result. Under high I/O, 
system panics with :

/: bad dir ino 2130825 at offset 0: mangled entry
panic: bad dir
cpu1: Begin traceback...
vpanic() at netbsd:vpanic+0x13c
snprintf() at netbsd:snprintf
ufs_dirbadentry() at netbsd:ufs_dirbadentry
ufs_lookup() at netbsd:ufs_lookup+0x4c3
VOP_LOOKUP() at netbsd:VOP_LOOKUP+0x34
lookup_once() at netbsd:lookup_once+0x18b
namei_tryemulroot() at netbsd:namei_tryemulroot+0x612
namei() at netbsd:namei+0x43
fd_nameiat.isra.0() at netbsd:fd_nameiat.isra.0+0x54
do_sys_statat() at netbsd:do_sys_statat+0x72
sys___lstat50() at netbsd:sys___lstat50+0x25
syscall() at netbsd:syscall+0x9a
--- syscall (number 441) ---
7f7ff70a705a:
cpu1: End traceback...

	System runs NetBSD 7.0.1 stable. In last panic (5th of august), kernel 
complains about :
/: bad dir ino 2130825 at offset 0: mangled entry

	In this panic, it complains about the same bad dir inode. But fsck 
doesn't return any error.

	I can upload somewhere netbsd.core.gz and netbsd.gz. I don't know how 
debug this issue.

	Best regards,

	JKB