public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Vega <vega_james@lycos.com>
To: linux-kernel@vger.kernel.org
Subject: fat32 all upper-case filename problem
Date: Sun, 04 Apr 2004 18:49:50 -0400	[thread overview]
Message-ID: <4070910E.7020808@lycos.com> (raw)

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

I've run across an interesting problem with creating all upper-case 
files/direcotries on fat32 partitions.  After creating a file in all upper-case, 
I can access it for a short time using either the all upper-case name or the all 
lower-case name.  After a short amount of time (or a umount/mount), I can only 
access the file via the all lower-case name.  I'm currently using kernel 2.6.4, 
but I've been seeing this since at least November of last year.

I've talked to a few people to see if anyone else can reproduce this and so far, 
I'm the only one that has been able to (save for the person that reported this 
bug http://bugs.xiph.org/show_bug.cgi?id=413).  Please CC any replies to me as I 
am not subscribed to the list.

Thanks,
James Vega

Example:

debil% touch /usbdrive/CASE
debil% ls /usbdrive
case
debil% ls /usbdrive/CASE
/usbdrive/CASE
debil% ls /usbdrive/case
/usbdrive/case
debil% umount /usbdrive && mount /usbdrive
debil% ls /usbdrive/case
/usbdrive/case
debil% ls /usbdrive/CASE
ls: /usbdrive/CASE: No such file or directory

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

             reply	other threads:[~2004-04-04 22:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-04 22:49 James Vega [this message]
2004-04-05 10:30 ` fat32 all upper-case filename problem Marco Roeland
2004-04-05 19:40   ` James Vega
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=4070910E.7020808@lycos.com \
    --to=vega_james@lycos.com \
    --cc=linux-kernel@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