public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Szabolcs Szakacsits <szaka@ntfs-3g.com>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: ntfs-3g-devel@lists.sourceforge.net,
	linux-fsdevel@vger.kernel.org, fuse-devel@lists.sourceforge.net,
	zfs-fuse@googlegroups.com, Marc Andre Tanner <mat@brain-dump.org>,
	Jean-Pierre ANDRE <jean-pierre.andre@wanadoo.fr>,
	linux-ext4@vger.kernel.org
Subject: Re: [ANNOUNCEMENT] Linux POSIX file system test suite
Date: Thu, 3 Apr 2008 07:12:12 +0300 (EEST)	[thread overview]
Message-ID: <Pine.LNX.4.62.0804030705050.12223@tamago.serverit.net> (raw)
In-Reply-To: <20080402222344.GC23382@mail.oracle.com>


On Wed, 2 Apr 2008, Joel Becker wrote:
> On Thu, Apr 03, 2008 at 12:29:47AM +0300, Szabolcs Szakacsits wrote:
> > The test suite mostly checks POSIX compliance and works for FreeBSD, 
> > Solaris, and Linux with UFS, ZFS, ext3, and NTFS-3G file systems. The list 
> > of system calls tested is: chmod, chown, link, mkdir, mkfifo, open, rename, 
> > rmdir, symlink, truncate, unlink. There are currently 1950 regression 
> > tests.
> <snip> 
> > Availability:
> > 
> > 	http://ntfs3g.org/sw/qa/pjd-fstest-20080402.tgz
> 
> 	Very interesting.  ocfs2, running as 'ext3' mode, gets:
>
> Failed 9/184 test scripts, 95.11% okay. 32/1950 subtests failed, 98.36% okay.

That's not bad as a start and it doesn't necessarily mean that there is 
anything wrong with ocfs2. There are many cases when SuS says that the 
behavior can be implementation specific.

But we did find that following ext3 as close as possible will reduce the 
number of bug reports. We started from "574/1950 subtests failed, 70.56% 
okay."

Regards,
	    Szaka

--
NTFS-3G:  http://ntfs-3g.org

       reply	other threads:[~2008-04-03  4:12 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   ` Szabolcs Szakacsits [this message]
     [not found]     ` <Pine.LNX.4.62.0804030705050.12223-03lVS0d9f+JcfUEgzQKStNHuzzzSOjJt@public.gmane.org>
2008-04-03 16:48       ` [ANNOUNCEMENT] Linux POSIX file system test suite 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
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=Pine.LNX.4.62.0804030705050.12223@tamago.serverit.net \
    --to=szaka@ntfs-3g.com \
    --cc=Joel.Becker@oracle.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=jean-pierre.andre@wanadoo.fr \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mat@brain-dump.org \
    --cc=ntfs-3g-devel@lists.sourceforge.net \
    --cc=zfs-fuse@googlegroups.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