From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <93bf184cc769cfc3e70f470d6876a1a8@quintile.net> From: Steven Stallion Date: Tue, 12 Dec 2017 13:16:30 -0600 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] A potentially useful venti client Topicbox-Message-UUID: c61e70aa-ead9-11e9-9d60-3106f5b1d025 I ran back through my old notes. Turns out I inflated the numbers a bit - it was about a week rather than a month. I suspect the main culprit is the fact that 9p doesn't support multiple outstanding. I wasn't in much of a hurry at the time, so I'm sure there are more efficient ways than simply firing up cwfs and using vac -s. On Tue, Dec 12, 2017 at 12:42 PM, Ole-Hjalmar Kristensen wrote: > Thanks for the tip about mounting with 9fs. I have used vacfs on Linux , > though. > But why so slow? Did you import a root with lots of backup versions? It was > partly because of that I made this client which can import venti blocks > without needing to traverse a file tree over and over again. > > On Tue, Dec 12, 2017 at 4:45 PM, Steven Stallion > wrote: >> >> Get ready to wait! It took almost a month for me to import about 30GB >> from a decommissioned file server. It was well worth the wait though - >> if you place the the resulting .vac file under /lib/vac (or >> $home/lib/vac) you can just use 9fs to mount with zero fuss. >> >> On a related note, once sources starting having issues with >> availability, I started running nightly snaps of my contrib directory >> via cron: >> >> contrib=/n/sources/contrib/$user >> 9fs sources >> @{cd $contrib && vac -a $home/lib/vac/contrib.vac .} >[2]/dev/null >> >> Now I have a dump-like history of changes I've made to my contrib >> directory without the need to connect to sources: >> >> % 9fs contrib.vac >> % lc /n/contrib >> 2015 2016 2017 >> >> Cheers, >> Steve >> >> On Tue, Dec 12, 2017 at 8:07 AM, Steve Simon wrote: >> > printarenas is a script - it walks through all your arenas at each >> > offset. >> > >> > You could craft another script that remembers the last arena and offset >> > you successfully >> > transferred and only send those after that. >> > >> > I think there is a pattern where you can save the last arena,offset in >> > the local >> > fossil. Then you could mount the remote venti to check that last >> > arena,offset >> > that actually arrived and stuck to the disk on the remote site. >> > >> > On a similar subject I have 10 years of backups from a decomissioned >> > work server >> > that I need to merge into my home venti one of these days... >> > >> > -Steve >> > >> >