From: Vitaly Fertman <vitaly@namesys.com>
To: Konstantin Sobolev <kos@supportwizard.com>, reiserfs-list@namesys.com
Subject: Re: fsck.reiser4 segfaults
Date: Thu, 15 Jul 2004 16:21:44 +0400 [thread overview]
Message-ID: <200407151621.44263.vitaly@namesys.com> (raw)
In-Reply-To: <200407151559.41256.kos@supportwizard.com>
Hello,
On Thursday 15 July 2004 15:59, Konstantin Sobolev wrote:
> Hi all,
>
> I have 2 computers running reiser4 partitions. Once I decided to check them
> for errors, and on both machines fsck reported that SB is corrupted. I
> suppose that's because partitions were formatted by older versions of
> reiser4progs. --build-sb worked OK. Then fsck reported about some
> corruptions that were successfully repaired with --build-fs on the first
> machine. However, on the second one fsck segfaults on attempt to do a
> repair.
>
> The output is:
> [skip]
> ***** Semantic Traverse Pass: reiser4 semantic tree checking.
> FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (3)
> set to (smart). Added.
> FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (4)
> set to (r5_hash). Added.
> FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (5)
> set to (dot_o_fibre). Added.
> FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (6)
> set to (stat40). Added.
> FSCK: Node (1260442), item (0), [29:0:2a] (stat40): needs pset member (7)
> set to (cde40). Added.
> Segmentation fault
>
> fsck version is fsck.reiser4 0.5.5, kernel is 2.6.4 with latest stable
> reiser4 snapshot
would you try the latest reiser4progs from
www.namesys.com/snapshots/2004.07.13-internal.testing/
> I've packed fs metadata with debugfs.reiser4 -P /dev/hda6 | bzip2 -c >
> hda6debug.bz2, it can be downloaded from
> http://www.prokhorov.org/hda6debug.bz2 , 38Mb
if the new fsck fails we will debug it with your metadata.
> Partition still can be mounted but I don't know if it is risky to work with
> it, I don't want to loose it completely.
--
Thanks,
Vitaly Fertman
next prev parent reply other threads:[~2004-07-15 12:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 11:59 fsck.reiser4 segfaults Konstantin Sobolev
2004-07-15 12:21 ` Vitaly Fertman [this message]
2004-07-15 13:11 ` Snapshot 2004.07.13 build problems (was: Re: fsck.reiser4 segfaults) Raymond A. Meijer
2004-07-15 13:27 ` Vitaly Fertman
2004-07-15 13:37 ` Raymond A. Meijer
[not found] ` <200407151739.17893.vitaly@namesys.com>
2004-07-15 13:57 ` Raymond A. Meijer
2004-07-15 18:45 ` fsck.reiser4 segfaults Konstantin Sobolev
2004-07-15 19:09 ` Vitaly Fertman
2004-07-15 19:22 ` Konstantin Sobolev
2004-07-16 9:33 ` mjt
2004-07-15 19:26 ` Vitaly Fertman
-- strict thread matches above, loose matches on Subject: below --
2006-03-31 14:21 Sarath Menon
2006-03-31 16:17 ` Vladimir V. Saveliev
2006-03-31 16:32 ` Vladimir V. Saveliev
2006-03-31 18:21 ` Sarath Menon
2006-03-31 20:21 ` Michael Weissenbacher
2006-04-01 6:02 ` Joachim Feise
2006-04-01 8:13 ` Sarath Menon
2006-04-01 9:02 ` Jake Maciejewski
2006-04-03 10:21 ` Vladimir V. Saveliev
[not found] ` <932539950604041657t42d33902s34dc8abcf056aa49@mail.gmail.com>
2006-04-05 0:00 ` Sarath Menon
2006-07-07 6:46 ` Sarath Menon
2006-08-09 13:03 Jussi Suutari-Jaasko
2006-08-10 8:19 ` Jussi Suutari-Jääskö
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=200407151621.44263.vitaly@namesys.com \
--to=vitaly@namesys.com \
--cc=kos@supportwizard.com \
--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.