home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!news.u.washington.edu!ns1.nodak.edu!plains.NoDak.edu!tinguely
- From: tinguely@plains.NoDak.edu (Mark Tinguely)
- Newsgroups: comp.unix.bsd
- Subject: Re: virtual memory exhausted
- Message-ID: <Bx8vM1.9zo@ns1.nodak.edu>
- Date: 5 Nov 92 13:18:01 GMT
- Article-I.D.: ns1.Bx8vM1.9zo
- References: <49040@shamash.cdc.com> <wiljo.720428350@kiel.UUCP> <sandi.720955101@gimli>
- Sender: usenet@ns1.nodak.edu (News login)
- Organization: North Dakota State University
- Lines: 11
- Nntp-Posting-Host: plains.nodak.edu
-
- 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.
-