On 4/25/07, Suparna Bhattacharya <[EMAIL PROTECTED]> wrote:
On Wed, Apr 25, 2007 at 05:50:55AM +0530, Karuna sagar K wrote:
One more set of numbers to calculate would be an estimate of cross-references
across chunks of block groups -- 1 (=128MB), 2 (=256MB), 4 (=512MB), 8(=1GB)
as sug
On 4/25/07, Suparna Bhattacharya [EMAIL PROTECTED] wrote:
On Wed, Apr 25, 2007 at 05:50:55AM +0530, Karuna sagar K wrote:
One more set of numbers to calculate would be an estimate of cross-references
across chunks of block groups -- 1 (=128MB), 2 (=256MB), 4 (=512MB), 8(=1GB)
as suggested
On 4/23/07, Avishay Traeger <[EMAIL PROTECTED]> wrote:
On Mon, 2007-04-23 at 02:16 +0530, Karuna sagar K wrote:
You may want to check out the paper "EXPLODE: A Lightweight, General
System for Finding Serious Storage System Errors" from OSDI 2006 (if you
haven't already). The
On 4/23/07, Avishay Traeger [EMAIL PROTECTED] wrote:
On Mon, 2007-04-23 at 02:16 +0530, Karuna sagar K wrote:
snip
You may want to check out the paper EXPLODE: A Lightweight, General
System for Finding Serious Storage System Errors from OSDI 2006 (if you
haven't already). The idea sounds very
On 4/24/07, Theodore Tso <[EMAIL PROTECTED]> 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
On 4/24/07, Theodore Tso [EMAIL PROTECTED] 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
On 4/23/07, Kalpak Shah <[EMAIL PROTECTED]> wrote:
On Mon, 2007-04-23 at 02:16 +0530, Karuna sagar K wrote:
.
The file system is looked upon as a set of blocks (more precisely
metadata blocks). We randomly choose from this set of blocks to
corrupt. Hence we would be able to ov
; wrote:
Karuna sagar K wrote:
> Hi,
>
> The attached code contains program to estimate the cross-chunk
> references for ChunkFS file system (idea from Valh). Below are the
> results:
>
Nice to see some numbers! But would be really nice to know:
- what the chunk size is
- h
sagar K wrote:
Hi,
The attached code contains program to estimate the cross-chunk
references for ChunkFS file system (idea from Valh). Below are the
results:
Nice to see some numbers! But would be really nice to know:
- what the chunk size is
- how the files were created or, more vaguely, how
On 4/23/07, Kalpak Shah [EMAIL PROTECTED] wrote:
On Mon, 2007-04-23 at 02:16 +0530, Karuna sagar K wrote:
.
The file system is looked upon as a set of blocks (more precisely
metadata blocks). We randomly choose from this set of blocks to
corrupt. Hence we would be able to overcome
Hi,
For some time I had been working on this file system test framework.
Now I have a implementation for the same and below is the explanation.
Any comments are welcome.
Introduction:
The testing tools and benchmarks available around do not take into
account the repair and recovery aspects of
Hi,
The attached code contains program to estimate the cross-chunk
references for ChunkFS file system (idea from Valh). Below are the
results:
test on ext3, / partition-1 on 27 March 2007
Number of files = 217806
Number of directories = 24295
Total size = 8193116 KB
Total data stored = 7557892
Hi,
The attached code contains program to estimate the cross-chunk
references for ChunkFS file system (idea from Valh). Below are the
results:
test on ext3, / partition-1 on 27 March 2007
Number of files = 217806
Number of directories = 24295
Total size = 8193116 KB
Total data stored = 7557892
Hi,
For some time I had been working on this file system test framework.
Now I have a implementation for the same and below is the explanation.
Any comments are welcome.
Introduction:
The testing tools and benchmarks available around do not take into
account the repair and recovery aspects of
Hi,
I am working on a testing framework for file systems focusing on
repair and recovery areas. Right now, I have been timing fsck and
trying to determine the effectiveness of fsck. The idea that I have is
below.
In abstract terms, I create a file system (ideal state), corrupt it,
run fsck on
Hi,
I am working on a testing framework for file systems focusing on
repair and recovery areas. Right now, I have been timing fsck and
trying to determine the effectiveness of fsck. The idea that I have is
below.
In abstract terms, I create a file system (ideal state), corrupt it,
run fsck on
16 matches
Mail list logo
