From: "Vladimir V. Saveliev" <vs@namesys.com>
To: jenn sirp <sirp1@llnl.gov>
Cc: reiserfs-list@namesys.com
Subject: Re: keys and inodes
Date: Sat, 03 Jul 2004 13:28:29 +0400 [thread overview]
Message-ID: <40E67C3D.6070609@namesys.com> (raw)
In-Reply-To: <1088802102.6434.80.camel@murdock.llnl.gov>
Hello
jenn sirp wrote:
> Hi,
>
> I was hoping someone might be able to answer a couple of questions about
> inodes is Reiser(v3).
>
> I would like to know how ReiserFS inodes and the VFS inodes in the
> d_cache correspond with each other.
You might want to read about dentry-inode relationship in
linux/Documentation/filesystem/vfs.txt.
Specifically, how and where it is
> that 'keys' get mapped to inodes in the system?
Reiserfs provides set of vfs operations. The one which is responsible
for mapping keys to inode is lookup method. reiserfs implementation is
reiserfs_lookup. It searches for the file name in filesystem tree. If
name is found - file key is extracted from it and VFS inode is created
(connected to d_cache dentry).
File key is stored in reiserfs specific portion of VFS inode.
>
> Do ReiserFS keys change or get reconstructed when tails are packed or
> when the tree gets re-balanced?
No. Once file is created - its key never changes. However, each position
in a file has its own key. For instance, 0-th byte of a file has key X,
Y, 1. 100-th byte of a file should be looked for with key X, Y, 101.
[X, Y] is the same for any part of file. This is what is extracted from
file name on lookup. Key of any other position within a file can be
easily calculated as we saw.
Or do keys remain consistent throughout
> a file's lifetime in the system?
>
Yes.
> Even the quickest response would be greatly appreciated.
>
> Thanks,
>
> Jenn
>
>
>
>
>
next prev parent reply other threads:[~2004-07-03 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-02 21:01 keys and inodes jenn sirp
2004-07-03 9:28 ` Vladimir V. Saveliev [this message]
2004-07-03 19:50 ` Marcelo Pacheco
2004-07-04 8:46 ` Vladimir V. Saveliev
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=40E67C3D.6070609@namesys.com \
--to=vs@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=sirp1@llnl.gov \
/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.