From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] Fs64 file server, partition boundaries out of range From: Gregory Pavelcak Date: Thu, 10 Aug 2006 08:44:37 -0400 In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-tfgkjeqyaacdcnakommqdreruo" Topicbox-Message-UUID: 9b697380-ead1-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --upas-tfgkjeqyaacdcnakommqdreruo Content-Disposition: ainline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Just to follow up. When I try to copyworm with c[w0w1]f{h0h2}, or f{h0h2}, or fh0 I get the following right after `beginning copyworm in 8 seconds' fworm: read 0 i/o error reading fh0 block 0 panic: no blocks to copy on fh0 cpu 0 exiting I should say that things like history, yesterday, 9fs dump have been working as advertised, so I do have a functioning worm. I also tried to make main h0 and be explicit about the fake worm-ness of output, which I hadn't been before (filsys output f{w2w3}). This was definitely different. For one, it took even longer than my other tries. But, instead of the `copyworm finished ... looping ... reset any time' message, it had rebooted itself. I'm going to stop this effort for a little while. At least until I get console logging set up, so that I can be sure to be accurate when I report what happened. Thanks again. Greg -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Geoff Collyer 7 Aug 2006 wrote: I think I understand your problem now. If you were copying a fake worm to a device of identical size, you could use copydev from h0, but when copying a fake worm, you need to use copyworm from fh0 or possibly even your normal main (c[w0w1]f{h0h2}). check reports an fsize of 712733, so that's the highest block number so far consumed by your fake worm, and is what copyworm should print as your limit (plus or minus a few blocks) when you copy from fh0 or your normal main. When you copied from h0, copyworm just used the size of h0 as its upper limit. Perhaps copyworm should complain if the source file system does not contain a worm. --upas-tfgkjeqyaacdcnakommqdreruo Content-Type: message/rfc822 Content-Disposition: ainline Received: from mail.cse.psu.edu (psuvax1.cse.psu.edu[130.203.4.6]) by sccrmxc18.comcast.net (sccrmxc18) with ESMTP id <20060807213020s1800gbbq9e>; Mon, 7 Aug 2006 21:30:20 +0000 X-Originating-IP: [130.203.4.6] Received: from psuvax1.cse.psu.edu (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 8F6C3A51B for ; Mon, 7 Aug 2006 17:29:57 -0400 (EDT) X-Original-To: 9fans@cse.psu.edu Delivered-To: 9fans@cse.psu.edu Received: from localhost (localhost [127.0.0.1]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id CD7A4638F5 for <9fans@cse.psu.edu>; Mon, 7 Aug 2006 17:29:21 -0400 (EDT) Received: from mail.cse.psu.edu ([127.0.0.1]) by localhost (psuvax1 [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 28350-01-6 for <9fans@cse.psu.edu>; Mon, 7 Aug 2006 17:29:19 -0400 (EDT) Received: from plan9.cs.bell-labs.com (outside.cs.bell-labs.com [204.178.31.2]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id D308C5AAE9 for <9fans@cse.psu.edu>; Mon, 7 Aug 2006 17:29:18 -0400 (EDT) Message-ID: To: 9fans@cse.psu.edu Subject: Re: [9fans] Fs64 file server, partition boundaries out of range Date: Mon, 7 Aug 2006 17:29:16 -0400 From: geoff@plan9.bell-labs.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces+g.pavelcak=comcast.net@cse.psu.edu Errors-To: 9fans-bounces+g.pavelcak=comcast.net@cse.psu.edu You have to set up console logging yourself on a cpu server, like this: aux/clog /mnt/consoles/fileserver /sys/log/fileserver & where "fileserver" is the name of your file server. This assumes you've already got consolefs(4) configured, running and mounted, and that you've got the file server's serial console configured and wired up to a serial port on the cpu server doing the logging. Add this to your file server's plan9.ini: console=0 baud=9600 It's a bit of work to set up, but very handy. Not only do you get a console log, but you can access the console from any of your Plan 9 machines with: C fileserver --upas-tfgkjeqyaacdcnakommqdreruo--