Date: Wed, 21 May 2003 17:51:28 +1000 (EST) From: Andy Farkas <andyf@speednet.com.au> To: Bruce Evans <bde@zeta.org.au> Cc: Current <freebsd-current@freebsd.org> Subject: Re: panic: mount: lost mount Message-ID: <20030521174255.H93323-100000@hewey.af.speednet.com.au> In-Reply-To: <20030521163526.I30051@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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<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.
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030521174255.H93323-100000>