Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 371701

Summary: mount.cifs not handling native format unc strings correctly with subshares
Product: Red Hat Enterprise Linux 5 Reporter: Jeff Layton <jlayton>
Component: sambaAssignee: Jeff Layton <jlayton>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.1CC: coughlan, dmair, dzickus, jplans, krafthef, riek, spurgeon, ssorce, staubach, steved
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-08 21:18:00 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 Jeff Layton 2007-11-08 19:22:54 UTC 
I have a [public] share set up on a samba server. That share has a 'p1'
directory in it. I can mount this directory using the following format:

//server/public/p1

...but not with:

\\server\public\p1

The difference is in how mount.cifs is parsing the string. When using forward
slashes as a delimiter, the options string looks like this:

unc=//server\\public,ip=www.xxx.yyy.zzz,user=root,ver=1,rw,noauto,guest,sec=none,prefixpath=p1

...with backslashes I get an option string like this:

unc=//server\\public\\p1,ip=www.xxx.yyy.zzz,user=root,ver=1,rw,noauto,guest,sec=none

...mount.cifs is not correctly stripping the "p1" off of the unc string and
adding the prefixpath option with native format UNC strings.
Comment 1 Jeff Layton 2007-11-08 21:18:00 UTC 
actually...now that I look, this bug and bug 370501 are pretty closely related.
I'll close this as a dupe, since I think we can fix both in userspace...


*** This bug has been marked as a duplicate of 370501 ***