Bug 2097 - Share length limitations and weird behavior
Summary: Share length limitations and weird behavior
Status: RESOLVED FIXED
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: File Services (show other bugs)
Version: 3.0.9
Hardware: x86 Linux
: P3 major
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-29 10:05 UTC by Misty Stanley-Jones
Modified: 2006-01-18 09:00 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Misty Stanley-Jones 2004-11-29 10:05:26 UTC 
I had a share called "Accounting" (10 characters).  I could see that share from 
clients (WinXP/2K) but any file would be opened as read-only, despite being 
writeable from the viewpoint of Windows, the Samba configuration, and the 
underlying filesystem configuration.  I changed the share name to "Acct" and 
the behavior changed to the expected (writable files).  Before changing the 
share name, I confirm that file locking (either in Samba or on Linux) were not 
the problem. 
 
WinXP and Win2K don't have problems accessing long file names (that I can find) 
so it looks like this might be a limitation in Samba.  I could swear that this 
bug was not present in 3.0.8 or previous but I'm not able to revert to test it.
Comment 1 Gerald (Jerry) Carter (dead mail address) 2006-01-18 09:00:08 UTC 
please retest against 3.0.21a.  I'm a little skepitical about 
the original bug report only because it doesn't make logical 
sense to me based on code reviews.  Please reopen if you can 
still reproduce the issue.