Bug 30161 - Problem mounting smbfs
Summary: Problem mounting smbfs
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.1
Hardware: i386
OS: Linux
high
medium
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-03-01 11:04 UTC by Inger Karin Haarbye
Modified: 2007-03-27 03:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-03-02 14:50:59 UTC
Embargoed:


Attachments (Terms of Use)

Description Inger Karin Haarbye 2001-03-01 11:04:31 UTC
"smbmount" or "mount -t smbfs" give serious problem on Wolverine.
When trying to mount the remote smb-filesystem - I can't access it. "df"
tells me that the 
remote file-system is mounted. "ls" shows no files, "mc" tells me that it
can't access "pub" (or whereever I mount the smb file-system) "File 'tmp'
exists but can not be stat-ed: No such file or directory".

No problem to access the Wolverin smb-filesystem from other boxes on the
network.

Don't know if this is a "mount" or a "samba"-bug

Comment 1 Jose Mercado 2001-03-01 21:27:56 UTC
Which kernel rpm are you using?  I already pointed this bug out; supposedly it
is fixed in rawhide.

Comment 2 Inger Karin Haarbye 2001-03-01 21:56:27 UTC
I use the Wolverine kernel: kernel-2.4.1-0.1.9 (for i686 I guess).

Comment 3 Bernhard Rosenkraenzer 2001-03-02 08:22:19 UTC
Assigning to kernel

Comment 4 Henri Schlereth 2001-03-02 14:50:50 UTC
I saw this problem as well with the i586 Wolverine.


Comment 5 Michael K. Johnson 2001-03-02 19:23:28 UTC
Rawhide is 2.4.1-0.1.14 last I checked.

If it's not fixed in that kernel (or later from rawhide), please
re-open this bug report.  Thanks!

Comment 6 Henri Schlereth 2001-03-03 22:41:28 UTC
Sorry Netscape crashed on me while I was making an entry. Tested this against
the 
Rawhide kernel and it is indeed fixed. Also shift this bug to where it actually
belongs
since this was a beta-testers bug and shouldnt have been filed under Public -
Wolverine.


Note You need to log in before you can comment on or make changes to this bug.