From owner-freebsd-current Wed Jul 22 20:21:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26161 for freebsd-current-outgoing; Wed, 22 Jul 1998 20:21:56 -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 UAA26156 for ; Wed, 22 Jul 1998 20:21:54 -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 XAA20963; Wed, 22 Jul 1998 23:21:10 -0400 (EDT) Date: Wed, 22 Jul 1998 23:21:10 -0400 (EDT) From: Brian Feldman To: "Jordan K. Hubbard" cc: Alfred Perlstein , Joel Ray Holveck , freebsd-current@FreeBSD.ORG Subject: Re: vn subsystem In-Reply-To: <27156.900992019@time.cdrom.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 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 newfs_msdos /dev/vn0 mount /dev/vn0 /msdos (oops, should this matter anyway?) mount_msdos /dev/vn0 /msdos *crash* Here follows the backtrace, I've still got the core and kernel, by the way. #0 boot (howto=256) at ../../kern/kern_shutdown.c:286 #1 0xf0119147 in panic ( fmt=0xf01c2967 "vm_fault: fault on nofault entry, addr: %lx") at ../../kern/kern_shutdown.c:427 #2 0xf01c2ae6 in vm_fault (map=0xf024f9d8, vaddr=4078645248, fault_type=3 '\003', fault_flags=0) at ../../vm/vm_fault.c:233 #3 0xf01e424c in trap_pfault (frame=0xf58977e0, usermode=0) at ../../i386/i386/trap.c:761 #4 0xf01e3eef in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -216322048, tf_esi = -213143552, tf_ebp = -175540152, tf_isp = -175540216, tf_ebx = 4096, tf_edx = -213147136, tf_ecx = 128, tf_eax = -3178496, tf_trapno = 12, tf_err = 2, tf_eip = -266459326, tf_cs = 8, tf_eflags = 66070, tf_esp = -175539904, tf_ss = -175539912}) at ../../i386/i386/trap.c:396 #5 0xf01e2742 in generic_bcopy () #6 0xf01b865f in ffs_read (ap=0xf589791c) at ../../ufs/ufs/ufs_readwrite.c:205 #7 0xf0104738 in vnstrategy (bp=0xf25a09f8) at vnode_if.h:331 #8 0xf014811e in spec_strategy (ap=0xf58979a4) at ../../miscfs/specfs/spec_vnops.c:556 #9 0xf0147829 in spec_vnoperate (ap=0xf58979a4) at ../../miscfs/specfs/spec_vnops.c:127 #10 0xf01c014d in ufs_vnoperatespec (ap=0xf58979a4) at ../../ufs/ufs/ufs_vnops.c:2305 #11 0xf01347a9 in bread (vp=0xf57f5f80, blkno=1, size=4096, cred=0x0, bpp=0xf58979f8) at vnode_if.h:891 #12 0xf014b161 in fillinusemap (pmp=0xf0cd0000) at ../../msdosfs/msdosfs_fat.c:946 #13 0xf014d16c in mountmsdosfs (devvp=0xf57f5f80, mp=0xf0c49800, p=0xf58095c0, argp=0xf5897ac0) at ../../msdosfs/msdosfs_vfsops.c:715 #14 0xf014ca75 in msdosfs_mount (mp=0xf0c49800, path=0xefbfd969 "/msdos", data=0xefbfd558 "`", ndp=0xf5897ea8, p=0xf58095c0) at ../../msdosfs/msdosfs_vfsops.c:321 #15 0xf013d6fe in mount (p=0xf58095c0, uap=0xf5897f84) at ../../kern/vfs_syscalls.c:280 #16 0xf01e4ab3 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 0, tf_esi = -272639639, tf_ebp = -272639784, tf_isp = -175538220, tf_ebx = 0, tf_edx = 0, tf_ecx = 0, tf_eax = 21, tf_trapno = 12, tf_err = 7, tf_eip = 21157, tf_cs = 31, tf_eflags = 582, tf_esp = -272641896, tf_ss = 39}) at ../../i386/i386/trap.c:1031 #17 0x52a5 in ?? () #18 0x107e in ?? () Cheers, Brian Feldman green@unixhelp.org On Mon, 20 Jul 1998, Jordan K. Hubbard wrote: > > hrm, not really there was some traffic on the lists a few weeks/months > > back about it being broken, but that's all i know. > > Erm, wonderful. Can we have some commentary from someone who's > actually proven this either way now? Like I said, my own usage of the > vn driver has not shown any such instability. If someone who's > _actually used it_ can now comment on its instability, we'll get a lot > further. > > - Jordan > > 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