From: Hans Reiser <reiser@namesys.com>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: reiserfs-list@namesys.com, Paul Gear <paul@gear.dyndns.org>
Subject: Re: Corrupt reiser3 fs
Date: Mon, 13 Jun 2005 11:08:42 -0700 [thread overview]
Message-ID: <42ADCBAA.603@namesys.com> (raw)
In-Reply-To: <200506131346.23587.vitaly@namesys.com>
Vitaly Fertman wrote:
>On Sunday 12 June 2005 02:42, Paul Gear wrote:
>
>
>>Hi folks,
>>
>>After filling my reiserfs with backups, i ended up with a corrupt
>>filesystem. I'm running Debian 3.1 (sarge), kernel 2.6.8-2-k7, and
>>reiserfsprogs 3.6.19-1.
>>
>>I don't care about this filesystem and will just recreate it, but i
>>thought i'd offer folks the opportunity to debug before i trash it.
>>
>>Here's my fsck output with all the noise cut out:
>>
>>---------8<----------------------------------------
>>
>>enoch:/tmp # fsck.reiserfs --rebuild-tree /dev/hdc1
>>...
>>111392 directory entries were hashed with "r5" hash.
>> "r5" hash is selected
>>Flushing..finished
>> Read blocks (but not data blocks) 19333032
>> Leaves among those 32365
>> - corrected leaves 35
>> - leaves all contents of which could not be
>>saved and deleted 5
>> pointers in indirect items to wrong area 25647 (zeroed)
>> Objectids found 104921
>>
>>Pass 1 (will try to insert 32360 leaves):
>>####### Pass 1 #######
>>Looking for allocable blocks .. finished
>>0%....20%....40%....60%... left 8239,
>>234 /sec
>>The problem has occurred looks like a hardware problem (perhaps
>>memory). Send us the bug report only if the second run dies at
>>the same place with the same block number.
>>
>>build_the_tree: Nothing but leaves are expected. Block 10905053 - unknown
>>
>>
Please improve this error message if you can.
>
>does it stop every time on the block 10905053 ?
>
>
>
>>There is no problem with memory (my other two hard disks and all of my
>>desktop programs are working fine), or, to my knowledge, the hard disk
>>or cable (since i can do a full dd of the hard disk to /dev/null).
>>
>>Anyone interested in taking a look at it, or should i just write it off
>>as stray gamma rays from Saturn and trash it? :-)
>>
>>
>>
>
>
>
prev parent reply other threads:[~2005-06-13 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 22:42 Corrupt reiser3 fs Paul Gear
2005-06-12 17:35 ` evilninja
2005-06-13 9:46 ` Vitaly Fertman
2005-06-13 18:08 ` Hans Reiser [this message]
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=42ADCBAA.603@namesys.com \
--to=reiser@namesys.com \
--cc=paul@gear.dyndns.org \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.