From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Zarochentsev Subject: Re: REISER4 corruptions errors Date: Mon, 26 Jan 2004 18:51:49 +0300 Message-ID: <20040126155148.GC21337@backtop.namesys.com> References: <16405.7504.491020.659611@laputa.namesys.com> <20040126142528.22476.qmail@web21509.mail.yahoo.com> <20040126152607.GB21337@backtop.namesys.com> <401541FA.5060309@gmx.net> Mime-Version: 1.0 Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com Content-Disposition: inline In-Reply-To: <401541FA.5060309@gmx.net> List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Carl-Daniel Hailfinger Cc: Paolo Correnti , REISER LIST 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.