From owner-freebsd-fs Sun Aug 29 1:12:20 1999 Delivered-To: freebsd-fs@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 4677015041; Sun, 29 Aug 1999 01:12:14 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id KAA15754; Sun, 29 Aug 1999 10:09:03 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Alfred Perlstein Cc: Erez Zadok , Matthew Dillon , hackers@FreeBSD.ORG, fs@FreeBSD.ORG, Michael Hancock , David Greenman Subject: Re: HEADS UP Reviewers. VFS changes to be committed. In-reply-to: Your message of "Sat, 28 Aug 1999 20:25:34 -0000." Date: Sun, 29 Aug 1999 10:09:03 +0200 Message-ID: <15752.935914143@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , Alfred P erlstein writes: > > >On Fri, 27 Aug 1999, Poul-Henning Kamp wrote: > >> >> Uhm, have any of you actually ever looked at src/sys/kern/vnode_if.src ? > >I can't really tell if you are commenting on the diffs I provided or >if you are commmenting on the comments I have recieved, or both. Mostly the comments actually I'm overloaded at the moment, so I have not been able to find time to sit down and thing through this one, sorry... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Sun Aug 29 1:23:31 1999 Delivered-To: freebsd-fs@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 125EE1502B for ; Sun, 29 Aug 1999 01:23:27 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id KAA24353; Sun, 29 Aug 1999 10:21:53 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.0/8.9.0) with ESMTP id KAA02648; Sun, 29 Aug 1999 10:21:49 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id KAA28792; Sun, 29 Aug 1999 10:21:38 +0200 (CEST) (envelope-from ticso) Date: Sun, 29 Aug 1999 10:21:38 +0200 From: Bernd Walter To: Terry Lambert Cc: Bernd Walter , freebsd-fs@FreeBSD.ORG Subject: Re: fs-locking and fs memory copies questions Message-ID: <19990829102137.A28745@cicely8.cicely.de> References: <19990828201723.A27704@cicely8.cicely.de> <199908282249.PAA06168@usr01.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199908282249.PAA06168@usr01.primenet.com>; from Terry Lambert on Sat, Aug 28, 1999 at 10:49:51PM +0000 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Aug 28, 1999 at 10:49:51PM +0000, Terry Lambert wrote: > > The code you need to modify is in ffs_mount in ffs_vfops.c. > A good hint - thanks! I'm worried about mnt_flag: Are 0x08000000 and 0x00800000 realy the only bits left? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Aug 30 7:26:46 1999 Delivered-To: freebsd-fs@freebsd.org Received: from hotmail.com (f273.hotmail.com [207.82.251.164]) by hub.freebsd.org (Postfix) with SMTP id 692761533C for ; Mon, 30 Aug 1999 07:26:43 -0700 (PDT) (envelope-from gupz@hotmail.com) Received: (qmail 4862 invoked by uid 0); 30 Aug 1999 14:24:25 -0000 Message-ID: <19990830142425.4861.qmail@hotmail.com> Received: from 161.44.52.23 by www.hotmail.com with HTTP; Mon, 30 Aug 1999 07:24:25 PDT X-Originating-IP: [161.44.52.23] From: "Dodge Ram" To: freebsd-fs@freebsd.org Subject: Sharing file descriptors Date: Mon, 30 Aug 1999 07:24:25 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Have a question on whether it is possible to share file descriptors between two processes. The purpose is to have a stanby process take over when the primary process fails. The primary process creates/deletes socket connections at run time. Forking does not scale well when the rate of connection creates/deletes in high. If there is an alternative approach to do this kindly let me know. Any helpful pointers are greatly appreciated. thanks and regards, ramesh ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Aug 30 10:11:43 1999 Delivered-To: freebsd-fs@freebsd.org Received: from mail-relay2.yahoo.com (mail-relay2.yahoo.com [206.251.17.77]) by hub.freebsd.org (Postfix) with ESMTP id 9BB0C15857 for ; Mon, 30 Aug 1999 10:11:38 -0700 (PDT) (envelope-from jh@yahoo-inc.com) Received: from borogove.yahoo.com (borogove.yahoo.com [205.216.162.65]) by mail-relay2.yahoo.com (8.9.3/8.9.3) with ESMTP id JAA07235; Mon, 30 Aug 1999 09:33:07 -0700 (PDT) Received: from localhost.yahoo.com (localhost.yahoo.com [127.0.0.1]) by borogove.yahoo.com (8.9.3/8.9.3) with SMTP id JAA08879; Mon, 30 Aug 1999 09:33:06 -0700 (PDT) Message-Id: <199908301633.JAA08879@borogove.yahoo.com> X-Authentication-Warning: borogove.yahoo.com: localhost.yahoo.com [127.0.0.1] didn't use HELO protocol To: "Dodge Ram" Cc: freebsd-fs@FreeBSD.ORG Subject: Re: Sharing file descriptors In-reply-to: Your message of "Mon, 30 Aug 1999 07:24:25 PDT." <19990830142425.4861.qmail@hotmail.com> Date: Mon, 30 Aug 1999 09:33:06 -0700 From: John Hanley Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > take over when the primary process fails Presumably the failure relates to big bulky app logic occasionally coring. Rearchitect so a tiny simple process holds the open file descriptor(s) and communicates through shared mem with your app. See also http://www.socks.nec.com/how2socksify.html http://www.fastcgi.com/ Cheers, JH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Aug 30 20:32:57 1999 Delivered-To: freebsd-fs@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 3716914E9E for ; Mon, 30 Aug 1999 20:32:08 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id UAA00235; Mon, 30 Aug 1999 20:31:28 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpdAAA7DaOwa; Mon Aug 30 20:31:21 1999 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id UAA13295; Mon, 30 Aug 1999 20:31:35 -0700 (MST) From: Terry Lambert Message-Id: <199908310331.UAA13295@usr04.primenet.com> Subject: Re: fs-locking and fs memory copies questions To: ticso@cicely.de (Bernd Walter) Date: Tue, 31 Aug 1999 03:31:35 +0000 (GMT) Cc: tlambert@primenet.com, ticso@cicely.de, freebsd-fs@FreeBSD.ORG In-Reply-To: <19990829013655.E27811@cicely8.cicely.de> from "Bernd Walter" at Aug 29, 99 01:36:56 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > This is the problem with growing FS's: the hash fill on the > > preexisting cylinger groups will be higher than on the new > > cylinder groups, leading to fragmentation. > > Mmmmm - I can't follow you on this. > The existing cg's are prefilled with old files. > The new ones are empty after growing. > I beleaved ffs would prever the new ones automaticaly because of > the super-blocks summary information. I don't think so. You'd want it to, but it probably won't. The problem that happens if it, in fact, does, is that you'd end up with data for new files clustering in one area of the disk, which is exactly the situation you wanted badly enough to avoid that you picked a hash-like algorithm (think of FFS as hashing to pick the blocks it's allocating) in the first place. This is why I said "Bad:" when referring to doing this on purpose, and not knowing when to stop. Create a couple of large files, and your allocation policy gets see-saw like. 8-(. > > A generic defragger would be a good think to have, if you wanted > > to allow shrinking partitions, too. > > I already need to move blocks around in case the superblock-summary > information needs another frag. > It was one of the more difficult things to do there are still some > erros left about this - the rest was quite easy. > Shrinking is something I don't beleave to get working properly, because > that would mean loosing cg's with all their inodes. > Moving files to different inodes is generaly a mess for NFS-servers. > Another point is that finding the reference for a frag is a real > expensive thing to do :( I agree on the frag, but if you are doing it in the background, you might not really care about the expense. The NFS inode problem can be resolved by virtualizing the inode numbers in the handled, but it's rather a pain to keep a table around for that. Like see-saw allocations, it hard to know when to stop doing it, once you start. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Mon Aug 30 23:46:13 1999 Delivered-To: freebsd-fs@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id D57F415867 for ; Mon, 30 Aug 1999 23:46:07 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id IAA21216; Tue, 31 Aug 1999 08:45:19 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.0/8.9.0) with ESMTP id IAA14813; Tue, 31 Aug 1999 08:46:00 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id IAA32065; Tue, 31 Aug 1999 08:45:45 +0200 (CEST) (envelope-from ticso) Date: Tue, 31 Aug 1999 08:45:45 +0200 From: Bernd Walter To: Terry Lambert Cc: Bernd Walter , freebsd-fs@FreeBSD.ORG Subject: Re: fs-locking and fs memory copies questions Message-ID: <19990831084545.A32008@cicely8.cicely.de> References: <19990829013655.E27811@cicely8.cicely.de> <199908310331.UAA13295@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199908310331.UAA13295@usr04.primenet.com>; from Terry Lambert on Tue, Aug 31, 1999 at 03:31:35AM +0000 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Aug 31, 1999 at 03:31:35AM +0000, Terry Lambert wrote: > > I beleaved ffs would prever the new ones automaticaly because of > > the super-blocks summary information. > > I don't think so. You'd want it to, but it probably won't. > > The problem that happens if it, in fact, does, is that you'd end up > with data for new files clustering in one area of the disk, which > is exactly the situation you wanted badly enough to avoid that you > picked a hash-like algorithm (think of FFS as hashing to pick > the blocks it's allocating) in the first place. > > This is why I said "Bad:" when referring to doing this on purpose, > and not knowing when to stop. Create a couple of large files, and > your allocation policy gets see-saw like. 8-(. > OK - my programm is nearly complete for working offline so I will bring it to end. Then I will do some tests how blocks get filled up after that. It's only a performance issue, so I'm shure I will be happy with it anyway. > > > > A generic defragger would be a good think to have, if you wanted > > > to allow shrinking partitions, too. > > > > I already need to move blocks around in case the superblock-summary > > information needs another frag. > > It was one of the more difficult things to do there are still some > > erros left about this - the rest was quite easy. > > Shrinking is something I don't beleave to get working properly, because > > that would mean loosing cg's with all their inodes. > > Moving files to different inodes is generaly a mess for NFS-servers. > > Another point is that finding the reference for a frag is a real > > expensive thing to do :( > > I agree on the frag, but if you are doing it in the background, you > might not really care about the expense. Doing it in the background might be a good solution when doing it online. At this moment I begin with increasing the strucktures - then writing the CGs including the expanded after that I reallocate some frags if needed and finaly rewrite the superblocks. It looks like the order is not the best one - I will need to rearange it. > > The NFS inode problem can be resolved by virtualizing the inode > numbers in the handled, but it's rather a pain to keep a table > around for that. Like see-saw allocations, it hard to know when > to stop doing it, once you start. 8-(. Yes and you may want to make it persistence that a reboot won't mess things up. Is NFS the only critical case? If yes it would be possible to check if it's exported and take special care in single-user mode and if exported One thing is clear - if we can't decrease the fs and the user needs to he will ending up with backup-repartition-restore and running into exactly the same troubles. A simple warning to remount all clients should be the best way and maybe optionally such a translation table. At this moment I'm thinking more about features like automaticaly increasing. Say you have n-partitions and don't want to have them to get overfilled. You would define a spare-pool and if one partition gets filled over a defined limit a disk from the sparepool will be taken and added automatically. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Sep 2 7:17:37 1999 Delivered-To: freebsd-fs@freebsd.org Received: from pop111.ocn.ne.jp (pop111.ocn.ne.jp [202.234.233.71]) by hub.freebsd.org (Postfix) with ESMTP id 9302C15B29 for ; Thu, 2 Sep 1999 07:17:31 -0700 (PDT) (envelope-from academy@academyjapan.co.jp) Received: from pop111.ocn.ne.jp by pop111.ocn.ne.jp (8.9.1a/OCN) id XAA11474; Thu, 2 Sep 1999 23:15:40 +0900 (JST) Date: Thu, 2 Sep 1999 23:15:40 +0900 (JST) Message-Id: <199909021415.XAA11474@pop111.ocn.ne.jp> From: =?ISO-2022-JP?B?QWNhZGVteSBKYXBhbn==?= To: =?ISO-2022-JP?B?ZnJlZWJzZC1mc0BGcmVlQlNELm9yZ2==?= X-Mailer: Direct Email v0.22 Subject: =?ISO-2022-JP?B?GyRCJUYlbCVTRUVPQyROJCpDTiRpJDshIRsoQkluZm8gb24gVmlkZW9waG9uZW==?= Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org こんにちわ、 これは便利！ Here's a good news for you, ホテル、旅館、単身赴任、留学にも a news of the Videophone 最適なニュース! over the normal coloer telephone line. 今、世界で話題の簡単テレビ電話 All you have to do is just の紹介です。 connect this videophone with 自宅のテレビと電話につなぐだけで the telephone and television. ＴＶ電話に早変わり！（工事不要） which you have in your home. 電話代は、今までと同じです。 Telephone charge is the same as ever. 遠くの友人や家族と、顔を見ながら Face to face communication with distant 話せるので一安心！！ your distant family 値段は一台で69,000円です。 Price per unit: 6,9000 yen 下をクリックしてみて下さい。 Please click left below. http://www.academyjapan.co.jp academy@academyjpan.co.jp アカデミー・ジャパン　担当：山本 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message From owner-freebsd-fs Thu Sep 2 14:45:52 1999 Delivered-To: freebsd-fs@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id 9154215B89 for ; Thu, 2 Sep 1999 14:45:45 -0700 (PDT) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.1/8.9.1) id OAA145746; Thu, 2 Sep 1999 14:45:25 -0700 Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp05.primenet.com, id smtpd8vKBya; Thu Sep 2 14:45:18 1999 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id OAA21686; Thu, 2 Sep 1999 14:45:12 -0700 (MST) From: Terry Lambert Message-Id: <199909022145.OAA21686@usr01.primenet.com> Subject: Re: fs-locking and fs memory copies questions To: ticso@cicely.de (Bernd Walter) Date: Thu, 2 Sep 1999 21:45:12 +0000 (GMT) Cc: tlambert@primenet.com, ticso@cicely.de, freebsd-fs@FreeBSD.ORG In-Reply-To: <19990829102137.A28745@cicely8.cicely.de> from "Bernd Walter" at Aug 29, 99 10:21:38 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Sat, Aug 28, 1999 at 10:49:51PM +0000, Terry Lambert wrote: > > > The code you need to modify is in ffs_mount in ffs_vfops.c. > > > A good hint - thanks! > I'm worried about mnt_flag: > Are 0x08000000 and 0x00800000 realy the only bits left? There are two sets of mount flags. One is for use by the kernel, one for use by user space to communicate with the kernel. If you can, use an internal flag, unless you are trying to send a flag down from mount. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message