From owner-freebsd-current Thu Jul 23 07:19:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA22946 for freebsd-current-outgoing; Thu, 23 Jul 1998 07:19:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA22938 for ; Thu, 23 Jul 1998 07:19:51 -0700 (PDT) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id KAA16043; Thu, 23 Jul 1998 10:18:26 -0400 (EDT) (envelope-from luoqi) Date: Thu, 23 Jul 1998 10:18:26 -0400 (EDT) From: Luoqi Chen Message-Id: <199807231418.KAA16043@lor.watermarkgroup.com> To: green@zone.baldcom.net, jkh@time.cdrom.com Subject: Re: vn subsystem Cc: bright@hotjobs.com, freebsd-current@FreeBSD.ORG, joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 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