On Fri, Jan 8, 2010 at 3:39 PM, <[email protected]> wrote: > On Fri, Jan 08, 2010 at 02:01:08PM -0600, Paul Hartman wrote: > >> I haven't noticed any difference with any of my vfat devices in >> 2.6.32. Filenames have mixed-case and seem usual. Where did you read >> about 2.6.32 changing long filename handling? I can't find any info >> about it. > > I have read it in several places, but the only one I (think I) > remember by name is lwn.net, and I couldn't give you any specific > article.
In the 2.6.32 kernel ChangeLog this is the only thing that looks to address it, and if anything it sounds like it should be the opposite of your problem (fixing it instead of causing it)... weird. Maybe try to add shortname=mixed to your mount options in case something in your system has it set otherwise. commit 955234755ce4a2c33cfc558912aa8f2148cc1fc6 Author: Paul Wise <[email protected]> Date: Sat Aug 1 21:30:31 2009 +0900 vfat: change the default from shortname=lower to shortname=mixed Because, with "shortname=lower", copying one FAT filesystem tree to another FAT filesystem tree using Linux results in semantically different filesystems. (E.g.: Filenames which were once "all uppercase" are now "all lowercase"). So, this changes the default of "shortname=lower" to "shortname=mixed". Signed-off-by: Paul Wise <[email protected]> [change fat_show_options()] Signed-off-by: OGAWA Hirofumi <[email protected]>
