Bug 129124
Summary: | kernel: smb_lookup: find //test.xml failed, error=-5 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Greg <gregh1> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED NEXTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | pfrields, wtogami |
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-16 06:01:07 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
Greg
2004-08-04 08:40:56 UTC
what server type is this ? Does cifs work better ? The mapped drive is on an AS400 IFS, and I have not used cifs. It was working fine on kernel 2.4 (rh9). Ant build scripts also suffer the same problem. I did read that kernel 2.6.7 addressed this problem. Cheers Greg Failed to mount /mnt/RUK : mount error: cifs filesystem not supported by the system Refer to the mount.cifs(8) manual page (e.g.man mount.cifs) cifs does not seem to work? Cheers Greg I am also seeing this. My config: Server: FC2, samba 3.0.7-FC2, kernel 2.6.6-1.435, raid-1 over SATA Client 1: FC2, samba 3.0.7-FC2, kernel 2.6.8-1.521 Client 2: FC3t2, samba 3.0.7-3, kernel 2.6.8 (stock) As with Greg, cifs doesn't work for me. I only started having this issue recently, which as near as I can tell coincided with upgrading Client 1 to 2.6.8-1.521. This problem did NOT appear with the 2.6.8 stock kernel I am running on Client 2. There is at least one other issue with 2.6.8-1.521 that I have seen (affecting a network driver, apparently unrelated to this problem) so I don't have high confidence in that kernel build. When I have a moment, I will regress Client 1 to an older kernel and see what happens. Uninstalling 2.6.8-1.521 and rebooting to 2.6.6-1.435.2.3 appears to have fixed this issue. ("Client 1" in my config is actually a server; it mounts the RAID volume over SMB and a number of processes use it. So, it exposes this error within about 15 minutes of uptime.) It's worth noting that even with the errors with 2.6.8-1.521, the server on 2.6.6-1.435 *does not* report any errors -- they are strictly client-side. So: RH/Fedora kernels prior to 2.6.8-1.521 do not have this bug in my environment; stock 2.6.8 does. (My mistake earlier, I checked again.) I had this problem. Mounting as CIFS fixed it. Can you give more info on how mounting the IFS with CIFS was done? Cheers Greg Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you. |