From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil/venti: diskReadRaw failed
Date: Wed, 19 Mar 2003 15:39:23 -0500 [thread overview]
Message-ID: <fd97175116cec64c5602a90feb4e7487@plan9.bell-labs.com> (raw)
In-Reply-To: <200303192034.h2JKY9c05096@zamenhof.cs.utwente.nl>
this is giving you the path from the block with the
i/o error all the way back up to the root block.
given that 0xf61d is readable yet 0xee65 is not,
i'd say you have a real disk error rather than
an overflow.
try running cp /dev/sdC0/fossil /dev/null and
see if you get i/o errors then.
diskReadRaw failed: part=3 addr=ee65: i/o error
archive(0, 0xee65): cannot find block: i/o error
archWalk 0xee65 failed; ptr is in 0xece8 offset 190
archWalk 0xece8 failed; ptr is in 0xd5c0 offset 7
archWalk 0xd5c0 failed; ptr is in 0xe877 offset 41
archWalk 0xe877 failed; ptr is in 0xe876 offset 4
archWalk 0xe876 failed; ptr is in 0xe875 offset 2
archWalk 0xe875 failed; ptr is in 0xe874 offset 4
archWalk 0xe874 failed; ptr is in 0xe873 offset 5
archWalk 0xe873 failed; ptr is in 0xe872 offset 2
archWalk 0xe872 failed; ptr is in 0xe871 offset 8
archWalk 0xe871 failed; ptr is in 0xe870 offset 42
archWalk 0xe870 failed; ptr is in 0xf61f offset 0
archWalk 0xf61f failed; ptr is in 0xf61e offset 0
archWalk 0xf61e failed; ptr is in 0xf61d offset 0
archiveBlock 0xf61d: i/o error
next prev parent reply other threads:[~2003-03-19 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 20:34 Axel Belinfante
2003-03-19 20:39 ` Russ Cox [this message]
2003-03-19 20:52 ` Axel Belinfante
2003-03-19 21:01 ` Axel Belinfante
2003-03-19 21:12 ` Russ Cox
2003-03-19 23:07 ` [9fans] [OT] heat-stroken disk? (was fossil/venti: diskReadRaw failed) Axel Belinfante
2003-03-19 21:01 ` [9fans] fossil/venti: diskReadRaw failed Russ Cox
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=fd97175116cec64c5602a90feb4e7487@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).