Subject: Re: Bug in null filesystem
To: None <windsor@warthog.com>
From: Benjamin Lorenz <lorenz@ps.uni-sb.de>
List: port-sparc
Date: 06/03/1998 22:37:33
> >  mount -t null /var/obj /usr/src
> >  panic: lockmgr: locking against myself
> 
> I was told (two full releases ago) that this was a known problem and that
> it would go away as soon as the lite-2 nullfs code was incorporated.

Hm... on a PC running release 1.3 it worked... or is this
a sparc specific problem?

Something other: savecore produced two files at reboot time:

 lorenz@toto[p1]</>% ll var/crash
 total 50058
 -rw-r--r--  1 root  wheel         2 Jun  3 22:26 bounds
 -rw-r--r--  1 root  wheel         5 Mar 12 16:38 minfree
 -rw-r--r--  1 root  wheel   1624326 Jun  3 22:26 netbsd.1
 -rw-r--r--  1 root  wheel  49578520 Jun  3 22:26 netbsd.1.core
 lorenz@toto[p1]</>%

Should the command `gdb netbsd.1 netbsd.1.core' succeed? All I get is

 "/var/crash/netbsd.1.core" is not a core dump: File format not recognized

...because

 lorenz@toto[p1]</>% file var/crash/netbsd.1.core
 var/crash/netbsd.1.core: data

Perhaps a stupid question: Is it okay to activate the swap device
in /etc/rc _before_ reading the dump?

-- 
      Benjamin <lorenz@dfki.de>