From owner-freebsd-fs Thu Apr 16 22:00:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18082 for freebsd-fs-outgoing; Thu, 16 Apr 1998 22:00:17 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18058; Fri, 17 Apr 1998 05:00:04 GMT (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id EAA17376; Fri, 17 Apr 1998 04:59:15 GMT Date: Fri, 17 Apr 1998 13:59:14 +0900 (JST) From: Michael Hancock To: freebsd-current@FreeBSD.ORG cc: freebsd-fs@FreeBSD.ORG Subject: Updated vfs patches Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've separated the layering fixes and the VFS_VRELE framework into separate projects. Here is an updated patch for making *both* refcounting and locking of vnodes reflexive using the current framework. http://www.freebsd.org/~mch/vop1a.diff For a testing tool see http://www.freebsd.org/~mch Some things I should note in this patch are listed below: 1) In the original code, ext2_rmdir and msdosfs_rmdir release the lock across the truncate call but ufs_rmdir doesn't. The ufs_rmdir implementation make it clean for me because I just delete the vput(), but in ext2_rmdir and msdosfs_rmdir I must reacquire the lock so the generic layer can do the vput() (phew!). I'm not sure if we should be holding a lock across truncate and I have yet to review the logs yet to see why. Perhaps someone can shed some light on this. 2) In the union filesystem, there are a also a few case where I have to reacquire the lock. However, it appears that there is an invariant that says if the upper vnode is held by me I can "diddle with the union vnode locking state at will", see UN_KLOCK and UN_ULOCK. I take advantage of this and reacquire the lock by just twiddling a bit instead of calling vn_lock(). Otherwise, this patch consists of mostly deleting vrele and vput calls in underlying filesystems and moving them to the generic layer. Regards, Mike Hancock To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Apr 16 22:24:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22174 for freebsd-fs-outgoing; Thu, 16 Apr 1998 22:24:37 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22156; Fri, 17 Apr 1998 05:24:28 GMT (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id FAA17520; Fri, 17 Apr 1998 05:23:40 GMT Date: Fri, 17 Apr 1998 14:23:40 +0900 (JST) From: Michael Hancock To: freebsd-current@FreeBSD.ORG cc: freebsd-fs@FreeBSD.ORG Subject: Re: Updated vfs patches In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 17 Apr 1998, Michael Hancock wrote: > http://www.freebsd.org/~mch/vop1a.diff > > 1) In the original code, ext2_rmdir and msdosfs_rmdir release the lock > across the truncate call but ufs_rmdir doesn't. The ufs_rmdir > implementation make it clean for me because I just delete the vput(), but > in ext2_rmdir and msdosfs_rmdir I must reacquire the lock so the generic > layer can do the vput() (phew!). I'm not sure if we should be holding a > lock across truncate and I have yet to review the logs yet to see why. > Perhaps someone can shed some light on this. I found it (POST_SOFTUPDATES)! Do we not block when calling truncate with softupdates on? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Apr 16 23:11:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05391 for freebsd-fs-outgoing; Thu, 16 Apr 1998 23:11:26 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05356; Fri, 17 Apr 1998 06:11:22 GMT (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id WAA28231; Thu, 16 Apr 1998 22:59:08 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd028229; Fri Apr 17 05:59:07 1998 Message-ID: <3536EE71.41C67EA6@whistle.com> Date: Thu, 16 Apr 1998 22:53:53 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Michael Hancock CC: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: Updated vfs patches References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michael Hancock wrote: > > On Fri, 17 Apr 1998, Michael Hancock wrote: > > > http://www.freebsd.org/~mch/vop1a.diff > > > > 1) In the original code, ext2_rmdir and msdosfs_rmdir release the lock > > across the truncate call but ufs_rmdir doesn't. The ufs_rmdir > > implementation make it clean for me because I just delete the vput(), but > > in ext2_rmdir and msdosfs_rmdir I must reacquire the lock so the generic > > layer can do the vput() (phew!). I'm not sure if we should be holding a > > lock across truncate and I have yet to review the logs yet to see why. > > Perhaps someone can shed some light on this. > > I found it (POST_SOFTUPDATES)! Do we not block when calling truncate with > softupdates on? > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message now THAT is a good question...... I basically took the code from kirk's changes and he seemed (from my memory.. I don't have the changes here) to have made that change, so I did too. I'd have to ask kirk WHY he did that and he's out of town for 1 more week. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Apr 16 23:35:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10138 for freebsd-fs-outgoing; Thu, 16 Apr 1998 23:35:36 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA10110; Fri, 17 Apr 1998 06:35:27 GMT (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.8/CET-v2.2) with SMTP id GAA17997; Fri, 17 Apr 1998 06:34:15 GMT Date: Fri, 17 Apr 1998 15:34:15 +0900 (JST) From: Michael Hancock To: Julian Elischer cc: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: Updated vfs patches In-Reply-To: <3536EE71.41C67EA6@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 16 Apr 1998, Julian Elischer wrote: > > I found it (POST_SOFTUPDATES)! Do we not block when calling truncate with > > softupdates on? > > now THAT is a good question...... > I basically took the code from kirk's changes and he seemed > (from my memory.. I don't have the changes here) to have made > that change, so I did too. I'd have to ask kirk WHY he did that > and he's out of town for 1 more week. The changes look intentional because it was like this before... vput(dvp) dvp = NULL truncate out: if (dvp) vput(dvp) return Now it looks like this ... truncate out: vput(dvp) return You had to make a couple of changes to do this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Apr 17 06:18:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18367 for freebsd-fs-outgoing; Fri, 17 Apr 1998 06:18:20 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from kaori.communique.net (kaori.communique.net [204.27.67.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18361 for ; Fri, 17 Apr 1998 13:18:19 GMT (envelope-from rzig@verio.net) Received: by kaori.communique.net with Internet Mail Service (5.0.1458.49) id ; Fri, 17 Apr 1998 08:17:03 -0500 Message-ID: From: Raul Zighelboim To: "'fs@freefall.freebsd.org'" Cc: "'n@nectar.com'" Subject: mirroring the system fs Date: Fri, 17 Apr 1998 08:17:01 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello there; I must install FreeBSD on a raid 0 system, based on ccd. my fstab is: # Device Mountpoint FStype Options Dump Pass# /dev/sd0s1b none swap sw 0 0 /dev/sd2s1b none swap sw 0 0 /dev/ccd0c / ufs rw 1 1 proc /proc procfs rw 0 0 and ccd.conf is: ccd0 16 6 sd0s1e sd2s1e but I cannot load the kernel until ccd0c has been defined, and I cannot defined it without the kernel! Is there a bootstrap that understand ccd ? FreeBSD floppy that loads the kernel but then goes on into the hard disks ? If I was to boot from bootp or a floppy, would I be able to revert control to the local drives ? thanks. ================================================== Raul Zighelboim rzig@verio.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Fri Apr 17 10:58:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12600 for freebsd-fs-outgoing; Fri, 17 Apr 1998 10:58:34 -0700 (PDT) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12587 for ; Fri, 17 Apr 1998 17:58:31 GMT (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id NAA06557; Fri, 17 Apr 1998 13:58:30 -0400 (EDT) Date: Fri, 17 Apr 1998 13:58:29 -0400 (EDT) From: "Matthew N. Dodd" To: Raul Zighelboim cc: "'fs@freefall.freebsd.org'" , "'n@nectar.com'" Subject: Re: mirroring the system fs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 17 Apr 1998, Raul Zighelboim wrote: > and ccd.conf is: > ccd0 16 6 sd0s1e sd2s1e > > but I cannot load the kernel until ccd0c has been defined, and I cannot > defined it without the kernel! You can't boot from a CCD. I wonder how trival it would be to store a copy of the ccd matadata on the first sector of each disk and let the kernel ccdconfig the volumes instead of the userland... -rw-r--r-- 1 root bin - 8775 Apr 10 14:16 ccdconfig.o Not all that much code really... /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message