Bug 120342
Summary: | list files in a mount samba directory | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | José Salgado <tatxe> |
Component: | samba | Assignee: | Jay Fenlason <fenlason> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | dan, frederic.riss, greig, imoq, jfeeney |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-04-21 17:26:09 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
José Salgado
2004-04-07 21:05:25 UTC
This would be a problem with the Linux kernel smbfs filesystem module, and not a Samba problem. I'm reassigning this to the kernel maintainers. You should try the Linux cifs filesystem module instead. It's more recent than smbfs and has active maintainers. smbfs is likely to be removed in a version or two. Well, then I had: [root@iglu root]# /sbin/mount.cifs //WWW/www /mnt/saladelfrio -o user=jose,password=baixantperlafontdelgat mount error 5 = Input/output error Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) actually this is an selinux issue with the winnt share not being configured for labling Could you submit the AVC messages within the /var/log/messages. I will add a genfs_context for cifs. Dan Using CIFS The var/log/messages is: Apr 9 15:00:39 iglu kernel: CIFS VFS: cifs_mount failed w/return code = -5 Using SMBFS the message is: Apr 9 15:01:49 iglu kernel: smbfs: Unrecognized mount option noexec Apr 9 15:01:49 iglu kernel: smb_lookup: find //.Trash-friopolar failed, error=-57 Apr 9 15:01:49 iglu kernel: smb_proc_readdir_long: error=-57, breaking Try with latest policy -1.11.1-1 I've got all the system updated via up2date and apt-get and the lastest policy package is: [root@iglu memstick]# rpm -q policy policy-1.10.2-5 Yes add ftp://people.redhat.com/dwalsh/SELinux/Fedora to /etc/yum.conf and you will get newere policy files. That way you don't have to wait 24 hours. ItÅ not a policy problem imho. Running on a custom kernel right now with SELINUX disabled (1. the avc messages are driving me nuts and making it insanely hard to read console output and logs, 2. easiest way I could think of to make sure SELinux is not to blame at all) and still getting an invalid slot error for this. Smbclient works fine btw even in the official selinux enabled kernel (2.6.5.1-315) up2date gave me. Considering CIFS is going berserk on me every time I try to use that (one of the cifs daemons goes wild, becomes unkillable even with kill -15 and keeps pumping stuff onto eth0 slowing the connection down substantially with only a reboot as solution) this is kind of bugging me a lot. With the new policy: [root@iglu root]# rpm -q policy policy-1.11.1-2 ar(uid=500) Apr 13 19:36:57 iglu su(pam_unix)[2605]: session opened for user root by friopolar(uid=500) And the log is: Apr 13 19:37:07 iglu kernel: smbfs: Unrecognized mount option noexec With cifs [root@iglu mnt]# /sbin/mount.cifs //WWW/www /mnt/saladelfrio -o user=jose,password=lilolariiii mount error 5 = Input/output error Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) And the log is: Apr 13 19:40:04 iglu kernel: CIFS VFS: cifs_mount failed w/return code = -5 Also, I am not convinced (in fact pretty sure that it isn't) that it is a kernel problem either. Smbfs worked fine for me on a one of the older kernels (although i had to recompile it with smbfs support) and started giving this error too after a round of updates. Seems to me something outside the kernel changed and broke it. Maybe mount itself or somesuch ? As I stated before its defenitly not a policy issue since I running a kernel without selinux in it. Following my own advise. I used an older version of 'smbmount' (one I found in samba-client-3.0.0-15.i386.rpm, which was just the first older samba 3.0 rpm I bumped into really) and this solved my problem. No invalid slot message and doing an ls -al of /mnt/<samba_mount> worked flawlessly. I am not sure where and why it broke in the newer versions and why not more people (outside fedora) seem to be having this problem. I did websearches of all kinds to see if this problem was perhaps discussed elsewhere on the web and found nothing on it anywhere (which seems odd if samba-client is to blame, people with other distros should have seen it too you would think). Anyways, for now a quick qorkaround for me is : Get smbmount from an older samba release (like from the rpm on the FC2T1 of FC2T2 install cd, I used the one from FC2T1 I think) and call that one instead of the one in /sbin when mounting SMBFS shares. back to samba again then :) bug #119766 is duplicate of this one, I think. Same here. Tested with many Samba servers (Fedora, Win2000, Debian Sarge). This bug didn't get fixed with the latest samba, samba-3.0.3-2.pre2 FYI I've also seen smb-mount fail with the invalid slot error on all fedora core2 versions of smbclient ( mount.cifs just hangs after you supply your password ). I see that Hans restored functionality by rolling back to samba-client-3.0.0-15. samba-client-3.0.2a-1 also works. Confirmed. I installed samba-client-3.0.2a-1.1.i386.rpm and now I can mount smbfs without any problem. Actually, I think the bug appeared in the 3.0.3pre versions. Tried multiple versions up to and including 3.0.2a and they all worked fine. Up2date and yum install 3.0.3pre2 though at the moment and thats the one it started giving the invalid slot message with. As for cifs, I can't even test cifs. Everytime I try a mount cifsd yanks my CPU to 100% and starts pumping god knows what onto my network link. Holding out for 2.6.6 which supposedly has a bunch of improvements on that matter. For the record though CIFS has NEVER worked for me. Not in FC2T1 or any of the upgrades since. I would try narrowing it down but every time cifsd goes nuts it also ends up being unkillable to boot so I didn't bother with it. The Version 3.0.3-4 doesn't work at all. Maybe it's time to think in dowgrading samba. Finally! samba-3.0.3-5.i386.rpm (from FC2, probably final release) works! Update to it at once and close this nasty bug ;) Verifying that this package works for me as well. It works for me too (almost in a NT file server). With the new version of samba (3.0.3-5), mount -t smbfs will now work, but mount.cifs still reports mount error 5 = Input/output error Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) I am still experiencing this fault. It's characterised for me by what looks like unreadable permissions on the mounted directory, as follows: [root@baldir root]# mount -t smbfs -o username=greig,uid=1000,gid=1000,domain=ITPARTNERS //10.7.0.15/data /mnt/tmp Password: <typed> [root@baldir root]# ls -la /mnt total 32 drwxr-xr-x 8 root root 4096 Jun 4 10:55 . drwxr-xr-x 21 root root 4096 Jun 4 10:40 .. ?--------- ? ? ? ? ? tmp This happens no matter what parameters I use for -o (admin user, leave out uid/gid/domain) and whether I name the server or use the IP address. Just a quick note - running FC2 with all current updates applied. |