NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/41281: cannot list files on a samba share



On 26/04/2009, Michael van Elst <mlelstv%serpens.de@localhost> wrote:
> The following reply was made to PR kern/41281; it has been noted by GNATS.
>
>
> From: Michael van Elst <mlelstv%serpens.de@localhost>
>
> To: gnats-bugs%NetBSD.org@localhost
>  Cc:
>
> Subject: Re: kern/41281: cannot list files on a samba share
>
> Date: Sun, 26 Apr 2009 13:24:56 +0200
>
>   Hi,
>
>   opendir() calls open with O_RDONLY|O_NONBLOCK but without a third
>   argument which is therefore 'random' in the ktrace output.
>
>   Listing a samba share on a netbsd-4 machine seems to work
>   fine here:
>
>   29565      1 ls       CALL  __stat30(0x80550cc,0xbfbfe2c4)
>   29565      1 ls       NAMI  "/mnt/"
>   29565      1 ls       RET   __stat30 0
>   29565      1 ls       CALL  open(0xbbbcd634,0,0)
>   29565      1 ls       NAMI  "."
>   29565      1 ls       RET   open 3
>   29565      1 ls       CALL  fcntl(3,2,1)
>   29565      1 ls       RET   fcntl 0
>   29565      1 ls       CALL  fchdir(3)
>   29565      1 ls       RET   fchdir 0
>   29565      1 ls       CALL  open(0x8051800,4,1)
>   29565      1 ls       NAMI  "/mnt/"
>   29565      1 ls       RET   open 4
>   29565      1 ls       CALL  fcntl(4,2,1)
>   29565      1 ls       RET   fcntl 0
>
>   The smbfs code isn't very precise with errnos. EINVAL can happen
>   at many places, usually this is the result of either bad hostname
>   resolution or incompatible authentication methods.
>
>   Therefore it would be interesting what kind of 'samba' server is
>   used. Here it is a real samba-3 but I guess in the error case it
>   is a Windows server.
>

No, the server is Debian Lenny.

The hostname resolution might be a problem, though.

I am not sure how the hostname specified on the command line interacts
with the stuff in ~/.nsmbrc

Still if there was problem with the hostname wouldn't reading files
fail as well?

Also mounting by IP address results in the same behaviour.

Thanks

Michal


Home | Main Index | Thread Index | Old Index