All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Andre Tanner <mat@brain-dump.org>
To: Szabolcs Szakacsits <szaka@ntfs-3g.org>
Cc: ntfs-3g-devel@lists.sf.net, linux-fsdevel@vger.kernel.org,
	fuse-devel@lists.sourceforge.net,
	ext2-devel@lists.sourceforge.net, zfs-fuse@googlegroups.com,
	Jean-Pierre ANDRE <jean-pierre.andre@wanadoo.fr>
Subject: Re: [ANNOUNCEMENT] Linux POSIX file system test suite
Date: Fri, 4 Apr 2008 22:40:43 +0200	[thread overview]
Message-ID: <20080404204043.GA1818@debbook.brain-dump.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0804022313390.664@tamago.serverit.net>

On Thu, Apr 03, 2008 at 12:29:47AM +0300, Szabolcs Szakacsits wrote:
> 
> Hello file system developers,
> 
> There are several POSIX file system test suites: closed source, commercial, 
> one which needs reading 174 pages installation guide, etc. Because of these 
> frustrations when Pawel Jakub Dawidek ported ZFS to FreeBSD, he also wrote 
> such a test suite quickly.
> 
> Last year the NTFS-3G team ported it to Linux/ext3 and Linux/NTFS-3G to 
> validate Jean-Pierre Andre's full file permissions and ownership support 
> for NTFS-3G. We sent our patches to Pawel for integration but this doesn't 
> seem to happen him (he didn't see problems but is busy).
> 
> Since this topic regularly appears on several lists, we are also often 
> asked about it and NTFS-3G does need it to be maintained, hence we decided 
> to release it and if nobody else would like to maintain it then we will do 
> so.

Hi,

Thanks for the release. 

I have a general question regarding FUSE. Why do all the tests pass on a
regular ext3 file system while there are quite a lot of errors (~80%
success) when run on top of the fuse example file system as found in the
fuse tarball? I thought the fuse filesystem just passes every access to 
the underlying file system. So what's causing the failures? Or am i doing
something wrong?

Thanks,
Marc

-- 
 Marc Andre Tanner >< http://www.brain-dump.org/ >< GPG key: CF7D56C0

      parent reply	other threads:[~2008-04-04 20:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-02 21:29 [ANNOUNCEMENT] Linux POSIX file system test suite Szabolcs Szakacsits
2008-04-02 22:23 ` Joel Becker
2008-04-03  4:12   ` 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
2008-04-03 18:27 ` Badari Pulavarty
     [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
2008-04-04  0:33 ` [ANNOUNCEMENT] Linux POSIX file system test suite David Chinner
2008-04-04  6:51   ` David Chinner
2008-04-04 15:48     ` Christoph Hellwig
2008-04-07  2:07       ` David Chinner
     [not found]     ` <20080404065109.GW108924158-sJ/iWh9BUns@public.gmane.org>
2008-04-06 23:51       ` Szabolcs Szakacsits
2008-04-04 20:40 ` Marc Andre Tanner [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=20080404204043.GA1818@debbook.brain-dump.org \
    --to=mat@brain-dump.org \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=jean-pierre.andre@wanadoo.fr \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=ntfs-3g-devel@lists.sf.net \
    --cc=szaka@ntfs-3g.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.