From owner-freebsd-current@FreeBSD.ORG  Thu May 18 18:19:22 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 51F7016A549
	for <freebsd-current@freebsd.org>; Thu, 18 May 2006 18:19:22 +0000 (UTC)
	(envelope-from thomas@hardy.tmseck.homedns.org)
Received: from smtp2.netcologne.de (smtp2.netcologne.de [194.8.194.218])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D0F3B43D45
	for <freebsd-current@freebsd.org>; Thu, 18 May 2006 18:19:21 +0000 (GMT)
	(envelope-from thomas@hardy.tmseck.homedns.org)
Received: from laurel.tmseck.homedns.org (xdsl-213-196-221-110.netcologne.de
	[213.196.221.110])
	by smtp2.netcologne.de (Postfix) with SMTP id EBEA44B8F
	for <freebsd-current@freebsd.org>;
	Thu, 18 May 2006 20:19:19 +0200 (MEST)
Received: (qmail 2168 invoked from network); 18 May 2006 18:19:41 -0000
Received: from unknown (HELO hardy.tmseck.homedns.org) (192.168.1.2)
	by 0 with SMTP; 18 May 2006 18:19:41 -0000
Received: from hardy.tmseck.homedns.org (localhost [127.0.0.1])
	by hardy.tmseck.homedns.org (8.13.6/8.13.6) with ESMTP id
	k4IIJI18001151; Thu, 18 May 2006 20:19:18 +0200 (CEST)
	(envelope-from thomas@hardy.tmseck.homedns.org)
Received: (from thomas@localhost)
	by hardy.tmseck.homedns.org (8.13.6/8.13.6/Submit) id k4IIJHL7001150;
	Thu, 18 May 2006 20:19:17 +0200 (CEST) (envelope-from thomas)
Date: Thu, 18 May 2006 20:19:17 +0200 (CEST)
Message-Id: <200605181819.k4IIJHL7001150@hardy.tmseck.homedns.org>
From: tmseck-lists@netcologne.de (Thomas-Martin Seck)
To: Yar Tikhiy <yar@comp.chem.msu.su>
In-Reply-To: <20060518151232.GA37743@comp.chem.msu.su>
X-Newsgroups: gmane.os.freebsd.current
X-Attribution: tms
Cc: freebsd-current@freebsd.org
Subject: Re: Root FS corruption
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 18 May 2006 18:19:22 -0000

* Yar Tikhiy <yar@comp.chem.msu.su>:

> I saw the following / corruption in a fresh CURRENT when using
> nextboot.  Of course, it wasn't the fault of nextboot itself,
> nextboot simply was the only utility to modify / in my case.
> 
> I found the contents of nextboot.conf once in my custom /root/supfile,
> the other time in the stock /etc/protocols.  /etc/protocols was
> large enough to see how the corruption had happened: the first
> fragment, 2048 bytes, of the file was replaced by the contents of
> nextboot.conf, zero padded.
>
> The / was a usual 2048/16384 UFS2 without soft-updates.  The kernel
> was GENERIC.  Forced fsck reported no problems at all.  The / had
> never been dirty because I used nextboot to boot single-user with
> all FSen read-only and investigate a panic unrelated to FS.
> 
> Did any one see a similar problem of fragment mis-allocation?

I experienced the exact same corruption some months ago with a RELENG_6
test system I update regularly. Unfortunately, this corruption happened
only once, I was never able to reproduce it since.

The kernel is a stripped down GENERIC, /root is a 2048/16384 UFS2 fs.