SMB Sharing not case sensitive

Bug #132233 reported by neodelphi
18
Affects Status Importance Assigned to Milestone
samba
Fix Released
Medium
samba (Debian)
Fix Released
Unknown
samba (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Two computers under Feisty Fawn.
Filesystem ext3

1) Open nautilus explorer
2) Create one file named something.txt
2) Create another file named Something.txt
3) Edit something.txt and write "aaaa". Save.
4) Edit Something.txt and write "bbbb". Save.
5) Share the folder containing the two files (Windows Sharing - SMB).

On another computer (with nautilus):
6) Navigate through the network and copy the two files on the Desktop (or elsewhere).
7) Open the two files with text editor
result: both files contains "aaaa".

No errors are signaled during the transfert. This problem can be "dangerous" since the copy is not similar from the original files.

Revision history for this message
Justin M. Wray (wray-justin) wrote :

Correct me if I am wrong, but this seems more like an issue with the way Windows handles filename case, not SMB/Ubuntu.

I do not experience the same issue with Sharing Linux -> Linux.

Not that it takes away the issue, just not an issue on our end.

Thanks,
Justin M. Wray

Revision history for this message
neodelphi (neodelphi) wrote :

I agree with you with the fact that Windows doesn't care about case.

The problem is that sharing from Linux to Linux with SMB make some troubles; I didn't try with Windows. A common user may encounter difficulties with this. In fact the two files are distinguished while navigating through the network, but the copies are not.

> I do not experience the same issue with Sharing Linux -> Linux.

In my case I could experience the problem twice. I'm ready to make further experiments if necessary to help.

The problem will remain if transferring from Linux to Windows since Windows won't be able to create the two files. However, it would be better if from Linux to Linux the case was handled.

Revision history for this message
Justin M. Wray (wray-justin) wrote : Re: [Bug 132233] Re: SMB Sharing not case sensitive

Okay, let me also do some further test, on the Linux -> Linux side. As that is something we can deal with.

Eitherway, we need to come up with an approch for the Linux -> Windows example as well. As this could cause problems for news users, and more likly coorporate adoption on the server-side. As such, I'll bring this to the attention of ubuntu-server as well.

Thanks again for the report.

Thanks,
Justin M. Wray

Sent via BlackBerry by AT&T

-----Original Message-----
From: neodelphi <email address hidden>

Date: Mon, 13 Aug 2007 21:25:31
To:<email address hidden>
Subject: [Bug 132233] Re: SMB Sharing not case sensitive

I agree with you with the fact that Windows doesn't care about case.

The problem is that sharing from Linux to Linux with SMB make some
troubles; I didn't try with Windows. A common user may encounter
difficulties with this. In fact the two files are distinguished while
navigating through the network, but the copies are not.

> I do not experience the same issue with Sharing Linux -> Linux.

In my case I could experience the problem twice. I'm ready to make
further experiments if necessary to help.

The problem will remain if transferring from Linux to Windows since
Windows won't be able to create the two files. However, it would be
better if from Linux to Linux the case was handled.

--
SMB Sharing not case sensitive
https://bugs.launchpad.net/bugs/132233
You received this bug notification because you are a direct subscriber
of the bug.

Revision history for this message
Albert Damen (albrt) wrote :

In my opinion the whole Linux/Windows issue is already covered by a setting in smb.conf: "case sensitive = yes/no/auto"

man smb.conf:
       case sensitive = yes/no/auto
          controls whether filenames are case sensitive. If they aren’t, Samba
          must do a filename search and match on passed names. The default
          setting of auto allows clients that support case sensitive filenames
          (Linux CIFSVFS and smbclient 3.0.5 and above currently) to tell the
          Samba server on a per-packet basis that they wish to access the file
          system in a case-sensitive manner (to support UNIX case sensitive
          semantics). No Windows or DOS system supports case-sensitive file‐
          name so setting this option to auto is that same as setting it to no
          for them. Default auto.

For me the default setting works fine from Linux to Linux.

neodelphi, can you please attach your smb.conf to this bug?

Revision history for this message
neodelphi (neodelphi) wrote :

Here is my smb.conf.

I will try to make it working with case sensitive.

Revision history for this message
neodelphi (neodelphi) wrote :

I've just added "case sensitive = yes" to my smb.conf and it works well now. However a new user couldn't find the solution easily, could this setting be a default setting if it is not the case yet ?

Thanks for you help.

Revision history for this message
Mathias Gug (mathiaz) wrote :

The default value of the case sensitive option is auto, which should handle all types of clients.

It may be a problem with the way nautilus deals with smb shares.

Revision history for this message
oss_test_launchpad (oss-test-launchpad) wrote :

Has there been any change on this issue?

Revision history for this message
Tim Richardson (tim-richardson) wrote :

Hi.
Here is a copy/paste from a Debian bug report (mine). I think that "auto" doesn't work. By googling I came across this.

Ubuntu most likely has the same problem.

Nautilus behaves correctly when a ext3 share is forced to case-sensitive "yes", but it doesn't work with "auto". Therefore, seems to a samba server problem.

There is a risk of data loss.

To reproduce data loss:

1. Share an ext3 folder with samba on a Debian host
2. On a Debian client, use nautilus to create two different files on the samba share,
file.txt and file.abc. Put different content in the two different files
3. Rename file.abc to be file.TXT
4. Note that silently, file.txt has been destroyed. The icon in nautilus may still be visible, but on opening it, it will show the contents of the original file.abc

This is fixed by forcing case sensitive yes in the samba share (on the server).
In this case, file.txt and file.TXT are different.

It seems that "auto" case-sensitive doesn't work properly.

Revision history for this message
Thierry Carrez (ttx) wrote :

This should be fixed in 3.3.x, could someone confirm that this is fixed in Jaunty.

Changed in samba (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Triaged
Changed in samba (Debian):
status: Unknown → Fix Released
Changed in samba:
status: Unknown → Fix Released
Thierry Carrez (ttx)
Changed in samba (Ubuntu):
status: Triaged → Fix Released
Changed in samba:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.