From: Alex Zarochentsev <zam@namesys.com>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
Cc: Paolo Correnti <paolunix@yahoo.com>,
REISER LIST <reiserfs-list@namesys.com>
Subject: Re: REISER4 corruptions errors
Date: Mon, 26 Jan 2004 18:51:49 +0300 [thread overview]
Message-ID: <20040126155148.GC21337@backtop.namesys.com> (raw)
In-Reply-To: <401541FA.5060309@gmx.net>
On Mon, Jan 26, 2004 at 05:36:10PM +0100, Carl-Daniel Hailfinger wrote:
> Alex Zarochentsev wrote:
>
> > this patch should help (! not tested):
> >
> > ===== tree.c 1.562 vs edited =====
> > --- 1.562/tree.c Wed Jan 14 11:46:20 2004
> > +++ edited/tree.c Mon Jan 26 18:24:39 2004
> > @@ -1468,7 +1468,7 @@
> > if ((result != 0) && (result != -E_NO_NEIGHBOR))
> > break;
> > /* Check can we delete the node as a whole. */
> > - if (iterations && znode_get_level(node) == LEAF_LEVEL &&
> > + if (0 && iterations && znode_get_level(node) == LEAF_LEVEL &&
> > UNDER_RW(dk, current_tree, read,
> > keyle(from_key, znode_get_ld_key(node)))) {
> > result = delete_node(next_node_lock.node,
>
> Was it your intention to disable the above code path?
no, it will be fixed in proper way. my fix is a temporary solution.
--
Alex.
prev parent reply other threads:[~2004-01-26 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 14:46 REISER4 "strange" partition size Paolo Correnti
2004-01-23 14:52 ` Nikita Danilov
2004-01-23 15:12 ` Paolo Correnti
2004-01-26 13:52 ` REISER4 corruptions errors Paolo Correnti
2004-01-26 13:59 ` Nikita Danilov
2004-01-26 14:25 ` Paolo Correnti
2004-01-26 15:26 ` Alex Zarochentsev
2004-01-26 16:36 ` Carl-Daniel Hailfinger
2004-01-26 15:51 ` Alex Zarochentsev [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=20040126155148.GC21337@backtop.namesys.com \
--to=zam@namesys.com \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=paolunix@yahoo.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.