From: Badari Pulavarty <pbadari@gmail.com>
To: Szabolcs Szakacsits <szaka@ntfs-3g.org>
Cc: shaggy@us.ibm.com, chris.mason@oracle.com,
ntfs-3g-devel@lists.sf.net,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [ANNOUNCEMENT] Linux POSIX file system test suite
Date: Mon, 07 Apr 2008 10:04:03 -0700 [thread overview]
Message-ID: <1207587843.31073.3.camel@badari-desktop> (raw)
In-Reply-To: <Pine.LNX.4.62.0804070207160.25240@tamago.serverit.net>
On Mon, 2008-04-07 at 02:34 +0300, Szabolcs Szakacsits wrote:
> On Thu, 3 Apr 2008, Badari Pulavarty wrote:
> > On Thu, 2008-04-03 at 00:29 +0300, Szabolcs Szakacsits wrote:
> >
> > > The default file system type is ext3 and it passes all tests.
> >
> > Hmm.. I ran it against ext2, ext3, jfs, btrfs. I don't see all "pass"
> > on ext3. What am I missing ?
>
> Your unique, consistently failing test cases for all file systems suggest
> that you have a buggy private kernel or some other individual issue in your
> test environment.
>
> You could use the -x debug shell option in the test scripts, rerun the
> failing ones and they will show why these test cases exactly fail.
I am running 2.6.25-rc8-mm1. What I noticed is, these failures happen
on ppc64. I ran the tests on x86-64 and ext2, ext3 passed all the tests.
> > btrfs seems to have little more failures.
>
> If you find the reason for the unexpected failures then the btrfs result
> will be quite good. Apparently it has only a few link, truncate, and unlink
> ctimes update problems. I think that's quite impressive in its state of
> development.
Yes. Indeed. btrfs has only these tests failing now (x86-64).
Failed Test Stat Wstat Total Fail Failed List of Failed
-------------------------------------------------------------------------------
/root/posix/tests/link/00.t 82 2 2.44% 56 63
/root/posix/tests/truncate/00.t 21 1 4.76% 15
/root/posix/tests/unlink/00.t 55 3 5.45% 17 22 53
Failed 3/184 test scripts, 98.37% okay. 6/1950 subtests failed, 99.69% okay.
Thanks,
Badari
next prev parent reply other threads:[~2008-04-07 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.62.0804022313390.664@tamago.serverit.net>
[not found] ` <20080402222344.GC23382@mail.oracle.com>
2008-04-03 4:12 ` [ANNOUNCEMENT] Linux POSIX file system test suite Szabolcs Szakacsits
[not found] ` <Pine.LNX.4.62.0804030705050.12223-03lVS0d9f+JcfUEgzQKStNHuzzzSOjJt@public.gmane.org>
2008-04-03 16:48 ` Joel Becker
2008-04-03 16:51 ` Amar S. Tumballi
[not found] ` <1207247251.30407.59.camel@dyn9047017100.beaverton.ibm.com>
[not found] ` <1207247251.30407.59.camel-Tq0y/nC7FQqofirLTBlK79w6IDGaBKkJqyM6JfAXOaQ@public.gmane.org>
2008-04-06 23:34 ` Szabolcs Szakacsits
2008-04-07 17:04 ` Badari Pulavarty [this message]
2008-04-08 15:37 ` ext4 not updating ctime on truncate ? Badari Pulavarty
2008-04-08 15:40 ` Eric Sandeen
[not found] ` <20080404003330.GW103491721@sgi.com>
[not found] ` <20080404065109.GW108924158@sgi.com>
[not found] ` <20080404065109.GW108924158-sJ/iWh9BUns@public.gmane.org>
2008-04-06 23:51 ` [ANNOUNCEMENT] Linux POSIX file system test suite Szabolcs Szakacsits
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=1207587843.31073.3.camel@badari-desktop \
--to=pbadari@gmail.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=ntfs-3g-devel@lists.sf.net \
--cc=shaggy@us.ibm.com \
--cc=szaka@ntfs-3g.org \
/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