Please support true case sensitivity with NFS

[kentvv]

To truly support the Linux/Unix users please add true case sensitivity. In particular, allow creation of files with names that differ only in their capitalization.

For example: FileName and FILENAME are separate and unique filenames.

If the case insensitive mapping was done to support Windows, please considering allowing NFS mounts to be segregated from Windows Samba shares.

Thank you

[doktor.notor]

Eh What kind of filesystem are you using on the drive you mount via NFS? (And, for starters are you sure you are not confusing NFS with the samba mounts?)

[kentvv]

I've enabled NFS on the DS508 and mounted a share from the DS508 to a Linux machine using NFS.

I'm not sure about your first question... my understanding is that the DS508 uses some sort of modified EXT3 filesystem.

Thanks

[doktor.notor]

I've enabled NFS on the DS508 and mounted a share from the DS508 to a Linux machine using NFS.
I'm not sure about your first question... my understanding is that the DS508 uses some sort of modified EXT3 filesystem.

And, what kind of problem are you having with case-sensitive stuff? You can find you which filesystem you are using when you ssh in and type "mount" command.

[kentvv]

I. Demonstration of the problem:

a) On a "normal" Linux ext3:

Code: Select all

linux-c95a /test/ext3# touch filename
linux-c95a /test/ext3# ls
filename 
linux-c95a /test/ext3# mv filename FileName
linux-c95a /test/ext3# ls
FileName 
linux-c95a /test/ext3# touch filename
linux-c95a /test/ext3# ls
filename  FileName 
linux-c95a /test/ext3#


b) On a NFS mount from the DS508:

Code: Select all

linux-c95a ds508/tmp# touch filename
linux-c95a ds508/tmp# ls
filename 
linux-c95a ds508/tmp# mv filename FileName
mv: `filename' and `FileName' are the same file
linux-c95a ds508/tmp# touch FileName
linux-c95a ds508/tmp# ls
filename 
linux-c95a ds508/tmp#


II. Results of mount on the ds508:

DiskStation> mount
/dev/md0 on / type ext3 (rw,data=ordered)
/tmp on /tmp type tmpfs (rw)
/sys on /sys type sysfs (rw)
/proc/bus/usb on /proc/bus/usb type usbfs (rw)
/dev/md2 on /volume1 type ext3 (usrquota,grpquota,data=writeback)

[doktor.notor]

Well, looks like the developers need a big smack with a jumbo-sized cluebat... Really hard to believe someone is stupid enough to patch ext3/reiserfs filesystems to make them case-insensitive because case sensitive = no configuration option in Samba would apparently be too easy and smart and make too much sense (here's another thread on this).

WTH?!

Fixing this issue is entirely impossible without reformatting your RAID arrays with standard, non-crippled mke2fs or mkreiserfs which of course means you need to move your data elsewhere first. After that, you'd have to disable any kind of filesystem checking with the crippled e2fsck/reiserfsck bundled with the firmware.

(To make this clear for non-Linux-savvy readers - this issue has nothing in common with NFS as the subject of the post might suggest... Standard NFS behaviour is case-sensitive when the underlying filesystem is case sensitive. OTOH, Samba by default is case-insensitive but case-preserving (which is exact same behavior as in Windows, totally compatible, causing zero issues to Windows users regardless of the underlying filesystem and there's exactly zero valid reasons to screw up documented ext3/reiserfs filesystem behaviour and features )

Looks like a good case for RMA to me. This by no means is a feature request, this is a serious bug.

[mich]

I can hardly believe that this is still not fixed. This bug has been known for more than a year now. I didn't know of this behaviour when I bought my 207+, and I'm facing serious problems with it in my environment, quite similar to those that many others already stated.

It can't be that hard to offer an option, can it?

I'm seriously thinking about returning the device although it fits my needs well otherwise. I can definitely not recommend it to others as it stands.

[doktor.notor]

It can't be that hard to offer an option, can it?

Messing with filesystem sensitivity is not an option at all. You simply leave such stuff as it is. As already explained above, Samba has options to set up the desired behaviour, so does the native NFS client from Microsoft. Sorry, but such brainfarts can't really be tolerated, dear Synology please revert your completely broken patches in your firmware.

I'm seriously thinking about returning the device although it fits my needs well otherwise. I can definitely not recommend it to others as it stands.

+1 on this... Huge disappointment.

[doktor.notor]

Dear Synology, any response here

[syno.allen]

We are planning to use case-sensitive filesystem in the next release.

Please note that all development information is subject to change without notice.

[doktor.notor]

We are planning to use case-sensitive filesystem in the next release.

Greatly appreciated.

[kentvv]

This is great news!

[maiden_taiwan]

Please, please hurry with this one: it is dangerous because it happens silently. Probably lots of people who are backing up their systems via NFS and rsync don't realize that their backups are corrupted because file "Foo" overwrites file "foo".

Thank you for fixing this in the next version.... When is it due?

[sthomas]

I can barely believe I'm reading this thread. The filesystem case patch was crazy!

A hearty +1 to all those requesting when corrected firmware will be available.
Will we have to reformat?

My God!

Steve

[Shamino]

Has this issue been solved as yet?