From owner-freebsd-current Mon Feb 11 19:49: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from newman2.bestweb.net (newman2.bestweb.net [209.94.102.67]) by hub.freebsd.org (Postfix) with ESMTP id E43C037B65A; Mon, 11 Feb 2002 18:19:13 -0800 (PST) Received: from okeeffe.bestweb.net (okeefe.bestweb.net [209.94.100.110]) by newman2.bestweb.net (Postfix) with ESMTP id 316352307D; Mon, 11 Feb 2002 21:18:10 -0500 (EST) Received: by okeeffe.bestweb.net (Postfix, from userid 0) id A8AC79F3E8; Mon, 11 Feb 2002 21:12:47 -0500 (EST) Date: Mon, 11 Feb 2002 11:55:48 -0500 (EST) From: Mikhail Teterin Subject: Re: panic: bdwrite: buffer is not busy To: bde@zeta.org.au Cc: jhb@FreeBSD.ORG, current@FreeBSD.ORG Message-Id: <20020212021247.A8AC79F3E8@okeeffe.bestweb.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 11 Feb, Bruce Evans wrote: > On Sun, 10 Feb 2002, Mikhail Teterin wrote: > >> On 10 Feb, Bruce Evans wrote: >> > This is a well known bug in the device layer. I reported it on >> > 2001/12/26 and fixed it locally a little later. See the thread in >> > -current about "panic during fdisk'ing a md(4) device" for patches. >> >> Fdisk I don't really need, but attempting to newfs the floppy caused >> the same panic :-\ And mounting the already formatted floppy leads to >> "invalid argument". Could we have this fixed soon, please? The >> inability to access a floppy is a great setback for my local FreeBSD >> advocacy efforts :-) > > Newfs'ing /dev/fd0 (instead of /dev/fd0[a-c]) should work better. That's what I was doing... > Not using devfs might work too. Kind of grew used to it by now :-) Let's me keep / mounted read-only :-) Thanks! -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message