On Wed, Jan 14, 2009 at 10:55:48AM +1100, Tim Richardson wrote: > Package: samba > Version: 2:3.2.5-4 > Severity: important
> When investigating bug #510564 I noticed this > 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 > > Because this involves dataloss, it may be considered a grave bug. > > > 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. > I used SWAT for the samba server admin. Debian in both cases (server and > client) was Sid. > > I leave #510564 open because while I think samba should be fixed, it > should also be fixed in Nautilus, because there is no guarantee about the > samba server being a fixed version. Please forward a packet capture showing that case-sensitive file handling has been negotiated by the client. If it hasn't been, then this is a client bug, not a server bug. Setting 'case sensitive = yes' is wrong as a default, for the reasons described in the smb.conf manpage. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
