>From nfs-admin@lists.sourceforge.net Thu Feb 1 03:51:36 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 DAA11596
for <jareth@camelot.co.jp>; Thu, 1 Feb 2001 03:51:35 +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 14O2Bn-0005EI-00; Wed, 31 Jan 2001 10:41:07 -0800
Received: from h24-65-192-120.cg.shawcable.net ([24.65.192.120]
helo=webber.adilger.net)
by usw-sf-list1.sourceforge.net with esmtp (Exim 3.16 #1 (Debian))
id 14O2Be-00058T-00
for <nfs@lists.sourceforge.net>; Wed, 31 Jan 2001 10:40:58 -0800
Received: (from adilger@localhost)
by webber.adilger.net (8.11.2/8.11.1/Debian 8.11.0-6) id f0VIeSE02823;
Wed, 31 Jan 2001 11:40:28 -0700
From: Andreas Dilger <adilger@turbolinux.com>
Message-Id: <200101311840.f0VIeSE02823@webber.adilger.net>
Subject: Re: [NFS] Re: Is ext3 kernel nfsd friendly?
In-Reply-To: <14967.22523.912507.813535@notabene.cse.unsw.edu.au> from
Neil Brown
at "Jan 31, 2001 11:10:35 am"
To: ext3-users@redhat.com
CC: Augusto Cisar Radtke <radtke@conectiva.com>,
nfs@lists.sourceforge.net
X-Mailer: ELM [version 2.4ME+ PL66 (25)]
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:40:27 -0700 (MST)
Status: O
Content-Length: 1941
Lines: 44
Neil Brown writes:> 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:
Neil, I sent Stephen a patch to update ext3 with the same changes that
went into ext2 2.2.17 and 2.2.18, which include your NFS changes.
> 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.
The (2a - return bad_inode for deleted inodes) step unfortunately breaks
ext3 recovery. It is somewhat difficult to fix, because one of the ext3
recovery steps involves cleaning up "orphan" inodes - inodes which
were
previously unlinked but held open by a process, so not deleted. The
cleanup involves doing an iget() and iput() on the inode to re-delete it.
If iget() returns bad_inode, then the orphan cleanup step will fail.
I think I have fixed this, so I will submit it to Stephen.
> 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".
My patch should clean all of this up for ext3, assuming it all works in
ext2. It should make it into ext3-0.0.6.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/nfs
