From owner-freebsd-current Fri Dec 28 9: 6: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (Postfix) with ESMTP id CCDBD37B419 for ; Fri, 28 Dec 2001 09:06:01 -0800 (PST) Received: from nutty.singapore.sun.com ([129.158.72.188]) by mercury.Sun.COM (8.9.3+Sun/8.9.3) with SMTP id JAA23239 for ; Fri, 28 Dec 2001 09:06:00 -0800 (PST) Received: (qmail 5194 invoked by uid 99407); Sat, 29 Dec 2001 01:05:59 +0800 (SGT) Date: Sat, 29 Dec 2001 01:05:59 +0800 From: KT Sin To: current@FreeBSD.ORG Subject: memory backed filesystem corruption Message-ID: <20011228170556.GA4995@nutty.Singapore.Sun.COM> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.24i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi My userland and kernel were rebuilt after running cvsup on Christmas day. Right after that, files created on /tmp which is swap-backed get corrupted easily. I was trying to build mozilla and everytime I untarred the source into /tmp, I would get about 10 random files corrupted. Each of these files has one or two chunks of data replaced with null bytes (^@). However, I didn't get the same error whenever I untarred into a physical disk backed filesystem. Has anyone experienced this problem? Can someone please try and confirm? Thanks kt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message