From: Valerie Henson <val_henson@linux.intel.com>
To: Kalpak Shah <kalpak@linsyssoft.com>,
Karuna sagar K <karunasagark@gmail.com>, Amit Gud <gud@ksu.edu>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ChunkFS - measuring cross-chunk references
Date: Sun, 6 May 2007 18:09:10 -0700 [thread overview]
Message-ID: <20070507010910.GE12859@nifty> (raw)
In-Reply-To: <20070423205333.GZ5967@schatzie.adilger.int>
On Mon, Apr 23, 2007 at 02:53:33PM -0600, Andreas Dilger wrote:
>
> Also, is it considered a cross-chunk reference if a directory entry is
> referencing an inode in another group? Should there be a continuation
> inode in the local group, or is the directory entry itself enough?
(Sorry for the delay; just moved to Portland these last couple of
weeks.)
It is a cross-chunk reference - we can't calculate the correct link
count for the target file unless we have a quick way to get all the
directory entries pointing to an inode. My current scheme is to
create a continuation inode for the directory in the chunk containing
the inode (if the chunk containing the inode is full, create new
continuation inodes for both in a new chunk).
-VAL
next prev parent reply other threads:[~2007-05-07 1:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 20:35 ChunkFS - measuring cross-chunk references Karuna sagar K
2007-04-22 16:27 ` Amit Gud
2007-04-23 7:19 ` Karuna sagar K
2007-04-23 9:34 ` Kalpak Shah
2007-04-23 20:53 ` Andreas Dilger
2007-04-24 0:13 ` Theodore Tso
2007-04-24 1:02 ` Arjan van de Ven
2007-04-24 1:24 ` Amit Gud
2007-04-24 1:38 ` Amit Gud
2007-04-24 15:07 ` Theodore Tso
2007-04-25 0:17 ` Karuna sagar K
2007-04-25 0:20 ` Karuna sagar K
2007-04-25 10:23 ` Suparna Bhattacharya
2007-05-19 22:49 ` Karuna sagar K
2007-05-07 5:18 ` Valerie Henson
2007-05-07 1:09 ` Valerie Henson [this message]
2007-05-07 1:09 ` Valerie Henson
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=20070507010910.GE12859@nifty \
--to=val_henson@linux.intel.com \
--cc=gud@ksu.edu \
--cc=kalpak@linsyssoft.com \
--cc=karunasagark@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.