From: Theodore Ts'o <tytso@mit.edu>
To: Dave Chinner <david@fromorbit.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
guy@linux.com, jra@google.com, drosen@google.com,
hch@infradead.org
Subject: Re: [RFC] A proposal for adding case insensitive lookups to ext4
Date: Mon, 7 Nov 2016 00:42:42 -0500 [thread overview]
Message-ID: <20161107054242.m6q4rufasjpysnvp@thunk.org> (raw)
In-Reply-To: <20161107043035.GH28177@dastard>
On Mon, Nov 07, 2016 at 03:30:35PM +1100, Dave Chinner wrote:
>
> OK, as long people are ok with things going wonky when the
> filesystem is mounted without those mount options, I'm not really
> fussed...
There are apparently NAS boxes that export the same directory with
case insensitive Samba and case sensitive NFS exports at the same
time, which would have all of these problems, and people apparently
don't complain much.
I agree we need to warn people in the documentation that if the file
system is initially mounted w/o case folding, and they create files
such as Readme and README in the same directory, and then mount the
file system with case folding, which file they get will be a bit Wonky
--- specifically, "Readme" and "README" will get the file which is an
exact match, but it is undefined which file "ReAdMe" will return.
Personally, I don't plan to lose any sleep over the issue. :-)
- Ted
next prev parent reply other threads:[~2016-11-07 5:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 17:28 [RFC] A proposal for adding case insensitive lookups to ext4 Theodore Ts'o
2016-11-04 16:14 ` Andreas Dilger
2016-11-04 21:51 ` Theodore Ts'o
2016-11-04 23:12 ` Andreas Dilger
2016-11-06 23:57 ` Dave Chinner
2016-11-07 0:14 ` Theodore Ts'o
2016-11-07 4:30 ` Dave Chinner
2016-11-07 5:42 ` Theodore Ts'o [this message]
[not found] ` <CAEuANoLdZ0STmhp+1voS9K6+Ndkb6zfSWEcc0_thUtDjS8NPwg@mail.gmail.com>
2016-11-05 0:00 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161107054242.m6q4rufasjpysnvp@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=david@fromorbit.com \
--cc=drosen@google.com \
--cc=guy@linux.com \
--cc=hch@infradead.org \
--cc=jra@google.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox