From owner-freebsd-fs Sun May 11 11:10:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA07272 for fs-outgoing; Sun, 11 May 1997 11:10:14 -0700 (PDT) Received: from gaia.coppe.ufrj.br (root@[146.164.5.200]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA07267 for ; Sun, 11 May 1997 11:10:12 -0700 (PDT) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.5/8.7.3) id PAA09593; Sun, 11 May 1997 15:10:09 -0300 (EST) From: Joao Carlos Mendes Luis Message-Id: <199705111810.PAA09593@gaia.coppe.ufrj.br> Subject: NFS between 2.2.1 and 2.1.7.1 To: fs@freebsd.org Date: Sun, 11 May 1997 15:10:09 -0300 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I've recently upgraded some of my NFS clients from FreeBSD 2.1.7 to FreeBSD 2.2.1-R. The server is too important to risc an upgrade right now. Also, on both systems I also upgraded from ethernet 10M (ne2000 and DEC 21040) to ethernet 100M (3c905). The hardware change some weeks after upgrading the OS version. Since the hardware upgrade, the client machine seens to be extremely problematic about NFS. It's always blocking NFS calls, and I don't know why. Here's some info: Client: zeus::root [541] ps -alx | grep nfs 0 109 1 0 2 0 232 12 accept Is ?? 0:00.01 nfsd: master 0 111 109 0 2 0 224 12 nfsd I ?? 0:00.00 nfsd: server 0 112 109 0 2 0 224 12 nfsd I ?? 0:00.00 nfsd: server 0 113 109 0 2 0 224 12 nfsd I ?? 0:00.00 nfsd: server 0 114 109 0 2 0 224 12 nfsd I ?? 0:00.02 nfsd: server 0 124 1 0 2 0 208 12 sbwait D ?? 0:00.18 nfsiod -n 4 0 125 1 0 -1 0 208 12 nfsrcv D ?? 0:00.07 nfsiod -n 4 0 126 1 0 -1 0 208 12 nfsrcv D ?? 0:00.01 nfsiod -n 4 0 127 1 0 -1 0 208 12 nfsrcv I ?? 0:00.01 nfsiod -n c 100 4955 4937 7 -1 0 2136 2576 nfsrcv I p2 0:03.03 sdr 100 4918 1 0 -1 0 220 772 nfsrcv I v0 0:00.13 xbiff 100 4951 1 0 -1 0 6768 2776 nfsrcv D v0 0:06.19 /usr/local/l Server: gaia::jonny [328] ps -alx | grep nfs 0 185 1 0 2 0 324 40 netcon Is ?? 0:00.02 nfsd: master 0 187 185 0 2 0 316 12 nfsd I ?? 0:00.00 nfsd: server 0 188 185 0 2 0 316 12 nfsd S ?? 0:08.28 nfsd: server 0 189 185 0 2 0 316 12 nfsd I ?? 0:00.13 nfsd: server 0 190 185 0 2 0 316 12 nfsd I ?? 0:00.01 nfsd: server 0 194 1 0 10 0 208 12 nfsidl I ?? 0:01.07 nfsiod -n 4 0 195 1 0 10 0 208 12 nfsidl I ?? 0:00.07 nfsiod -n 4 0 196 1 0 10 0 208 12 nfsidl I ?? 0:00.34 nfsiod -n 4 0 197 1 0 10 0 208 12 nfsidl I ?? 0:00.08 nfsiod -n 4 The client seems to be locked at the "nfsrcv" resource, when it should be at "nfsidl". It's not a network problem (at least, not a permanent one), since I can still telnet or everywhere. I shall try to change the nics and maybe the network cable (it's not a very good one), but this really looks like a software problem. Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 ( Job ) jonny@cisi.coppe.ufrj.br Network Manager UFRJ/COPPE/CISI Universidade Federal do Rio de Janeiro From owner-freebsd-fs Sun May 11 11:36:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA08412 for fs-outgoing; Sun, 11 May 1997 11:36:03 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA08398 for ; Sun, 11 May 1997 11:35:55 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id TAA01148; Sun, 11 May 1997 19:35:20 +0100 (BST) Date: Sun, 11 May 1997 19:35:20 +0100 (BST) From: Doug Rabson To: Joao Carlos Mendes Luis cc: fs@freebsd.org Subject: Re: NFS between 2.2.1 and 2.1.7.1 In-Reply-To: <199705111810.PAA09593@gaia.coppe.ufrj.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 11 May 1997, Joao Carlos Mendes Luis wrote: > Hi, > > I've recently upgraded some of my NFS clients from FreeBSD 2.1.7 to > FreeBSD 2.2.1-R. The server is too important to risc an upgrade right > now. Also, on both systems I also upgraded from ethernet 10M (ne2000 > and DEC 21040) to ethernet 100M (3c905). The hardware change some weeks > after upgrading the OS version. I have fixed a number of bugs in NFS since 2.2.1 was released. I haven't yet merged the fixes into the 2.2 branch but they certainly make 3.0 a lot more stable for heavy use of NFS, both NFSv2 and NFSv3. If you are not already, you should track the 2.2 branch with CVSup and watch for the NFS fixes when I commit then (in a week or two probably). > The client seems to be locked at the "nfsrcv" resource, when it should be > at "nfsidl". It's not a network problem (at least, not a permanent one), > since I can still telnet or everywhere. > > I shall try to change the nics and maybe the network cable (it's not > a very good one), but this really looks like a software problem. If that doesn't work, use 'tcpdump -vv -s300 port nfs' to get a packet trace and maybe we can figure out what is broken. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-fs Sun May 11 12:18:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA09803 for fs-outgoing; Sun, 11 May 1997 12:18:03 -0700 (PDT) Received: from train.tgci.com ([205.185.169.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA09798 for ; Sun, 11 May 1997 12:18:01 -0700 (PDT) Received: from emilyd ([206.250.85.68]) by train.tgci.com (8.6.12/8.6.9) with SMTP id MAA23980 for ; Sun, 11 May 1997 12:44:39 -0700 Message-Id: <199705111944.MAA23980@train.tgci.com> Comments: Authenticated sender is From: "Riley J. McIntire" To: freebsd-fs@FreeBSD.ORG Date: Sun, 11 May 1997 12:17:16 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: (Fwd) File descriptors-do I have Bad Breath? Reply-to: chaos@tgci.com Priority: normal X-mailer: Pegasus Mail for Win32 (v2.42a) Sender: owner-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Apologies if this is off-topic for freebsd-fs, but I either have very bad breath or am asking silly questions that don't deserve to be answered on Questions. Could someone take a look at my questions and at least tell me which manual RTFM refers to? :) ------- Forwarded Message Follows ------- From: Self To: questions@FreeBSD.ORG Subject: File descriptors Reply-to: chaos@tgci.com Date: Sat, 10 May 1997 13:27:28 I'm getting some bad file descriptor errors that prevented me from compiling a new kernal (I'm new...), and got some help here about that. But I'm not clear about what causes bad file descriptors or even what they are/do. I've searched the docs, man hier, man fd and am still not clear. Do they indicate the state a file is in? Open, writable, locked? What constitutes a bad one? Is it caused by bad hardware? Disks? Controllers? I'm had stuff like this on more that one occasion: find: /usr/include/machine: Bad file descriptor find: /usr/src/gnu/usr.bin/cc/cc_int/loop.c: Bad file descriptor find: /usr/src/gnu/usr.bin/cc/cc_int/obstack.c: Bad file descriptor etc Last time I had to use clri and some other stuff to fix it. fsck doesn't take care of it. I am going to replace the IDE 1.2GB Maxtor with a Seagate scsi for this low volume webserver( and move it from 2.1.7 to 2.2.1--a good idea???). Will this fix the cause? Is a bad disk causing this? I haven't done a low-level format, but plan on it later. Should/will this show up anything? Could someone explain or point me to some documentation on this? Ciao, Riley From owner-freebsd-fs Sun May 11 13:54:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA12475 for fs-outgoing; Sun, 11 May 1997 13:54:33 -0700 (PDT) Received: from gaia.coppe.ufrj.br (root@[146.164.5.200]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA12465 for ; Sun, 11 May 1997 13:54:30 -0700 (PDT) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.5/8.7.3) id RAA11556; Sun, 11 May 1997 17:54:12 -0300 (EST) From: Joao Carlos Mendes Luis Message-Id: <199705112054.RAA11556@gaia.coppe.ufrj.br> Subject: Re: NFS between 2.2.1 and 2.1.7.1 To: dfr@nlsystems.com (Doug Rabson) Date: Sun, 11 May 1997 17:54:11 -0300 (EST) Cc: jonny@mailhost.coppe.ufrj.br, fs@freebsd.org In-Reply-To: from Doug Rabson at "May 11, 97 07:35:20 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk #define quoting(Doug Rabson) // On Sun, 11 May 1997, Joao Carlos Mendes Luis wrote: // > I've recently upgraded some of my NFS clients from FreeBSD 2.1.7 to // > FreeBSD 2.2.1-R. The server is too important to risc an upgrade right // > now. Also, on both systems I also upgraded from ethernet 10M (ne2000 // > and DEC 21040) to ethernet 100M (3c905). The hardware change some weeks // > after upgrading the OS version. // // I have fixed a number of bugs in NFS since 2.2.1 was released. I haven't // yet merged the fixes into the 2.2 branch but they certainly make 3.0 a lot // more stable for heavy use of NFS, both NFSv2 and NFSv3. Just guessing: Would it work if I simply copied the sys/nfs subdir from -current to my 2.2 branch ? // If you are not already, you should track the 2.2 branch with CVSup and // watch for the NFS fixes when I commit then (in a week or two probably). I have always followed FreeBSD-stable/src, with the ftp mirror package. If there's something similar for 2.2, I'll follow it too. // trace and maybe we can figure out what is broken. It was sending write requests, and receiving no answer at all. Maybe a problem on the server (2.1.7) side ? I also used the dumbtimer option with no success. Now I'm trying with tcp mounts, and seems to be much more stable. I'm up for more than one hour, stressing the NFS system, and had no system locks until now. Of course, it's slower. :( Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 ( Job ) jonny@cisi.coppe.ufrj.br Network Manager UFRJ/COPPE/CISI Universidade Federal do Rio de Janeiro From owner-freebsd-fs Sun May 11 14:12:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA12988 for fs-outgoing; Sun, 11 May 1997 14:12:18 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA12982 for ; Sun, 11 May 1997 14:12:13 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id WAA01362; Sun, 11 May 1997 22:11:30 +0100 (BST) Date: Sun, 11 May 1997 22:11:30 +0100 (BST) From: Doug Rabson To: Joao Carlos Mendes Luis cc: fs@freebsd.org Subject: Re: NFS between 2.2.1 and 2.1.7.1 In-Reply-To: <199705112054.RAA11556@gaia.coppe.ufrj.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 11 May 1997, Joao Carlos Mendes Luis wrote: > Just guessing: Would it work if I simply copied the sys/nfs subdir from > -current to my 2.2 branch ? I'm afraid that won't work. The filesystems interfaces have diverged somewhat between 2.2 and 3.0. > > // If you are not already, you should track the 2.2 branch with CVSup and > // watch for the NFS fixes when I commit then (in a week or two probably). > > I have always followed FreeBSD-stable/src, with the ftp mirror package. > > If there's something similar for 2.2, I'll follow it too. That would probably work. You should try CVSup though - its a much more efficient use of bandwidth and its really easy to use. Read section 16.2 in the handbook. > > // trace and maybe we can figure out what is broken. > > It was sending write requests, and receiving no answer at all. Maybe a > problem on the server (2.1.7) side ? Hmm. I just fixed a bug like that in 3.0 but that bug was definately not present in 2.1.x. I am not supporting the NFS in 2.1.x at all really, so I don't know what it could be. The NFS in 2.2 and 3.0 is really much better than 2.1. It supports the newer version 3 protocol which has much better write performance (2-3 Mb/sec on my unloaded 100baseTX test network). I am also actively supporting this version and will try to fix any bugs which I can reproduce. > > I also used the dumbtimer option with no success. Now I'm trying with > tcp mounts, and seems to be much more stable. I'm up for more than one > hour, stressing the NFS system, and had no system locks until now. > > Of course, it's slower. :( Like I said, watch for the next batch of fixes to 2.2's NFS and see if it helps. You might consider subscribing to the cvs-sys@freebsd.org mailing list so that you can see when fixes are committed to the tree. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-fs Mon May 12 03:35:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA10674 for fs-outgoing; Mon, 12 May 1997 03:35:45 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10665 for ; Mon, 12 May 1997 03:35:42 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id LAA06661; Mon, 12 May 1997 11:35:05 +0100 (BST) Date: Mon, 12 May 1997 11:35:05 +0100 (BST) From: Doug Rabson To: pius@ienet.com cc: freebsd-fs@FreeBSD.ORG, terryl@ienet.com Subject: Re: nfs cache permissions problem? In-Reply-To: <199704302151.OAA04610@iago.ienet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 30 Apr 1997 pius@ienet.com wrote: > > On Wed, 30 Apr 1997, dfr@nlsystems.com wrote: > > I know about this problem and there is an open PR for it. I don't know > > what the right fix for it is though. I can't do an ACCESS rpc for every > > cache read (apart from the performance, NFSv2 doesn't have an ACCESS rpc). > > The best I have come up with so far is to somehow associate a cred with > > each buf in the cache and only allow accesses which are allowed by the > > cred. Failures will invalidate the buf and attempt the READ rpc, allowing > > the server to do the check. > > Oops, sorry, I should have checked the PRs first. > > So the fix provided by the originator of kern/2635 would significantly > affect performance? Or perhaps it has other problems? > > Does the NFSv3 implementation fix this? How do other NFS implementations > handle this case (e.g. OpenBSD, NetBSD, Linux, Solaris)? > > Anyways, thanks very much for your help, > Pius > I have committed a fixed for this permission problem to current. Expect a fix to show up in 2.2 within a couple of weeks. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 From owner-freebsd-fs Thu May 15 17:21:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA26607 for fs-outgoing; Thu, 15 May 1997 17:21:36 -0700 (PDT) Received: from mail.calweb.com (mail.calweb.com [208.131.56.11]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA26602 for ; Thu, 15 May 1997 17:21:30 -0700 (PDT) Received: by mail.calweb.com (8.8.5/8.8.5) with ESMTP id RAA03108 for ; Thu, 15 May 1997 17:21:22 -0700 (PDT) X-SMTP: hello web1.calweb.com from cslye@calweb.com server cslye@web1.calweb.com ip 208.131.56.51 Received: (from cslye@localhost) by web1.calweb.com (8.8.5/8.8.5) id RAA26072 for fs@freebsd.org; Thu, 15 May 1997 17:21:28 -0700 (PDT) Message-Id: <199705160021.RAA26072@web1.calweb.com> Subject: panic: blkfree: freeing free block To: fs@freebsd.org Date: Thu, 15 May 1997 17:21:28 -0700 (PDT) From: "Cameron Slye" X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, I am at a dead end.. I have low leveled the drive, I have newfsed the drive, I have cvsupped and installed new kernels for the last month.. Any ideas on this error ? Background on the system, p133 running on a asus p55t2p4 with 128mb. 2 2940UW's, root drive a quantum XP31070W L912 the /news/spool drive is a TANDEM 4275-1 1717 (IBM OEM I belive) There is a dual port SMC card (Digital 21040) current pcb at 1efac8 panic: blkfree: freeing free block #0 boot (howto=260) at ../../kern/kern_shutdown.c:243 243 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:243 #1 0xf0117c03 in panic (fmt=0xf0101439 "from debugger") at ../../kern/kern_shutdown.c:367 #2 0xf0101455 in db_panic (dummy1=-266612103, dummy2=0, dummy3=-1, dummy4=0xefbff92c "") at ../../ddb/db_command.c:440 #3 0xf0101345 in db_command (last_cmdp=0xf01e3b24, cmd_table=0xf01e3974, aux_cmd_tablep=0xf01fce54) at ../../ddb/db_command.c:337 #4 0xf01014c2 in db_command_loop () at ../../ddb/db_command.c:462 #5 0xf0103ca8 in db_trap (type=3, code=0) at ../../ddb/db_trap.c:73 #6 0xf01bd07b in kdb_trap (type=3, code=0, regs=0xefbffa1c) at ../../i386/i386/db_interface.c:126 #7 0xf01c5c34 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = -267381703, tf_ebp = -272631200, tf_isp = -272631228, tf_ebx = 260, tf_edx = -266612159, tf_ecx = -2147483648, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip = -266612103, tf_cs = 8, tf_eflags = 582, tf_esp = -266612175, tf_ss = -267289704}) at ../../i386/i386/trap.c:403 #8 0xf01bd279 in Debugger (msg=0xf0117b98 "panic") at ../../i386/i386/db_interface.c:254 #9 0xf0117bfa in panic (fmt=0xf0101439 "from debugger") at ../../kern/kern_shutdown.c:365 #10 0xf0101455 in db_panic (dummy1=-266612096, dummy2=0, dummy3=-1, dummy4=0xefbffab0 "") at ../../ddb/db_command.c:440 ---Type to continue, or q to quit--- #11 0xf0101345 in db_command (last_cmdp=0xf01e3b24, cmd_table=0xf01e3974, aux_cmd_tablep=0xf01fce54) at ../../ddb/db_command.c:337 #12 0xf01014c2 in db_command_loop () at ../../ddb/db_command.c:462 #13 0xf0103ca8 in db_trap (type=10, code=0) at ../../ddb/db_trap.c:73 #14 0xf01bd07b in kdb_trap (type=10, code=0, regs=0xefbffba0) at ../../i386/i386/db_interface.c:126 #15 0xf01c5c34 in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = -251225900, tf_esi = -266736111, tf_ebp = -272630812, tf_isp = -272630840, tf_ebx = 256, tf_edx = -266612159, tf_ecx = -2147483648, tf_eax = 18, tf_trapno = 10, tf_err = 0, tf_eip = -266612096, tf_cs = 8, tf_eflags = 838, tf_esp = -266612175, tf_ss = -267289704}) at ../../i386/i386/trap.c:403 #16 0xf01bd280 in Debugger (msg=0xf0117b98 "panic") at ../../i386/i386/db_interface.c:255 #17 0xf0117bfa in panic (fmt=0xf019ee11 "blkfree: freeing free block") at ../../kern/kern_shutdown.c:365 #18 0xf019efe3 in ffs_blkfree (ip=0xf1230200, bno=21768, size=8192) at ../../ufs/ffs/ffs_alloc.c:1230 #19 0xf01a140a in ffs_indirtrunc (ip=0xf1230200, lbn=-12, dbn=11905184, lastbn=-1, level=0, countp=0xefbffd24) at ../../ufs/ffs/ffs_inode.c:500 #20 0xf01a0e48 in ffs_truncate (ap=0xefbffdfc) at ../../ufs/ffs/ffs_inode.c:317 #21 0xf01a4989 in ufs_inactive (ap=0xefbffe28) at vnode_if.h:1003 #22 0xf0136ecf in vrele (vp=0xf11d4200) at vnode_if.h:699 ---Type to continue, or q to quit--- #23 0xf01b7bb1 in vnode_pager_dealloc (object=0xf1598f80) at ../../vm/vnode_pager.c:203 #24 0xf01b70b6 in vm_pager_deallocate (object=0xf1598f80) at ../../vm/vm_pager.c:177 #25 0xf01b24f0 in vm_object_terminate (object=0xf1598f80) at ../../vm/vm_object.c:416 #26 0xf01b232b in vm_object_deallocate (object=0xf1598f80) at ../../vm/vm_object.c:353 #27 0xf0136e18 in vrele (vp=0xf11d4200) at ../../kern/vfs_subr.c:881 #28 0xf0136dc3 in vput (vp=0xf11d4200) at ../../kern/vfs_subr.c:858 #29 0xf01a7dbc in ufs_remove (ap=0xefbffef4) at ../../ufs/ufs/ufs_vnops.c:695 #30 0xf0139145 in unlink (p=0xf1714a00, uap=0xefbfff94, retval=0xefbfff84) at vnode_if.h:459 #31 0xf01c6677 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -272639652, tf_esi = -272639488, tf_ebp = -272639556, tf_isp = -272629788, tf_ebx = -272639413, tf_edx = 0, tf_ecx = -272639697, tf_eax = 10, tf_trapno = 12, tf_err = 7, tf_eip = 80117, tf_cs = 31, tf_eflags = 582, tf_esp = -272639676, tf_ss = 39}) at ../../i386/i386/trap.c:890 #32 0x138f5 in ?? () #33 0x123a in ?? () #34 0x107e in ?? ()