From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <166806220906111706h34ac9dbat54ed0e1733e52082@mail.gmail.com> References: <166806220906111706h34ac9dbat54ed0e1733e52082@mail.gmail.com> Date: Thu, 11 Jun 2009 23:00:03 -0400 Message-ID: <3aaafc130906112000p2805a98ataaa4b2b32fdf8227@mail.gmail.com> From: "J.R. Mauro" To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] p9p venti problem Topicbox-Message-UUID: 099b65d6-ead5-11e9-9d60-3106f5b1d025 I can't help with this in particular, but QEMU does some really low-level hackery to the point where it wouldn't compile with GCC 4, so it's possible something like that is going on here. On Thu, Jun 11, 2009 at 8:06 PM, Adrian Tritschler wrote: > I've got a p9p venti running on two separate ubuntu linux boxes that > I've been using for months to keep backups of data and for QEMU plan9 > guests. =A0They have both stopped working, I suspect due to a recent > ubuntu kernel update. =A0I've rebuilt all of p9p but to no avail. > > The QEMU guests crash on boot stating "error reading block 43a72...3 > or wrong score: read too small 1: asked for 0 need at le... > panic: boot process died: unknown" > > Any attempt to write data into either venti on the linux systems fails > with the error: > > ajft@xyz:~/tmp$ vac x > create bsize 8192 psize 8160 > vac: vacfscreate: vacfileroot: read too small 1: asked for 0 need at leas= t 389 > > reading any existing *.vac file also fails: > > ajft@xyz:~/venti/2009/04/24$ unvac -t xyz_bin-2009-04-24.vac > unvac: vacfsopen: read too small 1: asked for 0 need at least 300 > > Any ideas? > -- > Adrian > >