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
--- Begin Message ---
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
--- End Message ---
