From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: Steven Stallion Date: Tue, 12 Dec 2017 10:23:16 -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: c6107c7a-ead9-11e9-9d60-3106f5b1d025 It depends - the 30GB I was mentioning before was from an older Ken's fs that I imported with a modified cwfs. Rather than deal with all of the history, I just took a snap with vac -s of the latest state of the file system. I keep the original dump along with the cwfs binary in case I ever need to dig into the dump (I haven't needed to in years). The last venti store I needed to move around I was able to just use rdarena/wrarena to reconstitute the fs on new hardware. I think it comes down to what you want to preserve - life gets easier if you don't need to worry about the dump. I don't think it would be too tough to script the dump though. You probably would just need to walk through each successive vac and archive it using vac -a. Probably easier said than done though :-) Steve On Tue, Dec 12, 2017 at 10:11 AM, Steve Simon wrote: > Interesting. > > how did you do the import? did you use vac -q and vac -d previous-score for each > imported day to try and speed things up? > > Previously I imported stuff into venti by copying it into fossil first > and then taking a snap. I always wanted a better solution, like being able > to use vac and then installing the score into my main filesystem through > a special fscons command. Sadly I never got around to it. > > -Steve >