Bug 29165 - Mounting smb exports with mount -t smbfs fails
Mounting smb exports with mount -t smbfs fails
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2001-02-24 00:25 EST by Jose Mercado
Modified: 2007-04-18 12:31 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-02-26 18:56:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jose Mercado 2001-02-24 00:25:56 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2smp i686; Nav)

When I mount an smb export using mount -t .smbfs //sambaserver/share
/mnt/share everything seems to work fine, ie, no complaints, df reports it
as being mounted.  Trying  to cd into /mnt/share produces cd: /mnt/share no
such file or directory.

Reproducible: Always
Steps to Reproduce:
1. mount -t smbfs //somesambaserver/share /mnt/somepreexisting/dir
2. cd /mnt/somepreexisting/dir


Actual Results:  cd: /mnt/somepreexisting/dir: No such file or directory

Expected Results:  #cd /mnt/somepreexisting/dir

I am using kernel-2.4.1-0.1.9smp-i686.
The problem goes away if I build my own kernel (either 2.4.1 or 2.4.2) from
non-rh source.
Comment 1 Glen Foster 2001-02-26 18:56:38 EST
We (Red Hat) should really try to resolve this before next release.
Comment 2 Phil Knirsch 2001-02-27 07:24:03 EST
I have just verified it with our current rawhide kernel and was able to mount a
smb exported filesystem using

mount -t smbfs -o username=foo,password=bar //server/foo /mnt/test

therefore i close the bug as RESOLVED in Rawhide.

Read ya, Phil
Comment 3 William Turner 2001-04-13 15:01:49 EDT
I just tried (unsuccessfully) mounting a smb export with Wolverine.  The 
problem still exists.  

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