Opened at 2015-12-04T21:20:50Z
Closed at 2020-06-30T13:42:05Z
#2604 closed defect (somebody else's problem)
Magic Folder: handle case-insensitivity on Windows more sensitively
| Reported by: | daira | Owned by: | daira |
|---|---|---|---|
| Priority: | major | Milestone: | undecided |
| Component: | code-frontend-magic-folder | Version: | n/a |
| Keywords: | magic-folder reliability preservation dataloss windows | Cc: | |
| Launchpad Bug: |
Description
Suppose that a magic folder has both Linux and Windows clients. The Linux client writes two files with names differing only in case, e.g. "readme" and "README". The Windows client will clobber one file with the contents of the other (depending on the order in which they get downloaded). It may also get confused with downloads for one of the files causing filesystem notifications for the other.
Change History (3)
comment:1 Changed at 2015-12-04T23:19:49Z by daira
comment:2 Changed at 2015-12-06T04:38:38Z by daira
I added an implementation of NTFS uppercase mapping for Windows Vista: https://github.com/tahoe-lafs/tahoe-lafs/commits/2604.ntfs-vista-casemap.0. I'm not sure whether we need it yet, but it was an interesting and fun exercise.
comment:3 Changed at 2020-06-30T13:42:05Z by exarkun
- Resolution set to somebody else's problem
- Status changed from new to closed
magic-folder has been split out into a separate project - https://github.com/leastauthority/magic-folder
The uppercase mapping used by NTFS is defined by an on-disk table created when the filesystem is formatted. Here's a reverse-engineering of the initial tables used by Vista and XP, from ntfs-3g.