From: Vitaly Fertman <vitaly@namesys.com>
To: Vince <fuzzy77@free.fr>, reiserfs-list@namesys.com
Subject: Re: fsck.reiser4 1.0.0, segmentation fault
Date: Fri, 13 Aug 2004 01:43:08 +0400 [thread overview]
Message-ID: <200408130143.09138.vitaly@namesys.com> (raw)
In-Reply-To: <411BDC03.3090105@free.fr>
[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]
On Friday 13 August 2004 01:07, Vince wrote:
> Hi,
>
> I got a segmentation fault while converting my reiser4 partition to the
> new format:
>
> 1) I first launched "debugfs.reiser4 -C /mydevice"
>
> (sidenote: il looks like the conversion requires really a lot -- too
> much ? -- memory. It ate up to 450MB in my case and I had to shut down
> almost all my running programs in order for it to finish...)
>
> 2) fsck.reiser4 asks to do a --build-fs
you did not run fsck before convertion so it is difficult to say if these
corruptions existed then, did not you? have you run fsck with logfile?
may I have a look at it if so?
> and then fails with a
> segmentation fault:
> ---------------------------------------------------------------------
> [...]
> INSERTING UNCONNECTED NODES
> 1. Twigs: done
> 2. Twigs by item: done
> 3. Leaves: done
> 4. Leaves by item: done
> Twigs: read 0, inserted 0, by item 0, empty 0
> Leaves: read 0, inserted 0, by item 0
> Time interval: Thu Aug 12 23:00:11 2004 - Thu Aug 12 23:00:11 2004
> CHECKING SEMANTIC TREE
> FSCK: Node (8803157), item (4), [d43d0:6d6174685f696e:d447b] (stat40):
> wrong size (12478), Fixed to (16384).
> [=================================================- ] 99%zsh:
> segmentation fault fsck.reiser4 --build-fs /dev/hdc3
> ----------------------------------------------------------------------
>
> I'm attaching a gdb backtrace of this failure (and can send the packed
> metadata on request).
oh, sorry, a stupid mistake in the recent changes. try this fix please.
--
Thanks,
Vitaly Fertman
[-- Attachment #2: reiser4progs-1.0.0-tree_scan.patch --]
[-- Type: text/x-diff, Size: 1105 bytes --]
===== libreiser4/tree.c 1.739 vs edited =====
--- 1.739/libreiser4/tree.c Mon Aug 9 20:58:28 2004
+++ edited/libreiser4/tree.c Fri Aug 13 01:15:48 2004
@@ -3198,11 +3198,13 @@
pos = &place.pos;
- if ((res = pre_func(place.node, data)) < 0)
- return res;
+ if (pre_func) {
+ if ((res = pre_func(place.node, data)) < 0)
+ return res;
- /* If res != 0, lookup is needed. */
- if (res) continue;
+ /* If res != 0, lookup is needed. */
+ if (res) continue;
+ }
for (; pos->item < reiser4_node_items(place.node); pos->item++) {
if ((res = reiser4_place_fetch(&place)))
@@ -3216,12 +3218,17 @@
return -EIO;
}
- if ((res = pre_func(place.node, data)) < 0)
- return res;
-
- /* If res != 0, lookup is needed. */
- if (res) break;
-
+ if (pre_func) {
+ if ((res = pre_func(place.node,
+ data)) < 0)
+ {
+ return res;
+ }
+
+ /* If res != 0, lookup is needed. */
+ if (res) break;
+ }
+
count = reiser4_node_items(place.node);
place.pos.item = -1;
next prev parent reply other threads:[~2004-08-12 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 21:07 fsck.reiser4 1.0.0, segmentation fault Vince
2004-08-12 21:43 ` Vitaly Fertman [this message]
2004-08-12 22:11 ` Vince
2004-08-13 9:13 ` mjt
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=200408130143.09138.vitaly@namesys.com \
--to=vitaly@namesys.com \
--cc=fuzzy77@free.fr \
--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.