From owner-freebsd-stable@FreeBSD.ORG Sun Jan 15 04:53:08 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 037921065676 for ; Sun, 15 Jan 2012 04:53:08 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-tul01m020-f182.google.com (mail-tul01m020-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id C3AD28FC14 for ; Sun, 15 Jan 2012 04:53:07 +0000 (UTC) Received: by obbta17 with SMTP id ta17so5365301obb.13 for ; Sat, 14 Jan 2012 20:53:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=m23qq/S1ZkR2GR1QRAW4pctwq79WC+KcP8A8xQphKHg=; b=JPHHj3UZxlyHnKaGizVaH/RL1rVdGqk//WCoRwNbRzS6LvRdWGHndih3ZgBeimK0r6 h4I9kcxsy4WMjDxWk6mhOfMPivQsaqXUIt8ahtG2h26kHH51nJxM374PBkPVlq8QZIu/ bC6Bjv/uF2tn6P9SXFIJlm/0GNWHxuqycLxWQ= MIME-Version: 1.0 Received: by 10.182.41.5 with SMTP id b5mr3319938obl.79.1326603187276; Sat, 14 Jan 2012 20:53:07 -0800 (PST) Received: by 10.182.152.6 with HTTP; Sat, 14 Jan 2012 20:53:07 -0800 (PST) In-Reply-To: References: Date: Sat, 14 Jan 2012 20:53:07 -0800 Message-ID: From: Garrett Cooper To: Joe Holden Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: 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:53:08 -0000 On Sat, Jan 14, 2012 at 8:20 PM, Joe Holden wrote: > =A0Guys.... > > 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 forgo= t > to unmount it beforehand, however as a result there is now inconsistencie= s > and probably data corruption or even missing data on other important > filesystems (ie; /, /var etc) because there wasn't even a sync or any kin= d > 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 b= ox > into one thats dead in the water seems a little extreme. That's usually the sign that something went bonkers with the underlying filesystem to the extent that it's corrupt beyond all repair. In this case though, I wouldn't necessarily say that the md-backed filesystem is the one that's corrupt -- it might be the root filesystem. What version of FreeBSD are you using and what do you have enabled in the filesystem (FFS, UFS1, UFS2, SU, SUJ..)? Thanks, -Garrett