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: Mon, 7 Aug 2006 18:50:17 -0400 In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-kpgqrzevtgnxprehgjrmqjfyjc" Topicbox-Message-UUID: 98e945d6-ead1-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --upas-kpgqrzevtgnxprehgjrmqjfyjc Content-Disposition: ainline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Console setup definitely seems worthwhile, but it will take me a little time to get to it. On the off chance I got some useful output from check, here it is. I don't think too much scrolled by. check: "/386/bin/upas/filter": xtag: checktag tag=Tnone/0; expected Tind1/50352 -- flushed (225420) check: "/386/bin/upas/list": xtag: checktag tag=Tnone/0; expected Tind1/50391 -- flushed (225953) check: "/386/bin/upas/_marshal": xtag: checktag tag=Tnone/0; expected Tind1/50406 -- flushed (226221) check free list lo=656348 hi=703242 nfiles=43599 fsize=712733 nused=201282 ndup=0 nfree=38803 tfree=38803 nfdup=0 nmiss=472646 nbad=0 nqbad=0 maxq=167269 base stack=620 high stack=1920 of 16000 deepest recursion=13 That's from the following config. When I did copyworm, I just had h0 as main and w2 as output; otherwise I get the no blocks to copy message. config w0 service pinky filsys main c[w0w1]f{h0h2} filsys dump o ipauth 192.168.0.109 ip 192.168.0.108 ipgw 192.168.0.1 ipmask 255.255.255.0 Just for the record, I tried copyworm from h0 to (w2w3) giving me approximately 100G target. There were no error messages at the end of copyworm, but when I tried to boot c[w0w1]f(w2w3) I got tag=Tnone/0; expected Tvirgo/12211541 - flushed (12211541) panic:fworm:checktag 12211541 cpu 0 exiting which is like what I started with only apparently reflecting the larger size Greg --upas-kpgqrzevtgnxprehgjrmqjfyjc 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-kpgqrzevtgnxprehgjrmqjfyjc--