From: "J.R. Mauro" <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] p9p venti problem
Date: Thu, 11 Jun 2009 23:00:03 -0400 [thread overview]
Message-ID: <3aaafc130906112000p2805a98ataaa4b2b32fdf8227@mail.gmail.com> (raw)
In-Reply-To: <166806220906111706h34ac9dbat54ed0e1733e52082@mail.gmail.com>
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<ajft@ajft.org> 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. They have both stopped working, I suspect due to a recent
> ubuntu kernel update. I'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 least 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
>
>
next prev parent reply other threads:[~2009-06-12 3:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 0:06 Adrian Tritschler
2009-06-12 3:00 ` J.R. Mauro [this message]
2009-06-12 3:34 ` Venkatesh Srinivas
2009-06-12 3:41 ` Venkatesh Srinivas
2009-06-12 6:55 ` Adrian Tritschler
2009-06-12 7:18 ` Venkatesh Srinivas
2009-06-12 7:26 ` Venkatesh Srinivas
2009-06-22 8:53 ` Mathieu
2009-06-12 14:07 ` J. R. Mauro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3aaafc130906112000p2805a98ataaa4b2b32fdf8227@mail.gmail.com \
--to=jrm8005@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).