From owner-freebsd-current Thu Jul 23 11:00:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28583 for freebsd-current-outgoing; Thu, 23 Jul 1998 11:00:23 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zone.baldcom.net (green@zone.BALDCOM.NET [205.232.46.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28565 for ; Thu, 23 Jul 1998 11:00:20 -0700 (PDT) (envelope-from green@zone.baldcom.net) Received: from localhost (green@localhost) by zone.baldcom.net (8.8.8/8.8.7) with SMTP id NAA00655; Thu, 23 Jul 1998 13:59:39 -0400 (EDT) Date: Thu, 23 Jul 1998 13:59:39 -0400 (EDT) From: Brian Feldman To: Luoqi Chen cc: jkh@time.cdrom.com, bright@hotjobs.com, freebsd-current@FreeBSD.ORG, joelh@gnu.org Subject: Re: vn subsystem In-Reply-To: <199807231418.KAA16043@lor.watermarkgroup.com> 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 No, newfs_msdos'ing and then mounting /dev/vn0, tho wrong, would have worked fine, and have previously. What I did later was I booted bochs, formatted the drive from inside bochs, installed DOS, etc. And then realized, stupidly, I couldn't mount the MS-DOS formatted drive because I wasn't using the right _slice_; so I mount dev/vn0s1c, and it works fine then. This is the same old problem as before... last time I saw it was with floppy disks, and I guess I thought it didn't affect other media like vn(4). BTW, if you didn't know, your mremap() for linux band-aid was merged into -CURRENT. Cheers, Brian Feldman green@unixhelp.org On Thu, 23 Jul 1998, Luoqi Chen wrote: > > > > Alright, it's unstable for large files. observe the following scenario and > > appropriate coredump: > > -rw-r--r-- 1 green green 528482304 Jul 22 23:11 /home/green/msdos.drv > > vnconfig -c -s io -s labels /dev/vn0 /home/green/msdos.drv > ^^^^^^ > Is there something missing here? Since the option labels is set, should > you do a fdisk before newfs? If you don't, vn driver will try to use dosfs > boot sector as an MBR, and funny things could happen. > > > newfs_msdos /dev/vn0 > > mount /dev/vn0 /msdos (oops, should this matter anyway?) > > mount_msdos /dev/vn0 /msdos > > *crash* > > -lq > > 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