public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Vega <vega_james@lycos.com>
To: Marco Roeland <marco.roeland@xs4all.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: fat32 all upper-case filename problem
Date: Mon, 05 Apr 2004 15:40:18 -0400	[thread overview]
Message-ID: <4071B622.20103@lycos.com> (raw)
In-Reply-To: <20040405103008.GB12373@localhost>

[-- Attachment #1: Type: text/plain, Size: 2389 bytes --]

Marco Roeland wrote:
> You forgot a 'ls /usbdrive' *before* the 'touch'. Now we don't know
> whether it was empty before. We'll assume so.

Sorry. Yes, the directory was empty before the 'touch'.

>>debil% touch /usbdrive/CASE
>>debil% ls /usbdrive
>>case
> 
> 
> This suggests that you've mounted your usbdrive (vfat probably?)
> _specifically_ with the option to force lowercase filenames. The default
> is to preserve the case of the filename (to the filename *should* be CASE here)
> and to see both names as equals.

Here is the output from the 'mount' command:

/dev/sda1 on /usbdrive type vfat (rw,noexec,nosuid,nodev,uid=1000,gid=1000)

AFAIK, I did nothing to force lowercase filenames.

> Another possibility is that there *was* already a file called 'case' and
> that the actual writing of the 'CASE' file in the directory is postponed
> until some sort of 'sync' operation. This also would need a
> specific 'case-sensitive' mount option.
> 
> 
>>debil% ls /usbdrive/CASE
>>/usbdrive/CASE
>>debil% ls /usbdrive/case
>>/usbdrive/case
> 
> 
> The above normally can only happen if there really are *two* files, one
> name 'case' and the other 'CASE'. So a case sensitive filesystem.

There was only one file as shown by the ls output above.  Also, the few people 
that I have asked to reproduce this are always able to ls both 'case' and 'CASE' 
even after a remount or waiting for the cached entry to expire.

>>debil% umount /usbdrive && mount /usbdrive
>>debil% ls /usbdrive/case
>>/usbdrive/case
>>debil% ls /usbdrive/CASE
>>ls: /usbdrive/CASE: No such file or directory
> 
> 
> Looks like you have mounted the thing with case-sensitiviy *and* forcing
> lowercase filenames always. Either there is a bug in the combination,
> or perhaps there is a bug in that the uppercase name is cached for some
> time in VFS until the lowercase name is reread from the usbdrive?

Again, I'm not knowingly specifying either case-sensitivity or forced lowercase 
filenames.  The line in /etc/fstab is as follows:
/dev/sda1 /usbdrive auto (rw,noexec,nosuid,nodev,uid=1000,gid=1000) 0 0

> When you test this please be very careful to reproduce every start and
> end condition *exactly*. <Bad pun alert> It's very easy to look at
> Heisenbugs here, with all these virtual filenames in case space. </Bad
> pun alert>

Thank you for the suggestions. I'll keep these in mind for future testing.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 264 bytes --]

  reply	other threads:[~2004-04-05 19:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-04 22:49 fat32 all upper-case filename problem James Vega
2004-04-05 10:30 ` Marco Roeland
2004-04-05 19:40   ` James Vega [this message]
2004-04-05 13:02 ` OGAWA Hirofumi
2004-04-05 19:44   ` James Vega
2004-04-05 21:39     ` James Vega

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=4071B622.20103@lycos.com \
    --to=vega_james@lycos.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco.roeland@xs4all.nl \
    /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