[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

(no subject)



>From nfs-admin lists sourceforge net  Wed Jan 31 09:21:55 2001
>Return-Path: <nfs-admin lists sourceforge net>
Received: from usw-sf-list1.sourceforge.net (usw-outbound.sourceforge.net [216.136.171.194])
	by gateway.camelot.jp (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id JAA03106
	for <jareth camelot co jp>; Wed, 31 Jan 2001 09:21:53 +0900
X-Authentication-Warning: gateway.camelot.jp: Host usw-outbound.sourceforge.net [216.136.171.194] claimed to be usw-sf-list1.sourceforge.net
Received: from localhost ([127.0.0.1] helo=usw-sf-list1.sourceforge.net)
	by usw-sf-list1.sourceforge.net with esmtp (Exim 3.16 #1 (Debian))
	id 14Nktf-0003bz-00; Tue, 30 Jan 2001 16:13:15 -0800
Received: from note.orchestra.cse.unsw.edu.au ([129.94.242.29])
	by usw-sf-list1.sourceforge.net with smtp (Exim 3.16 #1 (Debian))
	id 14Nkrh-0003Pa-00
	for <nfs lists sourceforge net>; Tue, 30 Jan 2001 16:11:13 -0800
Received: From
	notabene.cse.unsw.edu.au ([129.94.211.34] == elephant.orchestra.cse.unsw.EDU.AU)
	(for <radtke conectiva com>) (for <ext3-users redhat com>)
	(for <nfs lists sourceforge net>) By note With Smtp ;
	Wed, 31 Jan 2001 11:10:36 +1100 
Received: from neilb by notabene.cse.unsw.edu.au with local (Exim 3.12 #1 (Debian))
	id 14Nkr6-0004v9-00; Wed, 31 Jan 2001 11:10:36 +1100
From: Neil Brown <neilb cse unsw edu au>
To: "=?iso-8859-1?Q?Augusto_C=E9sar_Radtke?=" <radtke conectiva com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14967 22523 912507 813535 notabene cse unsw edu au>
Cc: ext3-users redhat com, nfs lists sourceforge net
Subject: Re: [NFS] Re: Is ext3 kernel nfsd friendly?
In-Reply-To: message from =?iso-8859-1?Q?Augusto_C=E9sar_Radtke?= on Monday January 29
References: <20010129095316 D11607 redhat com>
	<200101291849 f0TInOk15913 webber adilger net>
	<20010129174821 A4340 conectiva com>
X-Mailer: VM 6.72 under Emacs 20.7.2
X-face: 	[Gw_3E*Gng}4rRrKRYotwlE?.2|**#s9D<ml'fY1Vw+ XfR[fRCsUoP?K6bt3YD\ui5Fh?f
	LONpR';(ql)VM_TQ/<l_^D3~B:z$\YC7gUCuC=sYm/80G=$tt"98mr8(l))QzVKCk$6~gldn~*FK9x
	8`;pM{3S8679sP+MbP,72<3_PIH-$I&iaiIb|hV1d%cYg))BmI)AZ
Sender: nfs-admin lists sourceforge net
Errors-To: nfs-admin lists sourceforge net
X-BeenThere: nfs lists sourceforge net
X-Mailman-Version: 2.0
Precedence: bulk
List-Help: <mailto:nfs-request lists sourceforge net?subject=help>
List-Post: <mailto:nfs lists sourceforge net>
List-Subscribe: <http://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request lists sourceforge net?subject=subscribe>
List-Id: Discussion of NFS under Linux development,
	interoperability,
	and testing. <nfs.lists.sourceforge.net>
List-Unsubscribe: <http://lists.sourceforge.net/lists/listinfo/nfs>,
	<mailto:nfs-request lists sourceforge net?subject=unsubscribe>
List-Archive: <http://lists.sourceforge.net/archives//nfs/>
Date: Wed, 31 Jan 2001 11:10:35 +1100 (EST)
Status: O
Content-Length: 1608
Lines: 41

On Monday January 29, radtke conectiva com wrote:
> Andreas Dilger wrote:
> 
> > I've been using knfsd on ext3 (2.2.17 kernel) for quite some time without
> > problems.  However, this is the older NFS code, and not the major changes
> > that went into NFS for 2.2.18, so YMMV.
> 
> I'm using NFS with 2.2.19pre7 + ext3 without any problems yet, quite stable.

Ofcourse, "apparently stable" is quite different from "absolutely
reliable"...

I haven't looked at ext3 or played with it but in order for a
filesystem to work with knfsd (in it's current form) it must:

  Support the read_inode super_operation and 
   1/ recognise if the inode number refers to a currently active inode
       or not
   2a/ if not, must return an is_bad_inode() inode.
   2b/ if so must  provide a completely filled-in inode (nfs doesn't for example.
                ext2 does, ext3 almost certainly does).

   3/ The "delete_inode" super_operation must cope gracefully with
      being given an is_bad_inode.

   4/ Should keep a "generation" number in the inode-on-disk, should
      assigned a "new" value to this when the inode is allocated, and
      should store this value in the i_generation field of the "struct
      inode".


Before I started looking at knfsd, ext2 did not do 1 (or 2a) or 3, and
I think there was something funny with 4, but I'm not sure.
If ext3 does all these, it should work fine.  If not, I suspect they
would be fairly straight forward to add.

NeilBrown

_______________________________________________
NFS maillist  -  NFS lists sourceforge net
http://lists.sourceforge.net/lists/listinfo/nfs





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]