From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 18 Aug 2006 22:38:49 +0200 To: 9fans <9fans@cse.psu.edu> Subject: Re: [9fans] err 2: arena creation time after last write time From: csant Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 References: <3096bd910608180440o216712c4i68a577245469ff92@mail.gmail.com> <7d3530220608181329w357504c9s95396f72f3bdddae@mail.gmail.com> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <7d3530220608181329w357504c9s95396f72f3bdddae@mail.gmail.com> User-Agent: Opera Mail/9.02 (Linux) Topicbox-Message-UUID: a3e28592-ead1-11e9-9d60-3106f5b1d025 >> > I have a new installation of Plan9 (fossil+venti) in a Qemu, in the >> first >> > reboot the venti starts and then the console start to show: >> > >> > "err 2: arena creation time after last write time" >> > >> > why? >> >> I recently had that problem after a clean install of Plan 9 fossil+venti >> because there was a network error and the time could not be correctly >> sync'ed. That network problem showed up only in the fossil+venti >> installation and not the fossil one. >> >> /c >> > So, does this lead to big problems with Venti? I've wondered this > before--what if your clock gets mis-set, Venti makes an archive, and > then you reset your clock, but there's suddenly an archive /from the > future/! (cue Twilight Zone theme) I had just been understanding that venti does a dump at a given time, and stores it in something like /n/dump/// The only problem I could see here is if you dump twice on the same day, i.e. once in a future date, and then, after resetting your clock, on the right date once you reach it. How does venti handle that? /c