On Fri, Oct 06, 2006 at 07:19:19PM -0500, Sergio Mendoza wrote:
>   This bug is amd64 specific.  It works fine on 32-bit machines.  It has
> been discussed on debian-amd64 mailing lists:
> 
> (a) http://lists.debian.org/debian-amd64/2005/07/msg00300.html
> 
> (b) http://lists.debian.org/debian-amd64/2006/09/msg00338.html
> 
>   Briefly the problem is as follows:
> 
>   $ cmkdir directory
>   Key:
>   Again:
>   $ ls
>   directory
>   $ cfssh directory/
>   Key:
>   Directory is /var/cfs/.13687.31869
>   $ ls
>   ls: reading directory .: Input/output error
>   $ echo "Hello world" > test.txt
>   $ cat test.txt
>   Hello world
>   $ echo *
>   *
> 
>   So, as you can see it is possible to read the files, however ls or "echo *"
> doesn't list the directory contents.  Even "ls ./" and related commands
> will not work.

Hi Sergio, thanks for the report.

Unfortunately I don't have root access to an amd64 system, and would
need that to properly debug the problem, but maybe you can help me.  As
a start it would be good if you could post an strace output from this
Input/Output error.  If possible please find out the pid of cfsd, start
strace -p <pid>, and send the output of strace after reproducing the
problem above.

Regards, Gerrit.


>   By trying many things I discovered that it is possible to read the
> contents of the directory by performing the following trick:
> 
>   $ cmkdir directory
>   Key:
>   Again:
>   $ ls
>   directory
>   $ cfssh directory/
>   Key:
>   Directory is /var/cfs/.13687.31869
>   $ ls
>   ls: reading directory .: Input/output error
>   $ mkdirhier a/a
>   $ cd a/a/
>   $ ls
>   $ echo "Hello world" > test.txt
>   $ ls
>   test.txt
>   $ cat test.txt
>   Hello world
>   $ echo *
>   test.txt
> 
>   This is indeed very strange.  I can't tell where the error is but my
> guess is that somehow cfsd is not communicating properly with the nfs
> daemon.  
>   
>   Please note that as far as I am concerned this is an AMD64 only problem.
> I run cfs on i386 and works perfect!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to