backing up (was: cwfs...)

[Ethan Grammatikidis <eekee57@fastmail.fm>]

On Fri, 13 Apr 2012 12:55:20 +0200
cinap_lenrek@gmx.de wrote:

> looking at the source, it seems you get that error because
> the superblock hasnt been written to the worm yet.
> 
> this only happens when you start with a blank worm partition.
> 
> the error here looks spooky, but i think its non critical in
> that case. consinit just fires a touchsb command without
> really caring for the result.
> 
> you might add the following code to the end of cwream()
> 
> 	/* write superblock to worm */
> 	while(dumpblock(dev))
> 		;
> 
> --
> cinap

Thanks. I don't think I'm going to be able to test this, I've got
random dysfunction to worry about. The ethernet failures came back a
few hours after I unplugged the usb drive yesterday (which has been
perma-connected the last few weeks). On the next boot the machine's
keyboard stopped working after I connected with drawterm, and just now
I found connections on port 80 are timing out where they were fine
yesterday.

I'm going to go through with my upgrade and watch for errors after
that. I also want to back up to my linux machine daily but I'm not
entirely sure how. Copying files which exist in the latest dump dir but
not the previous one seems sensible. (Correct me if I'm wrong.) I'm not
sure what to put the files into at the Linux end as I want to preserve
history. I could use vac with p9p's venti I guess, or I could run cwfs
in a vm. (Or kfs in a vm. ;) I think I would prefer cwfs, any thoughts?