From owner-freebsd-current@FreeBSD.ORG  Tue May 20 23:39:37 2003
Return-Path: <owner-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 4661037B401
	for <freebsd-current@freebsd.org>;
	Tue, 20 May 2003 23:39:37 -0700 (PDT)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D495E43F3F
	for <freebsd-current@freebsd.org>;
	Tue, 20 May 2003 23:39:35 -0700 (PDT)	(envelope-from bde@zeta.org.au)
Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246])
	by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id QAA13159;
	Wed, 21 May 2003 16:39:26 +1000
Date: Wed, 21 May 2003 16:39:25 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: Jun Kuriyama <kuriyama@imgsrc.co.jp>
In-Reply-To: <7m4r3onc7i.wl@black.imgsrc.co.jp>
Message-ID: <20030521163526.I30051@gamplex.bde.org>
References: <7m4r3onc7i.wl@black.imgsrc.co.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Current <freebsd-current@freebsd.org>
Subject: Re: panic: mount: lost mount
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
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: Wed, 21 May 2003 06:39:37 -0000

On Wed, 21 May 2003, Jun Kuriyama wrote:

> With today's current, I've got a panic with bad floppy.
>
> fd0: hard error cmd=read fsbn 57 of 56-63 (ST0 44<abnrml,top_head> ST1 20<bad_crc> ST2 20<bad_crc> cyl 1 hd 1 sec 4)
> panic: mount: lost mount
> cpuid = 1; lapic.id = 01000000
> Debugger("panic")
> Stopped at      Debugger+0x55:  xchgl   %ebx,in_Debugger.0
> db> trace
> Debugger(c03eb40e,1000000,c03f085e,ebc05b80,1) at Debugger+0x55
> panic(c03f085e,ebc05ba4,c03f0812,46a,c896b720) at panic+0x11f
> vfs_mount(c896b720,c7eafd40,c8a32b80,0,bfbfece0) at vfs_mount+0xa80
> mount(c896b720,ebc05d10,c0407bf6,3fb,4) at mount+0xb8
> syscall(2f,2f,2f,80a210f,bfbff6a4) at syscall+0x26e
> Xint0x80_syscall() at Xint0x80_syscall+0x1d

Unfortunately, this is fairly normal file system behaviour when a critical
block is unreadable or damaged.  Here vfs detects a problem that it knows
it cannot handle, and panics.

Bruce