From owner-freebsd-questions Sat Feb 1 05:53:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id FAA21589 for questions-outgoing; Sat, 1 Feb 1997 05:53:02 -0800 (PST) Received: from pompano.pcola.gulf.net (root@pompano.pcola.gulf.net [198.69.72.14]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA21584 for ; Sat, 1 Feb 1997 05:53:00 -0800 (PST) Received: from pompano.pcola.gulf.net (spatula@localhost.gulf.net [127.0.0.1]) by pompano.pcola.gulf.net (8.8.5/8.7.3) with SMTP id HAA18674 for ; Sat, 1 Feb 1997 07:52:59 -0600 (CST) Date: Sat, 1 Feb 1997 07:52:58 -0600 (CST) From: Prisoner X-Sender: spatula@pompano.pcola.gulf.net To: freebsd-questions@freebsd.org Subject: swap Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have noticed that my system becomes unstable shortly after it begins using swap. This usually manifests itself as a page-not-present fault in the kernel mode or a lockup, or just unpredictable and strange behavior. When I was installing I had the install program check for bad blocks on the partitions I had created, and there were 5 bad blocks in the swap partition that were marked as unusable. Does the VM mechanism of the Intel or the routines that support it know enough to ignore these bad blocks? Also- is there a way to do something like an fsck to verify the integrity of my swap partition? Nick -- "I don't kill, and I don't murder, or manufacture atomic weapons!" - Nerf Herder Nick Johnson, run for your lives. http://www.gulf.net/~spatula/