lkml.org 
[lkml]   [2001]   [Jan]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: Bugs in knfsd -- Problem re-exporting an NFS share
On Saturday December 30, ankry@green.mif.pg.gda.pl wrote:
>
> > On Friday December 29, Frank.Olsen@stonesoft.com wrote:
> > > Hi -- could you please CC me if you reply to this mail.
> > >
> > > A: /exports/A - Redhat 7.0
> > > B1/B2: mount /exports/A on /export/A from A - Redhat 6.2
> > > C: mount /exports/A on /mnt/A from B1 or B2 - Redhat 6.2
> > >
> > > I use knfsd/nfs-utils on each machine.
> > >
> > > bash# ls /mnt/A
> > > /mnt/A/A.txt: No such file or directory
> >
> > This is not a supported configuration. You cannot export NFS mounted
> > filesystems with NFS. The protocol does not cope, and it
> > implementation doesn't even try.
> > NFS is for export local filesystems only.
>
> As I understand problem is somewhere else.
> If this is intentionally unsupported configuration - OK. So why the error
> appears ? The directory should be empty then.
>
> If the configuration is unsupported at the moment and the A.txt file is
> located on A, some code that attempts to read re-exported files/directories
> should be turned off (eg. #if 0).
>
> If the A.txt file is local for B1/B2 hosts, it is (IMHO) an obvious bug.
> Sucgh a file should be hidden at the act of mounting. For both local and
> remote access.
>
> Neil, could you tell us where the A.txt file is *really* located ?

Well.... its a long story.
The interface between knfsd and filesystems is not (currently) a clean
one. The current interface to filesystems is dictated by the VFS
layer, and it works primarily in terms of names.
knfsd wants to work in terms of inode numbers (or something similar)
and there is no such interface.

knfsd does manage to do its job, but only by abusing part of the VFS
interface - the "iget" routine which calls s_op->read_inode.
iget is meant to be an private interface, only ever called by the
filesystem itself (typically in the lookup operation) but, for ext2 at
least, it works for knfsd, so knfsd uses it.

Basically, knfsd assumes that is a filesystem has "read_inode"
defined, then it can safely use iget.

This works for ext2, but not for nfs.

The nfs filesystem does define read_inode, but uses it quite
differently to ext2.
The net result is that when you try to map an inode number to an inode
using iget with ext2 it always works, but if you do it with nfs it only
works if the inode is already in the cache.

So, when you:
ls /mnt/A
from C, knfsd on B1 (or B2) tries to find the directory 'A' and
succeeds beause it is in cache. It does a readdir on this directory
and gets a list of files including "A.txt".
But when it tries to access A.txt, iget doesn't work for it, and it
cannot find it.

So A.txt is really on A, not on B1 or B2. But when you look at A.txt
from C through B1 or B2 you only get a blurred image. You can see
that it is there, but not what it is.

Does that help?

NeilBrown


>
> Regards
> Andrzej
>
> BTW. AFAIR, I observed similar behaviour (files are visible but
> inaccessible) while mounting a local filesystem at a busy directory
> (eg.: mount /dev/fd0 .;ls -l) even in 2.2...
>
> --
> =======================================================================
> Andrzej M. Krzysztofowicz ankry@mif.pg.gda.pl
> phone (48)(58) 347 14 61
> Faculty of Applied Phys. & Math., Technical University of Gdansk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:52    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site