From owner-freebsd-stable@FreeBSD.ORG  Sun Jan 15 04:42:14 2012
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B9201106564A
	for <freebsd-stable@freebsd.org>; Sun, 15 Jan 2012 04:42:14 +0000 (UTC)
	(envelope-from jwhlists@gmail.com)
Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com
	[209.85.215.54])
	by mx1.freebsd.org (Postfix) with ESMTP id 4090C8FC0A
	for <freebsd-stable@freebsd.org>; Sun, 15 Jan 2012 04:42:13 +0000 (UTC)
Received: by lahd3 with SMTP id d3so1387158lah.13
	for <freebsd-stable@freebsd.org>; Sat, 14 Jan 2012 20:42:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=mime-version:date:message-id:subject:from:to:content-type;
	bh=sox5t1RUlueUx7EcAi1YaAn+YlKXzw211qlwL0fUeME=;
	b=LHS1x8p7E/07OeeJLBQGW/FIvy92vM+DDfrn+XdOFBF7ETvvwsL8UbAchW2o7KEDc6
	rQZvfaSqBAkQIhHQ7waSO9OMLhnMEV74FsIAuRcCYEHVOaAiYSbYsKrXI7YvsXgajSuI
	tAD3q9ocBIIN4/BOWRrYgi8APQAMFFHoIqQA8=
MIME-Version: 1.0
Received: by 10.152.131.202 with SMTP id oo10mr3321337lab.40.1326601229274;
	Sat, 14 Jan 2012 20:20:29 -0800 (PST)
Received: by 10.152.37.33 with HTTP; Sat, 14 Jan 2012 20:20:29 -0800 (PST)
Date: Sun, 15 Jan 2012 04:20:29 +0000
Message-ID: <CAD-04WOKH6yb0tjcM=pu86kzTfFej+c0E-v9AMC9VyEDn4HSOg@mail.gmail.com>
From: Joe Holden <jwhlists@gmail.com>
To: freebsd-stable@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.5
Subject: UFS corruption panic
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Jan 2012 04:42:14 -0000

 Guys....

Is a panic **really** appropriate for a filesystem that isn't even in
fstab?

ie;
panic: ufs_dirbad: /mnt: bad dir ino 3229 at offset 0: mangled entry

Which happened to be an file-backed md volume that got changed as I forgot
to unmount it beforehand, however as a result there is now inconsistencies
and probably data corruption or even missing data on other important
filesystems (ie; /, /var etc) because there wasn't even a sync or any kind
of other sensible behaviour.

This is on a production box, which also has gmirror so I now have no idea
what state it's going to be in when I can get a display attached.

Surely the appropriate response here for non-critical filesystems is to
warn and suggest manually inspecting it as turning a working production box
into one thats dead in the water seems a little extreme.

J