From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [RFC v2] Unicode/UTF-8 support for XFS Date: Mon, 29 Sep 2014 04:06:08 -0700 Message-ID: <20140929110608.GB17258@infradead.org> References: <20140918195650.GI19952@sgi.com> <20140922222611.GZ4322@dastard> <5422C540.1060007@sgi.com> <20140924231024.GA4758@dastard> <54257D3F.70302@sgi.com> <20140926165605.GA25274@infradead.org> <20140926170407.GB6012@samba2> <5425C067.7080904@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jeremy Allison , Christoph Hellwig , Dave Chinner , Ben Myers , linux-fsdevel@vger.kernel.org, tinguely@sgi.com, xfs@oss.sgi.com To: Olaf Weber Return-path: Received: from bombadil.infradead.org ([198.137.202.9]:55036 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751601AbaI2LGL (ORCPT ); Mon, 29 Sep 2014 07:06:11 -0400 Content-Disposition: inline In-Reply-To: <5425C067.7080904@sgi.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Sep 26, 2014 at 09:37:11PM +0200, Olaf Weber wrote: > My argument against "mount time case-insensitivity" and for "mkfs time > case-insensitivity" is related to switching from the case-sensitive domain > to the case-insensitive one. > > For case-sensitive, from "README" to "readme" there are 64 different > possible filenames. Let's say you create 63 out of these 64. Now remount > the filesystem case-insensitive, and try to open by the 64th version of > "readme". It is not an exact match for any of the 63 candidate files, and a > case-insensitive match to all 63 candidate files. Which of these 63 files > should be opened, and why that one in particular? Well, the point is not that we use the CI-capable hash all the time. I fully expect the current XFS behavior to remain the default for normal systems forever. I just want to make sure that the CI implementation you chose can also allow mixed lookups if we desire.