From: Michal Simek <michal.simek@petalogix.com>
To: Jyoti <jyotiv@linux.vnet.ibm.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Submitting patch
Date: Sat, 25 Jul 2009 08:15:34 +0200 [thread overview]
Message-ID: <4A6AA306.3060107@petalogix.com> (raw)
In-Reply-To: <20090724110008.GA11878@linux.vnet.ibm.com>
Please fix coding style. Use tab instead of space for indentation.
Thanks,
Michal
> PATCH IS CREATED FOR ltp-full-20090630.
>
> I am submitting a patch to kernel/fs/fs_di
>
> In this file data integity is performed by creating the file at
> different directory depth and then by comparing with original file.
>
> To this I have added one more approach to perform integrity test.
> 1. Creating two fragmented files each of size DiskSize/2.
> 2. Then comapring against the original file.
> 3. If not equal test case fails.
>
> My ultimate goal in creating fragmented files is that,
> 1. It creates many extents (fragments for each file)
> 2. FS code may behave wrong at corner cases which may come into picture
> after many extents gets added to the file.
> 3. Data corruption chances are there
> i. when file metadata updation is not proper (corner cases when fragments are more)
> ii.If write and read is not matching (write operation might have updated the block
> number some where and read may skip that block in some corner cases)
> 4. In reality fragments can occur only after much usage of the disk(create/delete file)
> 5. This is good test case for bigger size disk.(it can create more extents)
>
>
> To: ltp-list@lists.sourceforge.net
> Cc: subrata@linux.vnet.ibm.com
> Bcc: Jyoti <jyotiv@linux.vnet.ibm.com>
> Subject: Submitting patch
> Reply-To: Jyoti <jyotiv@linux.vnet.ibm.com>
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> ------------------------------------------------------------------------
>
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
--
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-07-25 6:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 11:00 [LTP] Submitting patch jyotiv
2009-07-25 6:15 ` Michal Simek [this message]
2009-07-25 16:48 ` Garrett Cooper
2009-07-27 9:29 ` Michal Simek
2009-07-30 18:29 ` Subrata Modak
2009-08-03 10:47 ` Cyril Hrubis
[not found] ` <4A76EA47.7070209@petalogix.com>
2009-08-03 13:54 ` Cyril Hrubis
[not found] ` <4A76F856.6030307@petalogix.com>
[not found] ` <364299f40908030944n74d79509r716dcbcc8875677b@mail.gmail.com>
[not found] ` <4A77F359.40901@petalogix.com>
2009-08-04 10:11 ` Subrata Modak
2009-07-30 18:50 ` Garrett Cooper
-- strict thread matches above, loose matches on Subject: below --
2009-08-05 9:00 Jyoti
2009-08-05 9:10 ` Subrata Modak
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=4A6AA306.3060107@petalogix.com \
--to=michal.simek@petalogix.com \
--cc=jyotiv@linux.vnet.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
/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