public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Akira Fujita <a-fujita@rs.jp.nec.com>
To: subrata@linux.vnet.ibm.com
Cc: Linux Test Project <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] ffsb failures running ltp-ext4 new features test on	SLES11sp1 PPC
Date: Tue, 22 Jun 2010 17:22:46 +0900	[thread overview]
Message-ID: <4C2072D6.7010008@rs.jp.nec.com> (raw)
In-Reply-To: <1277140788.4881.0.camel@subratamodak.linux.ibm.com>

 > Is there any patch you would like to Propose ?

I don't have a patch for this.
I am glad if someone takes care of this, though.

Regards,
Akira Fujita

(2010/06/22 2:19), Subrata Modak wrote:
> Is there any patch you would like to Propose ?
>
> Regards--
> Subrata
>
> On Mon, 2010-06-21 at 17:25 +0900, Akira Fujita wrote:
>> Hi Subrata,
>>
>>> Akira,
>>>
>>> Probably we need to change the tests conditions to restrict not to cross
>>> the size of partition. We can handle the tests better i think. I am not
>>> sure if the last commit is playing foul with the tests:
>>>
>>> commit 7f20a3add6c7f2166dbab5a712713ae8b5943448
>>> Author: Subrata Modak<subratamodak@subratamodak.linux.ibm.com>
>>> Date:   Wed Jun 2 18:16:46 2010 +0530
>>
>> Yes, we should check ext4 partition size and configure fssb write size
>> before testing.
>>
>> AFAIK, ext4-subdir-limit test does not depend on partition size,
>> and over 32000 directory feature is not supported in case
>> 1KB block size and long directory name.
>> So I think my fix (just skip invalid test case) is okay.
>>
>> Reference: linux/Documentation/filesystems/ext4.txt
>>
>> * lift 32000 subdirectory limit imposed by i_links_count[1]
>> [1] Filesystems with a block size of 1k may see a limit imposed by the
>> directory hash tree having a maximum depth of two.
>>
>> Regards,
>> Akira Fujita
>>
>> (2010/06/19 2:30), Subrata Modak wrote:
>>> Yes, i find many failures in the tests including dumping of BINARY
>>> characters on this screen. Following are excerpts of the failures:
>>>
>>> ext4-journal-checksum    7  TFAIL  :  ffsb returned failure
>>> ext4-journal-checksum    0  TINFO  :  journal mode: ordered, commit
>>> interval: 1,
>>> ext4-journal-checksum    8  TPASS  :  ext4 journal checksum test pass
>>> ext4-journal-checksum    0  TINFO  :  journal mode: journal, commit
>>> interval: 1,
>>> ext4-journal-checksum    9  TPASS  :  ext4 journal checksum test pass
>>> ext4-journal-checksum    0  TINFO  :  journal mode: writeback, commit
>>> interval: 100,
>>> write: No space left on device
>>> write: No space left on device
>>> write: No space left on device
>>> \x11]�0��������\x11]�@\x11]����O\x10�����0\x01\x01�碘
>>> �p\x02A��,�\x11]�\x13\x11]�\x13\x11]�\x13\x11]�\x13\x11]�\x13\x11]�\x13\x11]�\x13\x11]�\x14\x11]\x7fP\x17\x11]�p��������\x11]����N\x10�����0\x01\x01�����p\x02A��$�\x11]��\x11\x11]����������\x11]�������0�p\x02A��$�\x11]��\x12\x11]����������\x11]������0�p\x01w�\x11]}���������\x11]~\x11]\x7fP��\x10�����0\x01\x01�マ��p\x02A��,�\x11]\x7f�\x11]\x7f�\x11]\x7f�\x11]\x7f���O\x11]\x7f�\x11]\x7f�\x11]\x7f�\x11]}\x10\x16\x11]�0��������\x11]�@\x11]����O\x10�����0\x01\x01�碘�p\x02A��,�\x11]�\x13\x11]�\x13\x11]�\x13\x11]�\x13\x11]�\x13\x11]�\x13\x11]�\x13\x11]�\x14\x11]\x7fP\x17\x11]�p��������\x11]����N\x10�����0\x01\x01�����p\x02A��$�\x11]��\x11\x11]����������\x11]�������0�p\x02A��$�\x11]��\x12\x11]����������\x11]������0�p\x01w�
>>>
>>> Akira,
>>>
>>> Probably we need to change the tests conditions to restrict not to cross
>>> the size of partition. We can handle the tests better i think. I am not
>>> sure if the last commit is playing foul with the tests:
>>>
>>> commit 7f20a3add6c7f2166dbab5a712713ae8b5943448
>>> Author: Subrata Modak<subratamodak@subratamodak.linux.ibm.com>
>>> Date:   Wed Jun 2 18:16:46 2010 +0530
>>>
>>> Regards--
>>> Subrata
>>>
>>> On Fri, 2010-06-18 at 11:39 +0530, Subrata Modak wrote:
>>>> Hi Lucio,
>>>>
>>>> Till now i did not detect any failure for the sdb2:
>>>>
>>>> ext4-delalloc-mballoc    0  TINFO  :  isDelalloc: delalloc, isDirectIO:
>>>> 0, Blocksize: 1024, isAuto_da_alloc: auto_da_alloc=1
>>>> ext4-delalloc-mballoc    1  TPASS  :  delalloc/mballoc test pass
>>>> ext4-delalloc-mballoc    0  TINFO  :  isDelalloc: delalloc, isDirectIO:
>>>> 0, Blocksize: 1024, isAuto_da_alloc: noauto_da_alloc
>>>> ext4-delalloc-mballoc    2  TPASS  :  delalloc/mballoc test pass
>>>> ext4-delalloc-mballoc    0  TINFO  :  isDelalloc: nodelalloc,
>>>> isDirectIO: 0, Blocksize: 1024, isAuto_da_alloc: auto_da_alloc=1
>>>> ext4-delalloc-mballoc    3  TPASS  :  delalloc/mballoc test pass
>>>> ext4-delalloc-mballoc    0  TINFO  :  isDelalloc: nodelalloc,
>>>> isDirectIO: 0, Blocksize: 1024, isAuto_da_alloc: noauto_da_alloc
>>>> ext4-delalloc-mballoc    4  TPASS  :  delalloc/mballoc test pass
>>>> ext4-delalloc-mballoc    0  TINFO  :  isDelalloc: delalloc, isDirectIO:
>>>> 1, Blocksize: 1024, isAuto_da_alloc: auto_da_alloc=1
>>>> ext4-delalloc-mballoc    5  TPASS  :  delalloc/mballoc test pass
>>>> ext4-delalloc-mballoc    0  TINFO  :  isDelalloc: delalloc, isDirectIO:
>>>> 1, Blocksize: 1024, isAuto_da_alloc: noauto_da_alloc
>>>> ext4-delalloc-mballoc    6  TPASS  :  delalloc/mballoc test pass
>>>> ext4-delalloc-mballoc    0  TINFO  :  isDelalloc: nodelalloc,
>>>> isDirectIO: 1, Blocksize: 1024, isAuto_da_alloc: auto_da_alloc=1
>>>> ext4-delalloc-mballoc    7  TPASS  :  delalloc/mballoc test pass
>>>> ext4-delalloc-mballoc    0  TINFO  :  isDelalloc: nodelalloc,
>>>> isDirectIO: 1, Blocksize: 1024, isAuto_da_alloc: noauto_da_alloc
>>>> ext4-delalloc-mballoc    8  TPASS  :  delalloc/mballoc test pass
>>>> ext4-delalloc-mballoc    0  TINFO  :  isDelalloc: delalloc, isDirectIO:
>>>> 0, Blocksize: 4096, isAuto_da_alloc: auto_da_alloc=1
>>>>
>>>> I will continue to run the tests and update you again.
>>>>
>>>> Regards--
>>>> Subrata
>>>>
>>>> On Thu, 2010-06-17 at 18:12 -0300, Lucio Correia wrote:
>>>>> Hi Akira,
>>>>>
>>>>> I've found some failures running ext4-newfeat with SLES11sp1 on POWER6.
>>>>> Have you seen that before?
>>>>>
>>>>>
>>>>>
>>>>> ext4-delalloc-mballoc    0  TINFO  :  isDelalloc: delalloc, isDirectIO:
>>>>> 0,
>>>>> Blocksize: 4096, isAuto_da_alloc: auto_da_alloc=1
>>>>> write: No space left on device
>>>>> ext4-delalloc-mballoc    9  TFAIL  :  ffsb returned failure
>>>>>
>>>>> ext4-journal-checksum    0  TINFO  :  journal mode: writeback, commit interval:
>>>>> 1,
>>>>> write: No space left on device
>>>>> write: No space left on device
>>>>> write: No space left on device
>>>>> write: No space left on device
>>>>> ext4-journal-checksum    1  TFAIL  :  ffsb returned failure
>>>>>
>>>>> ext4-journal-checksum    0  TINFO  :  journal mode: writeback, commit interval:
>>>>> 100,
>>>>> write: No space left on device
>>>>> write: No space left on device
>>>>> write: No space left on device
>>>>> ext4-journal-checksum    4  TFAIL  :  ffsb returned failure
>>>>>
>>>>> ext4-journal-checksum    0  TINFO  :  journal mode: writeback, commit interval:
>>>>> 1,
>>>>> write: Success
>>>>> write: Success
>>>>> write: No space left on device
>>>>> ext4-journal-checksum    7  TFAIL  :  ffsb returned failure
>>>>>
>>>>> ext4-journal-checksum    0  TINFO  :  journal mode: writeback, commit interval:
>>>>> 100,
>>>>> write: No space left on device
>>>>> write: No space left on device
>>>>> ext4-journal-checksum   10  TFAIL  :  ffsb returned failure
>>>>>
>>>>> and so on 13, 16, 19, 22, 25, 28, 31, 34.
>>>>> ext4-delalloc-mballoc    0  TINFO  :  isDelalloc: delalloc, isDirectIO:
>>>>> 0,
>>>>> Blocksize: 4096, isAuto_da_alloc: auto_da_alloc=1
>>>>> write: No space left on device
>>>>> ext4-delalloc-mballoc    9  TFAIL  :  ffsb returned failure
>>>>>
>>>>> ext4-journal-checksum    0  TINFO  :  journal mode: writeback, commit interval:
>>>>> 1,
>>>>> write: No space left on device
>>>>> write: No space left on device
>>>>> write: No space left on device
>>>>> write: No space left on device
>>>>> ext4-journal-checksum    1  TFAIL  :  ffsb returned failure
>>>>>
>>>>> ext4-journal-checksum    0  TINFO  :  journal mode: writeback, commit interval:
>>>>> 100,
>>>>> write: No space left on device
>>>>> write: No space left on device
>>>>> write: No space left on device
>>>>> ext4-journal-checksum    4  TFAIL  :  ffsb returned failure
>>>>>
>>>>> ext4-journal-checksum    0  TINFO  :  journal mode: writeback, commit interval:
>>>>> 1,
>>>>> write: Success
>>>>> write: Success
>>>>> write: No space left on device
>>>>> ext4-journal-checksum    7  TFAIL  :  ffsb returned failure
>>>>>
>>>>> ext4-journal-checksum    0  TINFO  :  journal mode: writeback, commit interval:
>>>>> 100,
>>>>> write: No space left on device
>>>>> write: No space left on device
>>>>> ext4-journal-checksum   10  TFAIL  :  ffsb returned failure
>>>>>
>>>>> and so on 13, 16, 19, 22, 25, 28, 31, 34.
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>>
>>>>>
>>>>> Lucio Correia
>>>>> --------------
>>>>> Software Engineer
>>>>> IBM LTC
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate
>>>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
>>>>> lucky parental unit.  See the prize list and enter to win:
>>>>> http://p.sf.net/sfu/thinkgeek-promo
>>>>> _______________________________________________
>>>>> Ltp-list mailing list
>>>>> Ltp-list@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/ltp-list
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> ThinkGeek and WIRED's GeekDad team up for the Ultimate
>>>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
>>>> lucky parental unit.  See the prize list and enter to win:
>>>> http://p.sf.net/sfu/thinkgeek-promo
>>>> _______________________________________________
>>>> Ltp-list mailing list
>>>> Ltp-list@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/ltp-list
>>>
>>>
>>
>
>

------------------------------------------------------------------------------
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      reply	other threads:[~2010-06-22  8:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17 21:12 [LTP] ffsb failures running ltp-ext4 new features test on SLES11sp1 PPC Lucio Correia
2010-06-18  2:49 ` Akira Fujita
2010-06-18  6:09 ` Subrata Modak
2010-06-18 17:30   ` Subrata Modak
2010-06-21  8:25     ` Akira Fujita
2010-06-21 17:19       ` Subrata Modak
2010-06-22  8:22         ` Akira Fujita [this message]

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=4C2072D6.7010008@rs.jp.nec.com \
    --to=a-fujita@rs.jp.nec.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=subrata@linux.vnet.ibm.com \
    /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