From owner-freebsd-fs Wed Aug 7 14:40:12 2002 Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CED3837B401 for ; Wed, 7 Aug 2002 14:40:08 -0700 (PDT) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABEA543E6E for ; Wed, 7 Aug 2002 14:40:07 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from monica.cs.rpi.edu (monica.cs.rpi.edu [128.213.7.3]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA51738; Wed, 7 Aug 2002 17:40:05 -0400 (EDT) Received: from monica.cs.rpi.edu (crossd@localhost) by monica.cs.rpi.edu (8.11.6/8.11.6) with ESMTP id g77Le5C78847; Wed, 7 Aug 2002 17:40:05 -0400 (EDT) (envelope-from crossd@monica.cs.rpi.edu) Message-Id: <200208072140.g77Le5C78847@monica.cs.rpi.edu> To: fs@freebsd.org Cc: guptar@cs.rpi.edu Subject: vnodes (UFS journaling)? Date: Wed, 07 Aug 2002 17:40:05 -0400 From: "David E. Cross" Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Ok, we've noticed an "unfortunate" side-effect of our work. We leak data (part of the journal shows up in other files). I think it is because of our handling of the vnode, and it being reused for other files (as oppsoed to trashing memory, etc. The entries it writes in the files are valid). We've tried _not_ calling vput(jvp) on it after the initial open but then any access to the file hangs the kernel (in inode). How can we say "don't reuse this" but allow other people to access it? -- David Cross | email: crossd@cs.rpi.edu Lab Director | Rm: 308 Lally Hall Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message