From: "Karuna sagar K" <karunasagark@gmail.com>
To: "Theodore Tso" <tytso@mit.edu>,
"Kalpak Shah" <kalpak@linsyssoft.com>, "Amit Gud" <gud@ksu.edu>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: ChunkFS - measuring cross-chunk references
Date: Wed, 25 Apr 2007 05:50:55 +0530 [thread overview]
Message-ID: <2e4afe1e0704241720q3eb54e24gcd10b2026759333@mail.gmail.com> (raw)
In-Reply-To: <2e4afe1e0704241717l6e6ec72by898727b5973c221@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2053 bytes --]
On 4/24/07, Theodore Tso <tytso@mit.edu> wrote:
> On Mon, Apr 23, 2007 at 02:53:33PM -0600, Andreas Dilger wrote:
.........
> It would also be good to distinguish between directories referencing
> files in another chunk, and directories referencing subdirectories in
> another chunk (which would be simpler to handle, given the topological
> restrictions on directories, as compared to files and hard links).
>
Modified the tool to distinguish between
1. cross references between directories and files
2. cross references between directories and sub directories
3. cross references within a file (due to huge file size)
Below is the result from / partition of ext3 file system:
Number of files = 221794
Number of directories = 24457
Total size = 8193116 KB
Total data stored = 7187392 KB
Size of block groups = 131072 KB
Number of inodes per block group = 16288
No. of cross references between directories and sub-directories = 7791
No. of cross references between directories and file = 657
Total no. of cross references = 62018 (dir ref = 8448, file ref = 53570)
Thanks for the suggestions.
> There may also be special things we will need to do to handle
> scenarios such as BackupPC, where if it looks like a directory
> contains a huge number of hard links to a particular chunk, we'll need
> to make sure that directory is either created in the right chunk
> (possibly with hints from the application) or migrated to the right
> chunk (but this might cause the inode number of the directory to
> change --- maybe we allow this as long as the directory has never been
> stat'ed, so that the inode number has never been observed).
>
> The other thing which we should consider is that chunkfs really
> requires a 64-bit inode number space, which means either we only allow
> it on 64-bit systems, or we need to consider a migration so that even
> on 32-bit platforms, stat() functions like stat64(), insofar that it
> uses a stat structure which returns a 64-bit ino_t.
>
> - Ted
>
Thanks,
Karuna
[-- Attachment #2: cref.tar.bz2 --]
[-- Type: application/x-bzip2, Size: 2295 bytes --]
next prev parent reply other threads:[~2007-04-25 0:20 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 [this message]
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
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=2e4afe1e0704241720q3eb54e24gcd10b2026759333@mail.gmail.com \
--to=karunasagark@gmail.com \
--cc=gud@ksu.edu \
--cc=kalpak@linsyssoft.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).