public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: LTP-ML <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] Add new testcases for ext4 new features - V3
Date: Mon, 26 Oct 2009 16:28:22 +0900	[thread overview]
Message-ID: <4AE54F96.7060502@cn.fujitsu.com> (raw)
In-Reply-To: <4AE54BCA.7060104@cn.fujitsu.com>

Hi, Mr.Subrata

The patch that you made to fix the problem of ffsb was not merged into
this patch. So if you want to run this testcases, you must applied your
patch before compiling the testcases.

Regards.
Miao

on 2009-10-26 16:12, Miao Xie wrote:
> This is the patch of testcases for the ext4 new features test.
> It contains multi-block alloc/delayed alloc test, inode version test,
> journal checksumming test, nanosec timestamps test, online defrag test,
> persist prealloc test, subdirectory limit test and uninit groups test
> of ext4.
> 
> In this test suite, there is two FAIL in the subdirectory limit test.
> It is because we cann't create more than 32000 subdirectory when block
> size is small, such as 1024, and the name of every subdirectory is very
> long, such as every name is 255 bytes. I think it is the bug of the ext4.
> 
> Note: Your MUST run configure in the directory
>     testcases/kernel/fs/ext4-new-features
>       to config the tool of ffsb, and specify a partition to be used for 
> test
>       before compiling the tool. The data on the specified partition 
> would be
>       DESTROYED.
> 
> Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>




------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-10-26  7:28 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-26  7:12 [LTP] [PATCH] Add new testcases for ext4 new features - V3 Miao Xie
2009-10-26  7:28 ` Miao Xie [this message]
2009-10-26  8:29   ` Subrata Modak
2009-10-26 13:26   ` Subrata Modak
2009-10-26 13:26 ` Subrata Modak
2009-10-26 22:15   ` Andreas Dilger
2009-10-27 13:35     ` Subrata Modak
2009-10-29 18:31       ` Subrata Modak
2009-11-02 13:59         ` Subrata Modak
2009-11-26 12:02           ` Miao Xie
2009-12-03 15:11             ` Subrata Modak
2009-12-04 10:04               ` Miao Xie
2009-12-07 11:53                 ` Subrata Modak
2009-12-08  5:59                   ` Miao Xie
2009-12-09 12:13                     ` Subrata Modak
2009-11-30  3:28           ` Miao Xie
2009-11-30  9:39             ` Miao Xie
2009-11-30 10:01               ` Garrett Cooper
2009-11-03  2:47         ` Miao Xie
2009-11-09 17:39           ` Subrata Modak
  -- strict thread matches above, loose matches on Subject: below --
2009-12-07 13:29 naresh kamboju

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=4AE54F96.7060502@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.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