From owner-freebsd-current@FreeBSD.ORG Wed May 21 00:51:35 2003 Return-Path: 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 06DCA37B401 for ; Wed, 21 May 2003 00:51:35 -0700 (PDT) Received: from franky.speednet.com.au (franky.speednet.com.au [203.57.65.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97B7843FA3 for ; Wed, 21 May 2003 00:51:33 -0700 (PDT) (envelope-from andyf@speednet.com.au) Received: from hewey.af.speednet.com.au (hewey.af.speednet.com.au [203.38.96.242])h4L7pVqe049638; Wed, 21 May 2003 17:51:31 +1000 (EST) (envelope-from andyf@speednet.com.au) Received: from hewey.af.speednet.com.au (hewey.af.speednet.com.au [172.22.2.17])h4L7pTYm005515; Wed, 21 May 2003 17:51:29 +1000 (EST) (envelope-from andyf@speednet.com.au) Date: Wed, 21 May 2003 17:51:28 +1000 (EST) From: Andy Farkas X-X-Sender: andyf@hewey.af.speednet.com.au To: Bruce Evans In-Reply-To: <20030521163526.I30051@gamplex.bde.org> Message-ID: <20030521174255.H93323-100000@hewey.af.speednet.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Jun Kuriyama cc: Current 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2003 07:51:35 -0000 On Wed, 21 May 2003, Bruce Evans wrote: > 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 ST1 20 ST2 20 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. Is there any way to indicate that this was removable media to vfs? Maybe it could not panic in this case but rather fail gracefully. -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/