From: Yury Umanets <umka@namesys.com>
To: Kevin <coggy@redefine.org>
Cc: reiserfs-list@namesys.com
Subject: Re: access beyond end of device
Date: Sat, 15 Jun 2002 22:13:17 +0400 [thread overview]
Message-ID: <3D0B83BD.9010404@namesys.com> (raw)
In-Reply-To: 93554601344.20020615110307@redefine.org
Kevin wrote:
>I checked the mailing list archive, and I didn't see any solutions.
>It also seemed the the similar problems happened after a crash, which
>is not so in my case. Recently I was trying to extract a file and I
>got read errors. I checked dmesg and found the following repeated:
>
> attempt to access beyond end of device
> 38:01: rw=0, want=788705992, limit=58633312
> attempt to access beyond end of device
> 38:01: rw=0, want=788705992, limit=58633312
>
>Running reiserfsck --check gave me a bunch of things similar to this:
>bad_indirect_item: block 16371: item 2014 2043 0x1 IND (1), len 1276,
>location 96 entry count 0, fsck need 0, format new has a pointer 131
>to the block 9437328 which is in tree already
>9437328 which is in tree already
>
>It also found one broken file, and said that there was 1 corruption
>that required --rebuild-tree. I haven't done this yet because I'm a
>little worried it might die in the middle of the rebuild. Anyone have
>any idea what I should do?
>
>I am running 2.4.18, and reiserfsprogs 3.x.1c-pre4.
>
>
>
>
Anyway you may backup your data and try to rebuild tree by fsck.
>
>
next prev parent reply other threads:[~2002-06-15 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-15 18:03 access beyond end of device Kevin
2002-06-15 18:13 ` Yury Umanets [this message]
2002-06-15 18:37 ` Kevin
2002-06-15 20:07 ` Hans Reiser
2002-06-16 5:45 ` Kevin
-- strict thread matches above, loose matches on Subject: below --
2007-07-31 18:04 Access " Luiz Fernando N. Capitulino
2007-07-31 18:15 ` Luiz Fernando N. Capitulino
2007-08-01 0:12 ` Alan Cox
2007-08-01 14:17 ` Luiz Fernando N. Capitulino
2007-08-01 16:03 ` Alan 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=3D0B83BD.9010404@namesys.com \
--to=umka@namesys.com \
--cc=coggy@redefine.org \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.