From owner-freebsd-current Sat Feb 6 13:04:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22931 for freebsd-current-outgoing; Sat, 6 Feb 1999 13:04:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-19.ppp.wenet.net [206.15.85.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA22926 for ; Sat, 6 Feb 1999 13:04:08 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.2/8.9.1) with ESMTP id NAA09792; Sat, 6 Feb 1999 13:00:59 -0800 (PST) (envelope-from garbanzo@hooked.net) Date: Sat, 6 Feb 1999 13:00:59 -0800 (PST) From: Alex Zepeda To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: msdosfs/vn trouble, doscmd "nicety", fd trouble In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 6 Feb 1999, Brian Feldman wrote: > When I mount a floppy image (msdos, using the vn device), I soon get: > panic: zone: entry not free When I needed to copy some stuff onto a "boot disk", this worked fine with my Feb 1 kernel. Installing Win95 on Bochs OTOH and mounting the resulting disk image (was a pain, didn't work).... > I'll try do some more testing on this... I really don't know if it's a problem > with msdosfs or vn. It will only show p (like this) with INVARIANTS on. As I said above... it was rather weird that the hdd image I was using wouldn't mount when I vnconfig'd it and mount -tmsdosfs'd it.. it claimed the bpb was invalid.. Win95 under Bochs grok'd it.. > With this, I'm wondering if everyone's floppy drives work fine and if their > drives work fine on an AcerLabs socket 7 motherboard. If so, maybe I can > scrounge up a different floppy drive and try it out, but it really seems > to not be a hardware problem. The only floppy oddity I've noticed of late was when I tried making disk images of 1.68mb disks. dd if=/dev/fd0.1720.. worked fine and generated disk images fine.. but generated a LOT of error messages towards the end like: fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3364 of 3364-3367 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 5) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40 ST1 4 ST2 10 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40 ST1 4 ST2 10 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3364 of 3364-3367 (ST0 40 ST1 4 ST2 10 cyl 80 hd 0 sec 5) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3364 of 3364-3367 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 5) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3360 of 3360-3363 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 1) fd0c: hard error reading fsbn 3364 of 3364-3367 (ST0 40 ST1 4 ST2 0 cyl 80 hd 0 sec 5) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message