Samba broken

[Craig White]

On Sun, 2006-10-29 at 10:52 -0800, Kenneth wrote:
> This is driving me crazy.  Any suggestions on how to debug the problem would
> be appreciated.
> 
> I have Gentoo running on a server machine, running samba to provide network
> shares.  My "other" machine runs Windows part of the time and Linux part of
> the time.  I don't want to run both nfs and samba on server, so I find myself
> trying to connect to samba shares from Fedora Core 5.
> 
> The server has two shares exported, a public directory, and a homes share to
> allow access to home directories for individual users.
> 
> With Windows XP running on the client computer, I can connect to both shares
> with no problems.  From Fedora, I can mount the public directory, and I can
> use smbclient on the homes share with no problem.  I can also mount the homes
> share with
> mount -t cifs //server/homes <directory> -o user=<myself>
> This works with no complaints, and mount and df show it in place.
> 
> The problem is trying to access the share.  I can cd to the directory with no
> complaints, then I type ls, and I get the message
> ls: reading directory .: Invalid argument
> 
> A little more background. I had this working before.  The server side has not
> changed since it was working.  I re-installed Fedora on the client after a
> hard disk drive failure, so I'm probably missing something but I have no idea
> where to look.
> 
> I ran strace with the ls command, but it was not very helpful. It shows
> getdents() returning invalid argument.  The getdents man page says that means
> result buffer too short.  Which doesn't help identify the problem (at least
> not for me).
> 
> Sorry this is so long and disorganized, but I was trying to include all the
> relavent information.  Any suggestions appreciated.
----
sounds like an selinux issue

check /var/log/messages for avc denied messages

If you want, change selinux to permissive and reboot
<system-config-securitylevel>

on your Fedora computer - where are you mounting? <directory> doesn't
tell me anything and I would simply guess that you are mounting it
somewhere where the selinux contexts aren't happy.

Craig