Date: Fri, 23 May 2003 22:06:51 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "Daniel C. Sobral" <dcs@tcoip.com.br> Cc: Robert Watson <rwatson@freebsd.org> Subject: Re: /dev/null panic still alive Message-ID: <99395.1053720411@critter.freebsd.dk> In-Reply-To: Your message of "Fri, 23 May 2003 16:15:36 -0300." <3ECE7358.4060608@tcoip.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <3ECE7358.4060608@tcoip.com.br>, "Daniel C. Sobral" writes: >Poul-Henning Kamp wrote: >> In message <3ECE647B.1030705@tcoip.com.br>, "Daniel C. Sobral" writes: >> >> >>>And well. Funny. Something in my daily (or so it seems) caused the >>>panic. After which the lockmgr panic attacked. :-( Anyway, core dump for >>>the /dev/null: >> >> >> This is an attempt to fiddle an EA on a VCHR vnode backed by UFS/FFS. >> >> I currently have no idea how to fix this without doing things to the >> buffer cache which are not kosher at this time or at all. > >/me shrugs > >It's just that having a computer with mac enabled panic each time daily >is run is kinda bad. Somewhere, probably under /compat/linux/dev you have some device nodes on a UFS filesystem. You shouldn't need those (I think ?) and they are likely the cause of this. Kirk's on vacation and I havn't heard back from rwatson what he think we should do. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99395.1053720411>