Message-ID: <f6564100511181303g1507e3efyaa3e1e7ce2b09a28@mail.gmail.com>
Date: Fri, 18 Nov 2005 16:03:28 -0500
From: Rodrigo Amestica <ramestica AT gmail DOT com>
To: sam DOT robb AT timesys DOT com
Subject: Re: nfs problems
Cc: cygwin AT cygwin DOT com
In-Reply-To: <3D848382FB72E249812901444C6BDB1D022F54B0@exchange.timesys.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
References: <3D848382FB72E249812901444C6BDB1D022F54B0 AT exchange DOT timesys DOT com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id jAIL3aNE006074

On 11/14/05, Robb, Sam <sam DOT robb AT timesys DOT com> wrote:
> If you have any interest in working on
> resolving it, I'd be happy to hear whatever else you can
> discover about the problem.

Hi Sam,

what I found is the following: in a machine like mine, in which I have
2 physical disk drives, I get the following from the stat command:

/exports/c
Device: c98ce9bh/211340955d     Inode: 1407374883553285  Links: 9

/exports/d
Device: c847021ch/3360096796d   Inode: 1407374883553285  Links: 6

As you can see the device id is not the same but the inode it is!

Now, in libnfs/fhandle.c there is a function called pseudo_inode. For
cygwin this function creates a pseudo node id that enterely drops any
information about the device id. Therefore, what is happening is that
for a remote client /exports/c and /exports/d are mounted on the same
file system because fh_lookup has no means for resolving same inodes
on diffrent drives.

Inlined in the code of pseudo_inode there is a comment. The comment
seems to be valid for one single drive, but as soon as you have more
thatn 1 then the comment is, let's say, incorrect.

Perhaps, the author of that comment was very aware of this situation
and somewhere else annotated that this version of nfs-server is not
good for more than one drive.

Fixing the problem seems to be possible, but I just wonder about the
comment in pseudo_inode. Perhaps, there is something else I'm
overlooking.

thanks,
 Rodrigo

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/