From owner-freebsd-current Sun Dec 17 14:19:27 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA27118 for current-outgoing; Sun, 17 Dec 1995 14:19:27 -0800 (PST) Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA27112 for ; Sun, 17 Dec 1995 14:19:24 -0800 (PST) Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by mail.barrnet.net (8.7.1/MAIL-RELAY-LEN) with ESMTP id NAA22057 for ; Tue, 12 Dec 1995 13:21:41 -0800 (PST) Received: (from mark@localhost) by linus.demon.co.uk (8.7.3/8.7.3) id VAA00447 for current@freebsd.org; Tue, 12 Dec 1995 21:18:40 GMT Message-Id: <199512122118.VAA00447@linus.demon.co.uk> From: mark@linus.demon.co.uk (Mark Valentine) Date: Tue, 12 Dec 1995 21:18:39 +0000 X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: current@FreeBSD.ORG Subject: padded files Sender: owner-current@FreeBSD.ORG Precedence: bulk I've had a couple of header files apparently get padded out to an 8K boundary with NULs during a make world today (small sample: might have been a page boundary). This was on an up-to-date kernel. The modification time on the files was "just a minute ago", when the only feasible operation on them was cpp reading them... (This is a single user machine, not connected to any network at the time.) I've also been getting a few of the previously reported "attempt to write meta-data" messages, but not at the same time as these file corruptions. Could some of the recent innocuous changes possibly be not so innocuous, or uncovering old bugs? System is a 486DX2/66, 16MB RAM, AHA1542C (no bounce buffers). Mark. -- "Tigers will do ANYTHING for a tuna fish sandwich." "We're kind of stupid that way." *munch* *munch*