From: Hans Reiser <reiser@namesys.com>
To: Payal Rathod <payal-fs@scriptkitchen.com>
Cc: reiserfs-list@namesys.com
Subject: Re: somewhat OT query on journalling
Date: Wed, 19 Jul 2006 13:28:38 -0700 [thread overview]
Message-ID: <44BE95F6.50004@namesys.com> (raw)
In-Reply-To: <20060719152744.GA26155@tranquility.scriptkitchen.com>
Payal Rathod wrote:
>Hi,
>I was just reading about filesystems and my ideas are a bit confused.
>I read quite a few articles on net but still my basic doubts are not
>completely clarified. I thought this would be the right place to ask, since many
>journalling gurus might be here.
>Can someone tell me do journalling fs maintain journal about the
>metadata or the all the data?
>
>
V3 defaults to metadata only, V4 does data also because we can do it
without performance loss.
>Also, is it true that now-a-days there is no such thing as inode "block"
>since for faster access the inodes are kept near the data itself?
>
>
reiserfs does not use inodes at all. see our website for more.
>How is the journal maintained? How is it prevented from being
>too big and why are these fs not slower than traditional fs since it
>involves an overhead of writing to a journal?
>
>
see website. there is overhead. for v4 it is not a lot though.
>And lastly don't the journalling fs give a false sense of security to
>the user, saying that the data is written to disk when in reality only an
>entry is made in journal and data is still not committed to disk.
>
>
someone else anwered this....
>Thanks a lot for the patience and eagerly waiting for any replies.
>
>With warm regards,
>-Payal
>
>
>
>
>
next prev parent reply other threads:[~2006-07-19 20:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 15:27 somewhat OT query on journalling Payal Rathod
2006-07-19 17:30 ` Toby Thain
2006-07-19 17:30 ` Toby Thain
2006-07-19 19:09 ` David Masover
2006-07-19 19:19 ` David Masover
2006-07-19 20:28 ` Hans Reiser [this message]
2006-07-21 12:45 ` Payal Rathod
2006-07-21 18:54 ` David Masover
2006-07-21 21:26 ` Andreas Schäfer
2006-07-21 21:53 ` David Masover
2006-07-22 0:54 ` Hans Reiser
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=44BE95F6.50004@namesys.com \
--to=reiser@namesys.com \
--cc=payal-fs@scriptkitchen.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.