22 Jan
2023
22 Jan
'23
4:36 a.m.
Hi Folks,
I have three NASs: two Buffalo Link Stations, and one ASUStor. It never occurred to me to
check for case insensitivity before, but I did and they aren't! This surprises me
because case sensitivity is much easier to implement and it does not surprise me because
the Windows world is case insensitive.
So, my first question is, "Can I require case sensitivity during the mount
command?". I can't find anything about that, but I have seen comments claiming
that CIFS mounts are case sensitive by default, but mine clearly aren't.
As an ancillary question, does anybody know if btrfs is case sensitive? I've spent
some time looking, but I haven't found any comments I trust. For example, the [
https://en.wikipedia.org/wiki/Btrfs | Wikipedia article ] fails to mention it.
Thanks for the help,
--
Chris.
V:916.799.9461
F:916.974.0428
A: Because we read from top to bottom, left to right.
Q: > Why should I start my reply below the quoted text?
26 Jan
26 Jan
6:18 p.m.
On Sat, Jan 21, 2023 at 08:36:33PM -0800, Chris Miller wrote:
Hi Folks,
I have three NASs: two Buffalo Link Stations, and one ASUStor. It never
occurred to me to check for case insensitivity before, but I did and
they aren't! This surprises me because case sensitivity is much easier
to implement and it does not surprise me because the Windows world is
case insensitive.
So, my first question is, "Can I require case sensitivity during the
mount command?". I can't find anything about that, but I have seen
comments claiming that CIFS mounts are case sensitive by default, but
mine clearly aren't.
As an ancillary question, does anybody know if btrfs is case sensitive?
I've spent some time looking, but I haven't found any comments I trust.
For example, the [1]Wikipedia article fails to mention it.
I don't have btrfs, yet if I check the man page for btrfs, you will see the
options. Plus, there are certain options that are implemented regardless
of the file system type.
Start with the following
$ man mount
Search for
FILESYSTEM-INDEPENDENT MOUNT OPTIONS
Then search for file system specific options.
FILESYSTEM-SPECIFIC MOUNT OPTIONS
You will see that there is a man page specific to btrfs
You can see that ntfs has the following option. I imagine that this is
something just for ntfs.
$ man mount.ntfs
ignore_case (only with lowntfs-3g)
Ignore character case when accessing a file (FOO, Foo,
foo, etc. designate
the same file). All files are displayed
with lower case in directory listings.
Or, use
$ apropos mount
Investigate btrfs.
$ man btrfs
Install the man pages if you haven't installed them.
That should give you your options.
Brian
--
Brian Lavender
http://www.brie.com/brian/
"There are two ways of constructing a software design. One way is to
make it so simple that there are obviously no deficiencies. And the other
way is to make it so complicated that there are no obvious deficiencies."
Professor C. A. R. Hoare
The 1980 Turing award lecture
7:13 p.m.
Hi Brian,
I don't have btrfs, yet if I check the man page
for btrfs, you will see the
options. Plus, there are certain options that are implemented regardless
of the file system type.
Ya know, it never occurred to me to use the man pages.
However, "man btrfs" gives me "btrfs - a toolbox to manage btrfs
filesystems", and the suggested "man btrfs-filesystem" only uses the word
"case" in reference to sizing descriptions like "KB", "MB",
"GB", and so on. So at a minimum Fedora 36 does not give me the same experience
you have, and I still don't know if btrfs is "Case Sensitive", or merely
"Case Preserving". But, it turns out that it doesn't matter. btrfs was one
of the options for formatting the disks in the ASUStor, and apparently, not knowing
anything about btrfs, I used ext4. So, btrfs is no longer relevant to my problem.
$ man mount.ntfs
ignore_case (only with lowntfs-3g)
Ignore character case when accessing a file (FOO, Foo,
foo, etc. designate
the same file). All files are displayed
with lower case in directory listings.
NTFS in a Windows environment is "Case
Preserving". I have no idea if it is actually designed as "Case Sensitive"
with a layer of "Case Agnosticism", or if it is "Case Preserving" and
that's the end of it, meaning I can't get to any "Case Sensitive"
behavior, that we all know is there; it takes effort to ignore case.
Everywhere I hear "CIFS is Case Sensitive, if the underlying filesystem supports
this.", but I don't see it. I have three NASes -- two Buffalo LinkStations and
one ASUStor. At a minimum the ASUStor has an ext4 filesystem, which I know is "Case
Sensitive", at least in the Linux use case, and I'm pretty sure the Buffalo
LinkStations do as well. I have never tried to use any with a Windows client.
There is a "nocase" mount option and interestingly there is no
"no-case" option, meaning there is also no "case" option. This means
that you can suppress "Case Sensitivity", but you can't assert it.
I now know that I am dealing with a "Case Sensitive" filesystem (ext4) and a
"Case Sensitive" mount operation (CIFS), so I should be seeing "Case
Sensitivity" -- and I'm not. And I have no explanation. And it isn't limited
to the ASUStor; the Buffalo LinkStations are just the same.
echo "UPPER" > FILE;
echo "lower" > file;
... creates a single file, "FILE", and the second "creation"
overwrites it so the contents of "FILE" is "lower".
Thanks for the help,
--
Chris.
V:916.799.9461
F:916.974.0428
A: Because we read from top to bottom, left to right.
Q: > Why should I start my reply below the quoted text?
710
days inactive
714
days old
2 comments
2 participants
participants (2)
-
Brian E. Lavender -
Chris Miller