Re: [NetBSD-7] Panic in nfsd

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

Manuel Bouyer a écrit :
> On Tue, Jan 05, 2016 at 10:24:32AM +0100, BERTRAND Joël wrote:
> > Christos Zoulas a écrit :
> > > On Jan 4,  9:53pm, joel.bertrand%systella.fr@localhost (=?UTF-8?Q?BERTRAND_Jo=c3=abl?=) wrote:
> > > -- Subject: Re: [NetBSD-7] Panic in nfsd
> > >
> > > | Christos Zoulas a écrit :
> > > | > Can you try with a DEBUG/DIAGNOSTIC/LOCKDEBUG kernel?
> > > |
> > > | 	I can. I will upgrade system as soon as possible.
> > >
> > > Perhaps also: makeoptions    DEBUG="-g"      # compile full symbol table
> > > In case it dumps.
> > >
> > > Good luck,
> > >
> > > christos
> >
> > 	I have added this option. Yesterday, when I have tried to rebuild NetBSD
> > from sources, system have paniced twice :
> >
> > Jan  4 23:45:14 legendre /netbsd: vpanic() at netbsd:vpanic+0x13c
> > Jan  4 23:45:14 legendre /netbsd: snprintf() at netbsd:snprintf
> > Jan  4 23:45:14 legendre /netbsd: ufs_dirbadentry() at
> > netbsd:ufs_dirbadentry
>
> Did you force a fsck (fsck -fy) from single user on all filesystems ?
> If the system paniced on a corrupted fs, WAPBL isn't of any help
> and only a fsck can fix the problem.

	I have done a fsck /dev/rld0a in single user mode (only as I cannot 
access to server console before next friday).

	Regards,

	JKB