All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Matthias Urlichs <smurf@noris.de>,
	Oleg Drokin <green@namesys.com>,
	reiserfs-list@namesys.com
Subject: Re: fsck mode halfway between --fix-fixable and --rebuild-tree ?
Date: Tue, 01 Oct 2002 15:02:08 +0400	[thread overview]
Message-ID: <3D9980B0.1010909@namesys.com> (raw)
In-Reply-To: 15769.21090.312924.423577@laputa.namesys.com

Nikita Danilov wrote:

>Matthias Urlichs writes:
> > Hi,
> > 
> > Nikita Danilov:
> > > Actually, B-link trees (B-trees with sibling pointers) don't require any
> > > additional io for sibling pointers maintenance. Just draw a picture of
> > > what is going on during insertion of new node or node deletion and you
> > > will see. B-link disadvantages are extra space required in a node to
> > > store the sibling pointer and unfriendliness to the "wandered logging".
> > > 
> > Would a wandering log really store the updated blocks themselves, or just
> > _log_ them?  In the latter case I don't see the difference between a
> > wandering log and the static log we have now; the former case looks like
> > it'd have to write at least three times as much log data (not only the
> > leaf block, but going all the way back to the root) even without taking
> > sibling blocks into account.
>
>Wandered logs in particular and reiser4 transaction design in general
>are exposed at the http://www.namesys.com/txn-doc.html. Take a look.
>
> > 
> > -- 
> > Matthias Urlichs     |     noris network AG     |     http://smurf.noris.de/
>
>Nikita.
>
>
>  
>
zam and I just came to the conclusion yesterday that that paper was 
hopelessly outdated and needs a complete rewrite after Halloween....



  reply	other threads:[~2002-10-01 11:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-28  9:28 Reiserfs/emacs incompatibility/bug ? arthur.chereau
2002-09-29 15:23 ` fsck mode halfway between --fix-fixable and --rebuild-tree ? Matthias Urlichs
2002-09-30  6:18   ` Oleg Drokin
2002-09-30 11:12     ` Hans Reiser
2002-09-30 11:15       ` Oleg Drokin
2002-09-30 11:17       ` Matthias Urlichs
2002-09-30 11:22         ` Oleg Drokin
2002-09-30 13:08           ` Matthias Urlichs
2002-09-30 13:20             ` Hans Reiser
2002-09-30 17:36               ` Matthias Urlichs
2002-09-30 17:56                 ` Valdis.Kletnieks
2002-10-01  6:37               ` Nikita Danilov
2002-10-01  7:32                 ` Matthias Urlichs
2002-10-01  7:44                   ` Nikita Danilov
2002-10-01 11:02                     ` Hans Reiser [this message]
2002-10-01 11:00                 ` Hans Reiser
2002-10-01 11:12                   ` Nikita Danilov
2002-10-01 12:15                   ` Matthias Urlichs
2002-10-01 18:43                     ` Hans Reiser
2002-10-02  8:13                       ` Matthias Urlichs
2002-10-02 11:04                         ` Vitaly Fertman
2002-10-02 12:21                           ` Matthias Urlichs
2002-09-30 15:15             ` Vitaly Fertman
2002-09-30 11:43         ` Vitaly Fertman
2002-09-29 23:54 ` Reiserfs/emacs incompatibility/bug ? Matthias Andree

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=3D9980B0.1010909@namesys.com \
    --to=reiser@namesys.com \
    --cc=Nikita@Namesys.COM \
    --cc=green@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=smurf@noris.de \
    /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.