Bug 11965 - vfs_fruit: missing catia mapping for U+F029
vfs_fruit: missing catia mapping for U+F029
Status: ASSIGNED
Product: Samba 4.1 and newer
Classification: Unclassified
Component: VFS Modules
unspecified
All All
: P5 normal
: ---
Assigned To: Ralph Böhme
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-06-13 15:12 UTC by Matthieu Pepin
Modified: 2016-06-20 21:05 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthieu Pepin 2016-06-13 15:12:25 UTC
When using fruit:encoding=native, an additional catia mapping should be added:
0x2e:0xf029

This character is used then "mangle names = no" is used and MacOS creates a file with a terminating . (eg: test.).

Adding this mapping permits the use of such names since a final . is allowed in MacOS. Otherwise, a file named "test(U+F029)" is created on the file system and it's not readable/writable by Mac clients.

Even with this fix, Fruit still has trouble accessing resource forks for files ending with a period (like fonts), but this is caused by something else.
Comment 1 Matthieu Pepin 2016-06-20 12:51:15 UTC
Unfortunately, it seems that in some circumstances, it causes bad side effects. Sometimes, the . and .. folders are listed as U+F029 and U+F029,U+F029. This can have tragic consequences for folder deletions (it becomes recursive up to the root). I'm not to sure how to fix file names ending with a . on MacOS then... I think a naive character swap like catia does is not enough.
Comment 2 Ralph Böhme 2016-06-20 12:58:46 UTC
A log level 10 of an incidence where . or .. are mapped would be really helpful (alongside a network trace an overview of whats going on). Instructions how to reproduce it as well.
Comment 3 Matthieu Pepin 2016-06-20 13:02:04 UTC
Actually, I'm having trouble replicating it myself, but I saw it. I think it happens when stacking more vfs modules (shadow_copy2 maybe). I'm going to investigate more.