From owner-freebsd-current  Sun Dec  1 06:38:38 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA16463
          for current-outgoing; Sun, 1 Dec 1996 06:38:38 -0800 (PST)
Received: from dyson.iquest.net ([198.70.144.127])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA16458;
          Sun, 1 Dec 1996 06:38:35 -0800 (PST)
Received: from dyson.iquest.net (localhost [127.0.0.1]) by dyson.iquest.net (8.8.2/8.6.9) with SMTP id JAA01134; Sun, 1 Dec 1996 09:38:34 -0500 (EST)
Message-ID: <32A19869.41C67EA6@freebsd.org>
Date: Sun, 01 Dec 1996 09:38:33 -0500
From: "John S. Dyson" <dyson@freebsd.org>
Organization: John S. Dyson's home machine
X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 3.0-CURRENT i386)
MIME-Version: 1.0
To: sos@freebsd.org
CC: current@freebsd.org
Subject: Re: Corrupted CVS updates
References: <199612011411.PAA23207@ravenock.cybercity.dk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Soren Schmidt wrote:

> 
> Hmm, I have seen various problems with some of the bigger CTM
> patches (esp. those that touch all files), this triggers our
> old well known (but not understood) vm problem, that manifests
> itself as an bogus diskblock (one page), that will disappear if
> the disk is unmounted & then mounted again 95% of the times, the
> last 5% that invalid block will have been written back to disk :(
> It seems that my systems has been suffering pretty bad from this
> over the last ~14 days or so. I have one workaround for this:
> mount the disks via nfs and do the update from another machine,
> this fixes the problem, but is dog slow....
> 
Sorry for my Netscape reply -- only mailer that I have right
now that supports mime...

Could you tell me if you are mounting your filesystems async?
I am looking at the problem (in filesystem mode -- unfortunately
meant to be in documentation mode.)

John