From owner-freebsd-stable@FreeBSD.ORG Sun Jan 15 04:46:04 2012 Return-Path: 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 59ADB106564A for ; Sun, 15 Jan 2012 04:46:04 +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 D18C48FC15 for ; Sun, 15 Jan 2012 04:46:03 +0000 (UTC) Received: by lahd3 with SMTP id d3so1387985lah.13 for ; Sat, 14 Jan 2012 20:46:02 -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=4X+v3lOBDqkYeDLCaFyb6YLI1vJf+mf4tojNEa1pZvo=; b=gPc6P+ehkkUy1Wfvw+QGqzf/ZBi/sVm7QrxL9GQOt/AQhqISIHlZvHFm1vdTQ1m2Zg KWzlRRA7/1pKDdTk9IcqM0NwceAvycSoXcUY0r7wE8nupNULvDnFbFoHOQHjCpdULoGw 8K6yFJAps7n0lgx7/y0abUit811J/lVJcbcI4= MIME-Version: 1.0 Received: by 10.152.110.6 with SMTP id hw6mr3470817lab.37.1326602762490; Sat, 14 Jan 2012 20:46:02 -0800 (PST) Received: by 10.152.11.131 with HTTP; Sat, 14 Jan 2012 20:46:02 -0800 (PST) Date: Sun, 15 Jan 2012 04:46:02 +0000 Message-ID: From: Joe Holden 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Jan 2012 04:46:04 -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