Date: Sun, 2 Apr 2000 20:02:54 +0200 From: Vallo Kallaste <vallo@matti.ee> To: Bernd Walter <ticso@cicely.de> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402200254.A69811@myhakas.matti.ee> In-Reply-To: <20000402173729.A25194@cicely8.cicely.de>; from ticso@cicely.de on Sun, Apr 02, 2000 at 05:37:30PM %2B0200 References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> <20000402153935.A64937@myhakas.matti.ee> <20000402173729.A25194@cicely8.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Apr 02, 2000 at 05:37:30PM +0200, Bernd Walter <ticso@cicely.de> wrote: > > I hook up serial console to get full traceback next time, but I don't > > have any knowledge for further analysis. > > You don't need a serial console to get further informations. > You should compile the kernel with debug symbols and set dumpdev in rc.conf > to get a crash dump. > > Are you for any chance running the NFS Server without nfsd? > I expect them to be needed if you are serving vinum volumes. Yes, but I don't have space for crashdump and I can't build new kernel with limited memory usage because I don't have /usr filesystem up and running. Is there a way to limit memory usage without recompiling kernel? I can store 32MB crashdump at the moment, no separate /var filesystem because I thought 4.0-RELEASE will be stable enough for experimenting with vinum.. I don't have another 4.0-RELEASE or stable system but I'll try to build 4.0-R kernel on -current system. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000402200254.A69811>