Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!cs.uoregon.edu!news.uoregon.edu!news.u.washington.edu!ns1.nodak.edu!plains.NoDak.edu!tinguely From: tinguely@plains.NoDak.edu (Mark Tinguely) Subject: Re: virtual memory exhausted Sender: usenet@ns1.nodak.edu (News login) Message-ID: <Bx8vM1.9zo@ns1.nodak.edu> Date: Thu, 5 Nov 1992 13:18:01 GMT References: <49040@shamash.cdc.com> <wiljo.720428350@kiel.UUCP> <sandi.720955101@gimli> Nntp-Posting-Host: plains.nodak.edu Organization: North Dakota State University Lines: 11 In article <sandi.720955101@gimli> root@gimli.cs.uct.ac.za (Sandi Donno) writes: >Be careful! I tried this on my 4MB system, to see if I could get past a >compile problem. My system hung, and the filesystem was trashed after >rebooting. You may want to look at how you configured your filesystems. Doing a `disklabel -r wd0', if the cylinder list entries (right most numbers) have asterisks behind them, you did not start and end you filesystem partitions on cylinder boundaries. While this does not fix VM problem, it should save you from trashed filesystems.