From owner-freebsd-bugs  Thu Apr 30 07:30:11 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA17293
          for freebsd-bugs-outgoing; Thu, 30 Apr 1998 07:30:11 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA17267;
          Thu, 30 Apr 1998 07:30:08 -0700 (PDT)
          (envelope-from gnats)
Received: from pccejkar.dcse.fee.vutbr.cz (pccejkar.dcse.fee.vutbr.cz [147.229.9.118])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16418
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 30 Apr 1998 07:23:17 -0700 (PDT)
          (envelope-from xcejka00@pccejkar.dcse.fee.vutbr.cz)
Received: (from xcejka00@localhost)
	by pccejkar.dcse.fee.vutbr.cz (8.8.8/8.8.8) id QAA00382;
	Thu, 30 Apr 1998 16:23:54 +0200 (CEST)
	(envelope-from xcejka00)
Message-Id: <199804301423.QAA00382@pccejkar.dcse.fee.vutbr.cz>
Date: Thu, 30 Apr 1998 16:23:54 +0200 (CEST)
From: xcejka00@dcse.fee.vutbr.cz
Reply-To: xcejka00@dcse.fee.vutbr.cz
To: FreeBSD-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: 3.2
Subject: kern/6465: File contents are zeroed after reboot
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         6465
>Category:       kern
>Synopsis:       File contents are zeroed after reboot
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Apr 30 07:30:03 PDT 1998
>Last-Modified:
>Originator:     Rudolf Cejka
>Organization:
FEE TU Brno, Czech Republic
>Release:        FreeBSD 3.0-CURRENT i386
>Environment:

	First of all, I tried this on "FreeBSD 3.0-980304-SNAP i386"
	(GENERIC kernel too). File contents were zeroed totally. Now,
	I'm trying today's -CURRENT (Thu Apr 30 1998) and it looks
	"better" - files are zeroed only partially... But it still does
	not look very well... (ffs is my root filesystem.)

>Description:

	Look at how-to-repeat. When I'm trying to use nullfs layer,
	everything looks well until reboot. But after reboot - contents
	of files are disrupted, if they were copied via nullfs layer.

>How-To-Repeat:

	It's very easy. Just type these commands:
	(Important note: File "any_file" must be long enough, 30000 bytes or
	more for example.)

	cd /
	mkdir test
	mount -t null /test /mnt
	cp any_file /mnt/test.bad
	cp any_file /test/test.ok
	diff /test/test.bad /test/test.ok
	... Files are the same, OK
	... Reboot Your machine ...
	diff /test/test.bad /test/test.ok
	... And files differ!!!Lengths are the same, but content of
	    /test/test.bad is partially zeroed

>Fix:
	
	I tried to find this bug, but I haven't any idea. I think - the
	problem is in ffs or memory management (nullfs looks normally).

>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message