From owner-freebsd-fs Sun Sep 14 00:38:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA28416 for fs-outgoing; Sun, 14 Sep 1997 00:38:49 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA28411 for ; Sun, 14 Sep 1997 00:38:46 -0700 (PDT) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id JAA01330; Sun, 14 Sep 1997 09:38:02 +0200 (CEST) To: Terry Lambert cc: fs@FreeBSD.ORG Subject: Re: getcwd() as syscall... In-reply-to: Your message of "Sat, 13 Sep 1997 22:01:50 -0000." <199709132201.PAA29443@usr03.primenet.com> Date: Sun, 14 Sep 1997 09:38:00 +0200 Message-ID: <1328.874222680@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Terry, read up on the code before you speak. It's always a good idea There is one point where you by accident is not entirely wrong, but it is obvious from the rest that you don't know why that statement is somewhat true. I will leave it to you to figure out which one. I will only address the two most wrong points here: >Other than that, it's a *great* idea, and the purpose behind >the parent pointers in the first place. 8-) 8-). No it wasn't. [*] >Oh... is there an option to fsck to set these on a legacy FS? They are not stored on disk. Poul-Henning [*] And before you launch into a long tirade on this point, please look in the CVS files and see who added them. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-fs Sun Sep 14 03:01:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA03505 for fs-outgoing; Sun, 14 Sep 1997 03:01:09 -0700 (PDT) Received: from usr06.primenet.com (tlambert@usr06.primenet.com [206.165.6.206]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA03499 for ; Sun, 14 Sep 1997 03:01:07 -0700 (PDT) Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id DAA14437; Sun, 14 Sep 1997 03:00:41 -0700 (MST) From: Terry Lambert Message-Id: <199709141000.DAA14437@usr06.primenet.com> Subject: Re: getcwd() as syscall... To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Sun, 14 Sep 1997 10:00:41 +0000 (GMT) Cc: tlambert@primenet.com, fs@FreeBSD.ORG In-Reply-To: <1328.874222680@critter.freebsd.dk> from "Poul-Henning Kamp" at Sep 14, 97 09:38:00 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Terry, read up on the code before you speak. > > It's always a good idea > > There is one point where you by accident is not entirely wrong, but > it is obvious from the rest that you don't know why that statement > is somewhat true. I will leave it to you to figure out which one. > > I will only address the two most wrong points here: > > >Other than that, it's a *great* idea, and the purpose behind > >the parent pointers in the first place. 8-) 8-). > > No it wasn't. [*] > > >Oh... is there an option to fsck to set these on a legacy FS? > > They are not stored on disk. Sorry. I thought that this had been done on my suggestion, per modification made to UFS for the NXFS code. If you will remember, I was the one who originally pointed out that POSIX did not require directories to be files, and therefore, it was OK to not allow hard links on directories. If you have a hard link on a directory, there's no reason *not* to store this data on disk. After all, there are ree fields which can be used for this purpose. If this is not currently the case, then it *should* be. Personally, I'd change the mechanism whereby hard links are stored\ on disk to ensure that files had parent pointers as well. 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 Sun Sep 14 03:23:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA04293 for fs-outgoing; Sun, 14 Sep 1997 03:23:38 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA04280 for ; Sun, 14 Sep 1997 03:23:32 -0700 (PDT) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id MAA01572; Sun, 14 Sep 1997 12:22:44 +0200 (CEST) To: Terry Lambert cc: fs@freebsd.org Subject: Re: getcwd() as syscall... In-reply-to: Your message of "Sun, 14 Sep 1997 10:00:41 -0000." <199709141000.DAA14437@usr06.primenet.com> Date: Sun, 14 Sep 1997 12:22:44 +0200 Message-ID: <1570.874232564@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199709141000.DAA14437@usr06.primenet.com>, Terry Lambert writes: >If this is not currently the case, then it *should* be. > >Personally, I'd change the mechanism whereby hard links are stored\ >on disk to ensure that files had parent pointers as well. send patches. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-fs Sun Sep 14 10:00:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA18025 for fs-outgoing; Sun, 14 Sep 1997 10:00:32 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA18014 for ; Sun, 14 Sep 1997 10:00:30 -0700 (PDT) Received: from shane.plutotech.com (shane.plutotech.com [206.168.67.149]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id LAA22091 for ; Sun, 14 Sep 1997 11:00:29 -0600 (MDT) Message-Id: <199709141700.LAA22091@pluto.plutotech.com> From: "Mike Durian" To: fs@freebsd.org Subject: Initial VFS/NFS question repost to fs list Date: Sun, 14 Sep 1997 11:00:29 -0600 Sender: owner-freebsd-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Mr. Kamp suggested that readers of the fs list might not have seen my original question that I sent to the hackers list. Here it is: I've got a VFS problem I'm hoping someone out there can give me some ideas on. I've written a VFS based filesystem that is an interface to our RAID system. The RAID system stores video frames and the filesystem allows access to the data and automatically translates the data to a variety of file formats (TIFF, Targa, YUV, etc.). The frame number and conversion type are defined by the path name. Eg /pfs/frames/tiff/0.tiff or /pfs/HMSF/tga/hour00/minute01/second10//00.01.10.29.tga. The filesystem is implemented partially in the kernel and partially as a user application. The two parts communicate via a socket. The filesystem works well for normal accesses, but I'm having a strange problem with NFS. I've supplied the fhtovp and vptofh hooks and things basically work, but I can get the client side wedged under heavy accesses. If I run four simultaneous processes copying data to my filesystem, after a while I'll see one of the nfsiod go to sleep on "vfsfsy" and not return. Eventually, the other nfsiods will go to sleep on "nfsrcv" and that's that. In both cases, it looks like the clients aren't getting a acks from the server. Strangely, none of the nfsd processes on the server are sleeping and the user mount_pfs process isn't sleeping either. In fact the filesystem is still perfectly usable. It's just the NFS client that is wedged. I'm not sure where the problem lies. Is it an NFS issue or a (more likely) bug in my filesystem? Does anybody have any ideas on why an NFS server might drop an ACK and wedge the client? I did get the same results with both NFSv3 and NFSv2. TCP failed too, though lasted longer with a number of "server not responing"/"server responding again" messages. The messages would appear back to back without the server really going down. Thanks, mike From owner-freebsd-fs Wed Sep 17 06:32:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA10914 for fs-outgoing; Wed, 17 Sep 1997 06:32:57 -0700 (PDT) Received: from gate.mgt.msk.ru (mgtrep.24h.dialup.ru [194.87.18.139]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA10908 for ; Wed, 17 Sep 1997 06:32:50 -0700 (PDT) Received: from asteroid.mgt.msk.ru (asteroid.mgt.msk.ru [192.168.133.145]) by gate.mgt.msk.ru (8.8.6/8.8.6) with ESMTP id RAA10925 for ; Wed, 17 Sep 1997 17:32:30 +0400 (MSD) Received: from asteroid.mgt.msk.ru (localhost.mgt.msk.ru [127.0.0.1]) by asteroid.mgt.msk.ru (8.8.6/8.8.6) with ESMTP id RAA01861 for ; Wed, 17 Sep 1997 17:31:43 +0400 (MSD) Message-Id: <199709171331.RAA01861@asteroid.mgt.msk.ru> To: fs@freebsd.org Reply-To: tarkhil@mgt.msk.ru Subject: LFS status Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Sep 1997 17:31:41 +0400 From: "Alexander B. Povolotsky" Sender: owner-freebsd-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! What is current LFS status? Or maybe someone has ported advfs? Alex. From owner-freebsd-fs Wed Sep 17 11:50:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA01752 for fs-outgoing; Wed, 17 Sep 1997 11:50:35 -0700 (PDT) Received: from usr02.primenet.com (tlambert@usr02.primenet.com [206.165.6.202]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA01745 for ; Wed, 17 Sep 1997 11:50:25 -0700 (PDT) Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id LAA02219; Wed, 17 Sep 1997 11:49:52 -0700 (MST) From: Terry Lambert Message-Id: <199709171849.LAA02219@usr02.primenet.com> Subject: Re: LFS status To: tarkhil@mgt.msk.ru Date: Wed, 17 Sep 1997 18:49:50 +0000 (GMT) Cc: fs@FreeBSD.ORG In-Reply-To: <199709171331.RAA01861@asteroid.mgt.msk.ru> from "Alexander B. Povolotsky" at Sep 17, 97 05:31:41 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-fs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hello! > > What is current LFS status? It's a Master's project by Margo Seltzer. John Dyson was working on making the 4.4-Lite2 version run in FreeBSD. > Or maybe someone has ported advfs? I saw the announcement of advfs, but I don't think a port had been done. it's possible, i suppose. 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 Sep 17 12:18:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA03525 for fs-outgoing; Wed, 17 Sep 1997 12:18:30 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA03510 for ; Wed, 17 Sep 1997 12:18:23 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA20059 (5.67b/IDA-1.5 for fs@FreeBSD.ORG); Wed, 17 Sep 1997 21:18:17 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id UAA02087; Wed, 17 Sep 1997 20:49:31 +0200 (MET DST) From: Wilko Bulte Message-Id: <199709171849.UAA02087@yedi.iaf.nl> Subject: Re: LFS status To: tarkhil@mgt.msk.ru Date: Wed, 17 Sep 1997 20:49:31 +0200 (MET DST) Cc: fs@FreeBSD.ORG In-Reply-To: <199709171331.RAA01861@asteroid.mgt.msk.ru> from "Alexander B. Povolotsky" at Sep 17, 97 05:31:41 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] 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 As Alexander B. Povolotsky wrote... > Hello! > > What is current LFS status? Or maybe someone has ported advfs? What makes you think Digital would publish the AdvFS sources for free download? I assume you mean that FS... 'This must be a joke' Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ----------------------------------------------------------------------Yoda