From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] fs (config) questions From: forsyth@caldo.demon.co.uk MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-tyrzjwrrhulswfsspfsjfdlfwl" Message-Id: <20010413085004.E15FE19A2E@mail.cse.psu.edu> Date: Fri, 13 Apr 2001 09:47:26 +0100 Topicbox-Message-UUID: 81cc2858-eac9-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-tyrzjwrrhulswfsspfsjfdlfwl Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit >>Another, maybe a bit naive, question: the worm-like nature of the >>pseudo worm will cause it to fill up eventually. >>Would it be possible to plug in another disk and configure that >>as part of an existing pseudo-worm, like if you would be adding >>a worm disk/platter(?) to a jukebox which always has one more >>free slot? it isn't naive. yes it is possible, but not quite that easy (yet). i've done it several times, using a specially-modified file server kernel to initialise the bitmap for the pseudo-worm area (after that the normal code is happy to include and write to the extended space). see http://www.caldo.demon.co.uk/home9.html and http://www.caldo.demon.co.uk/work9.html (the list of machine configurations is a bit out of date). > filsys main c[p(w0)0.25p(w0)25.25p(w0)50.25]f[w1.<0-1>.0] interleaving this way on a single disc always seemed slower to me. it might make sense across dedicated drives, but i haven't tried that recently. --upas-tyrzjwrrhulswfsspfsjfdlfwl Content-Type: message/rfc822 Content-Disposition: inline Received: from finch-punt-12.mail.demon.net ([194.217.242.36]) by lavoro; Thu Apr 12 22:01:56 BST 2001 Received: from punt-1.mail.demon.net by mailstore for forsyth@caldo.demon.co.uk id 987104733:10:13542:0; Thu, 12 Apr 2001 19:45:33 GMT Received: from psuvax1.cse.psu.edu ([130.203.4.6]) by punt-1.mail.demon.net id aa1120754; 12 Apr 2001 19:45 GMT Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.20.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 0582519A10; Thu, 12 Apr 2001 15:45:12 -0400 (EDT) Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 4336519A0A for <9fans@cse.psu.edu>; Thu, 12 Apr 2001 15:44:36 -0400 (EDT) Received: from zeus.cs.utwente.nl (zeus.cs.utwente.nl [130.89.10.12]) by utrhcs.cs.utwente.nl (8.9.3/8.9.3) with ESMTP id VAA00627 for <9fans@cse.psu.edu>; Thu, 12 Apr 2001 21:44:32 +0200 (MET DST) Received: from polya.cs.utwente.nl by zeus.cs.utwente.nl (8.8.8+Sun/csrelay-Sol1.4/RB) id VAA27839; Thu, 12 Apr 2001 21:44:32 +0200 (MET DST) Received: from localhost by polya.cs.utwente.nl (8.8.8+Sun/SMI-SVR4) id VAA27862; Thu, 12 Apr 2001 21:44:31 +0200 (MET DST) Message-Id: <200104121944.VAA27862@polya.cs.utwente.nl> To: 9fans@cse.psu.edu Subject: Re: [9fans] fs (config) questions In-reply-to: Your message of "Wed, 11 Apr 2001 22:20:24 +0200." <200104112020.WAA24727@polya.cs.utwente.nl> References: <200104112020.WAA24727@polya.cs.utwente.nl> From: Axel Belinfante X-Organisation: University of Twente, Department of Computer Science, Formal Methods and Tools Group, PO Box 217, NL-7500 AE Enschede, The Netherlands X-Phone: +31 53 4893774 X-Telefax: +31 53 4893247 X-Face: 3YGZY^_!}k]>-k'9$LK?8GXbi?vs=2v*ut,/8z,z!(QNBk_>~:~"MJ_%i`sLLqGN,DGbkT@ N\jhX/jNLTz2hO_R"*RF(%bRvk+M,iU7SvVJtC*\B6Ud<7~`MGMp7rCI6LVp=%k=HE?-UCV?[p\$R? mI\n2/!#3/wZZsa[m7d;PKWiuH6'~ Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Thu, 12 Apr 2001 21:44:31 +0200 To follow up on my own message: I just more or less completed setting up the file server. I'm still interested in feedback on the more general question of what would be sensible filesys configs. Another, maybe a bit naive, question: the worm-like nature of the pseudo worm will cause it to fill up eventually. Would it be possible to plug in another disk and configure that as part of an existing pseudo-worm, like if you would be adding a worm disk/platter(?) to a jukebox which always has one more free slot? W.r.t. the fileserver I just brought up: There are probably still some rough edges, but I can boot the auth/cpu server from it, and connect to it via drawterm. However, when I ssh to it, it dies: telnetd 202: suicide: sys: trap: fault read addr=0x4326 pc=0x00004326 telnetd 196:die Any ideas where to look for that? (after the eastern weekend :-) Axel. > I'm trying to build a file server. The available documentation > gives me a pretty good idea of how to configure it (or so it seems), > provided I know what I want. The question is, given the hardware available > to me, what would be a 'sensible' configuration? > > Recent file server discussion suggested to me at least two rules of thumb: > 1) keep it simple > 2) when 'stealing' one (or more) partition(s) from a pseudo cached worm, > take them from the cache disk, and not from the pseudo worm > 3) go back to rule 1) > Are there other 'rules'? For example, for a cached (pseudo) worm, how big > should the cache be, e.g. relative to worm, or to number of users or ...? > > The hardware available to me consists of a pc with two scsi controllers. > The first controller controls a single 4Gb disk. > The second controller controls two 8Gb disks. > > My idea was to use the two 8Gb disks as pseudo-worm, > and (part of?) the 4Gb disk as cache. > How much cache would be sensible? > Should I concatenate the two 8Gb disks, or is it better > to interleave them? > Would it make sense to define partitions on the 8Gb disks? > (probably not, because of KISS) > > The remainder of this messages describes my attempts so far. > Unfortunately, I did not capture all error messages so it is > a bit vague. I will try again, and come with more concrete > questions and details if I encounter problems. > I hope this still provides enough information for someone to react > on the configurations I tried. > > Before the March 27 update I tried to boot the pc with a 9pcfs kernel, > but it did hang even before printing the config: prompt. > With the march 27 update I got to the config: prompt. > I tried as firs configuration (typing from memory, because the actual > attempt I made already a little more than a week ago) > (omitting the ip/ream/end stuff) > > filsys main c[p(w0)0.25p(w0)25.25p(w0)50.25]f[w1.<0-1>.0] > filsys dump o > filsys temp p(w0)75.25 > > but this failed (error message about the config, I think, but I did > not see the what's wrong with it). > > Then I tried the simpler > > filsys main cp(w0)0.25f[w1.<0-1>.0] > filsys dump o > filsys temp p(w0)25.75 > > which also did not work (again, I think, I got some error message, > without understanding the error) > > The even more simple > > filsys main cw0f[w1.<0-1>.0] > filsys dump o > > seemed to work at first, but this no longer gives me un-dumped temp space. > Moreover, after reboot of the fs it had problems reading the configuration > (I recall error messages like 'filsss unknown command' or something similar: > an error message containing what seems to be a fsconfig command, but > with some character duplicated, replacing the original character, > giving an erroneous command) > Does this sound familiar to someone?i > > I intend to (soon) retry building the file server, and then try to have > a laptop connected to the fs as console (the output scrolls too fast, > and, worse, disappears when the fs kernel crashes and reboots.) > I still have to read the man pages, but I recall having seen a 'cons' > command or something similar, and a plan9.ini console config entry. > > Thanks in advance for any feedback, > Axel. --upas-tyrzjwrrhulswfsspfsjfdlfwl--