From owner-freebsd-fs Tue Sep 30 05:24:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA22450 for fs-outgoing; Tue, 30 Sep 1997 05:24:59 -0700 (PDT) Received: from ns.russianet.ru (russianet.ru [194.84.155.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA22441; Tue, 30 Sep 1997 05:24:51 -0700 (PDT) Received: (from sergey@localhost) by ns.russianet.ru (8.8.6/8.8.5) id QAA06887; Tue, 30 Sep 1997 16:24:48 +0400 (MSD) From: Sergey Vnotchenko Message-Id: <199709301224.QAA06887@ns.russianet.ru> Subject: Compressed filesystem To: freebsd-questions@FreeBSD.ORG Date: Tue, 30 Sep 1997 16:24:47 +0400 (MSD) Cc: freebsd-fs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello. I'm looking for read/write compressed filesystem for FreeBSD. Where can I get info about any? Thanks, Sergey. From owner-freebsd-fs Tue Sep 30 09:33:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA05360 for fs-outgoing; Tue, 30 Sep 1997 09:33:24 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA05354; Tue, 30 Sep 1997 09:33:18 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id JAA22976; Tue, 30 Sep 1997 09:33:04 -0700 (PDT) Date: Tue, 30 Sep 1997 09:33:03 -0700 (PDT) From: Doug White Reply-To: Doug White To: Sergey Vnotchenko cc: freebsd-questions@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: Compressed filesystem In-Reply-To: <199709301224.QAA06887@ns.russianet.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Sep 1997, Sergey Vnotchenko wrote: > I'm looking for read/write compressed filesystem for FreeBSD. > Where can I get info about any? I don't know if any exists at current, but try asking hackers@freebsd.org and/or fs@freebsd.org. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major From owner-freebsd-fs Tue Sep 30 21:50:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA16122 for fs-outgoing; Tue, 30 Sep 1997 21:50:56 -0700 (PDT) Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA16117; Tue, 30 Sep 1997 21:50:52 -0700 (PDT) Received: from guppy.cs.columbia.edu (guppy.cs.columbia.edu [128.59.16.155]) by cs.columbia.edu (8.8.5/8.6.6) with ESMTP id AAA07941; Wed, 1 Oct 1997 00:50:44 -0400 (EDT) Received: from guppy.cs.columbia.edu (sauce@localhost) by guppy.cs.columbia.edu (8.8.5/8.6.6) with ESMTP id AAA12529; Wed, 1 Oct 1997 00:50:44 -0400 (EDT) Message-Id: <199710010450.AAA12529@guppy.cs.columbia.edu> X-Mailer: exmh version 1.6.7 5/3/96 To: fs@freebsd.org cc: hackers@freebsd.org Subject: kernel modules Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Oct 1997 00:50:44 -0400 From: Alex Shender Sender: owner-freebsd-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I was wondering if any of you have written any filesytems as kernel modules. If so can you send me a pointer to the code. I am currently developing a filesystem for linux and Solaris and would like to port it to FreeBSD and would really appreciate it, if I could do it as a module. Thanks, Alex Shender From owner-freebsd-fs Tue Sep 30 23:00:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA19502 for fs-outgoing; Tue, 30 Sep 1997 23:00:31 -0700 (PDT) Received: from ccalpha01.center.osaka-u.ac.jp (ccalpha01.center.osaka-u.ac.jp [133.1.4.22]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA19495 for ; Tue, 30 Sep 1997 23:00:22 -0700 (PDT) Received: (from youki@localhost) by ccalpha01.center.osaka-u.ac.jp (8.7.5+2.6Wbeta6/3.4W4) id PAA30476; Wed, 1 Oct 1997 15:04:11 +0900 (JST) Date: Wed, 1 Oct 1997 15:04:11 +0900 (JST) From: Youki Kadobayashi Message-Id: <199710010604.PAA30476@ccalpha01.center.osaka-u.ac.jp> To: freebsd-fs@FreeBSD.ORG Subject: Re: Compressed filesystem Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have half- working version of compressed filesystem for BSD/OS. I said "half" because it doesn't support fstat(), O_APPEND, O_RDWR and fseek().. I think I can make a port to FreeBSD if VFS interface is the same. Youki Kadobayashi Osaka University From owner-freebsd-fs Wed Oct 1 16:49:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA17017 for fs-outgoing; Wed, 1 Oct 1997 16:49:59 -0700 (PDT) Received: from usr04.primenet.com (tlambert@usr04.primenet.com [206.165.6.204]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA16993; Wed, 1 Oct 1997 16:49:48 -0700 (PDT) Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id QAA22980; Wed, 1 Oct 1997 16:49:44 -0700 (MST) From: Terry Lambert Message-Id: <199710012349.QAA22980@usr04.primenet.com> Subject: Re: kernel modules To: sauce@cs.columbia.edu (Alex Shender) Date: Wed, 1 Oct 1997 23:49:44 +0000 (GMT) Cc: fs@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <199710010450.AAA12529@guppy.cs.columbia.edu> from "Alex Shender" at Oct 1, 97 00:50:44 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I was wondering if any of you have written any filesytems as kernel > modules. If so can you send me a pointer to the code. I am currently > developing a filesystem for linux and Solaris and would like to port it to > FreeBSD and would really appreciate it, if I could do it as a module. Look in the source tree. NFS and several other FS's can be loaded as modules. When I wrote the initial module code, I converted procfs as my example. The initialization code in the FS is a bit bogus: if you need to add new VOP_* calls, you will need to recompile the kernel anyway. This is because of the fact that the number of VOP entries is counted from the UFS_VNOPS table instead of the actual number of VOPS_* calls defined in vnode_if.c, and the vnode_if.c (a generated file) is not padded at all to allow growth. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-fs Wed Oct 1 21:06:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA29891 for fs-outgoing; Wed, 1 Oct 1997 21:06:25 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA29885 for ; Wed, 1 Oct 1997 21:06:21 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id EAA07386; Thu, 2 Oct 1997 04:05:06 GMT Date: Thu, 2 Oct 1997 13:05:06 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: Chris Csanady , brandon@roguetrader.com, wilko@yedi.iaf.nl, freebsd-fs@FreeBSD.ORG Subject: Re: Known problems with async ufs? In-Reply-To: <199709242308.QAA23263@usr03.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 24 Sep 1997, Terry Lambert wrote: > It will also mean that there are no hooks to guarantee transactions > are idempotent (multiple atomic transactions considered as an > all-or-nothing unit) for something like a user accessible transaction > tracking system. I think you're looking for another term. Idempotent transactions are like reads where you can repeat the transaction without ill-effects. Non-idempotent transactions modify the state of the system such that they can't be repeated, say rmdir foo. Multiple atomic transactions that are atomic can be restated as an atomic transaction. Regards, Mike From owner-freebsd-fs Thu Oct 2 01:16:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA12007 for fs-outgoing; Thu, 2 Oct 1997 01:16:22 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA12002 for ; Thu, 2 Oct 1997 01:16:20 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id BAA24245; Thu, 2 Oct 1997 01:15:59 -0700 (MST) From: Terry Lambert Message-Id: <199710020815.BAA24245@usr08.primenet.com> Subject: Re: Known problems with async ufs? To: michaelh@cet.co.jp (Michael Hancock) Date: Thu, 2 Oct 1997 08:15:58 +0000 (GMT) Cc: tlambert@primenet.com, ccsanady@bob.scl.ameslab.gov, brandon@roguetrader.com, wilko@yedi.iaf.nl, freebsd-fs@FreeBSD.ORG In-Reply-To: from "Michael Hancock" at Oct 2, 97 01:05:06 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > It will also mean that there are no hooks to guarantee transactions > > are idempotent (multiple atomic transactions considered as an > > all-or-nothing unit) for something like a user accessible transaction > > tracking system. > > I think you're looking for another term. Idempotent transactions are like > reads where you can repeat the transaction without ill-effects. > Non-idempotent transactions modify the state of the system such that they > can't be repeated, say rmdir foo. > > Multiple atomic transactions that are atomic can be restated as an atomic > transaction. Reads advance the file pointer, unless they are mread. Same for write vs. mwrite. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-fs Thu Oct 2 21:29:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA15498 for fs-outgoing; Thu, 2 Oct 1997 21:29:31 -0700 (PDT) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA15492 for ; Thu, 2 Oct 1997 21:29:25 -0700 (PDT) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.5/CET-v2.1) with SMTP id EAA04260; Fri, 3 Oct 1997 04:28:27 GMT Date: Fri, 3 Oct 1997 13:28:27 +0900 (JST) From: Michael Hancock To: Terry Lambert cc: ccsanady@bob.scl.ameslab.gov, brandon@roguetrader.com, wilko@yedi.iaf.nl, freebsd-fs@FreeBSD.ORG Subject: Re: Known problems with async ufs? In-Reply-To: <199710020815.BAA24245@usr08.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Oct 1997, Terry Lambert wrote: > > > It will also mean that there are no hooks to guarantee transactions > > > are idempotent (multiple atomic transactions considered as an > > > all-or-nothing unit) for something like a user accessible transaction > > > tracking system. > > > > I think you're looking for another term. Idempotent transactions are like > > reads where you can repeat the transaction without ill-effects. > > Non-idempotent transactions modify the state of the system such that they > > can't be repeated, say rmdir foo. > > > > Multiple atomic transactions that are atomic can be restated as an atomic > > transaction. > > Reads advance the file pointer, unless they are mread. Same for write vs. > mwrite. Maybe getattr would have been a better example. Though I've seen references where they separate VOP operations into idempotent and non-idempotent operations. It's probably more important in the context of NFS servers where things are stateless. A read here is packaged with file positioning so repeated receives of the same request doesn't hurt anything. Regards, Mike From owner-freebsd-fs Fri Oct 3 23:38:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA01241 for fs-outgoing; Fri, 3 Oct 1997 23:38:22 -0700 (PDT) Received: from usr08.primenet.com (tlambert@usr08.primenet.com [206.165.6.208]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA01236 for ; Fri, 3 Oct 1997 23:38:12 -0700 (PDT) Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id XAA08655; Fri, 3 Oct 1997 23:37:53 -0700 (MST) From: Terry Lambert Message-Id: <199710040637.XAA08655@usr08.primenet.com> Subject: Re: Known problems with async ufs? To: michaelh@cet.co.jp (Michael Hancock) Date: Sat, 4 Oct 1997 06:37:53 +0000 (GMT) Cc: tlambert@primenet.com, ccsanady@bob.scl.ameslab.gov, brandon@roguetrader.com, wilko@yedi.iaf.nl, freebsd-fs@FreeBSD.ORG In-Reply-To: from "Michael Hancock" at Oct 3, 97 01:28:27 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Reads advance the file pointer, unless they are mread. Same for write vs. > > mwrite. [ ... ] > It's probably more important in the context of NFS servers where > things are stateless. A read here is packaged with file > positioning so repeated receives of the same request doesn't hurt > anything. amread takes a file offset; it's there (in other OS's) to support kernel preeemptive threading. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.