BjoKaSH / maczfs-archive

Legacy MacZFS - Archived here due Google-code shutdown. Automatically exported from code.google.com/p/maczfs -- Do Not Use! Use https://openzfsonosx.org/
Other
1 stars 0 forks source link

File disappear when copying if name contains french character #53

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Name the file with a french character like é or â on a hfs file system
2. Copy the file to the zfs with the Finder

What is the expected output? What do you see instead?
The file disappears on the next fs event like if it was not copied

What version of the product are you using? On what operating system?
119

Please provide any additional information below.

Original issue reported on code.google.com by ozitvo...@gmail.com on 25 Aug 2010 at 5:13

GoogleCodeExporter commented 9 years ago
Thanks for looking into this. I suspect that it also has an effect on the 
latest build (MacZFS_74) but this is probably a Mac specific issue.

Original comment by alex.ble...@gmail.com on 25 Nov 2010 at 9:28

GoogleCodeExporter commented 9 years ago
For what it's worth, I am not currently experiencing this on 75.0.10.

Original comment by dmz...@gmail.com on 22 Jan 2011 at 3:49

GoogleCodeExporter commented 9 years ago
I had this problem a couple days ago. I was able to save the file successfully 
directly onto ZFS partition with the foreign characters (``š'' and ``ć''), 
but after doing that I couldn't stat the file (Finder reported a file does not 
exist error). A reboot fixed the problem.

When doing ls on the file, it saw the file in the directory listing, but said 
it didn't exist.

Original comment by druro...@gmail.com on 13 Jun 2011 at 11:03

GoogleCodeExporter commented 9 years ago
This thread is somewhat old; but it was the most relevant search result.

I've been experiencing the problem described in the original post. I have 
observed however, that files disappear, and folders appear empty only when 
Finder is involved. When it is the Finder itself doing the file/folder 
operations (e.g. moving an individual file or folder over from HFS+ that has an 
accented character in its name), folders just vanish, while individually moved 
files may or may not. The same operations done from the command line work out 
just fine; and applications can see/read them.

The culprit here is most likely Finder. ...but would Apple accept any 'bug 
reports' related to this?

Original comment by alptekin...@gmail.com on 18 Nov 2012 at 11:35

GoogleCodeExporter commented 9 years ago
Just happened to me on a fresh, stable MacZFS install.
Priority-Low ? Come on this is a very CRITICAL bug as it can easily lead to 
data lost by the user !

Original comment by dpere...@gmail.com on 18 Sep 2013 at 4:41

GoogleCodeExporter commented 9 years ago
This is just crazy, unacceptable, I have again many folders disappearing, just 
in front of my eyes ! Were there. Click to open. Poof ! No more there.
Go in the terminal : NOT THERE EITHER.
Back in the Finder : some folders are back... until I click again.
Terminal : still nothing.
It's breaking my heart, but I have to uninstall right away this unreliable 
piece of software (that's advertised as bulletproof).

Original comment by dpere...@gmail.com on 18 Sep 2013 at 5:04

GoogleCodeExporter commented 9 years ago
FYI, each time I see an item disappear, I've got this in my logs : 
Sep 18 22:52:31 MacPro.local filecoordinationd[341]: Warning: Exception caught 
during decoding of received message, dropping incoming message.
    Exception: Exception while decoding argument 5 of invocation:
    <NSInvocation: 0x7fa613e022c0>
    return value: {Vv} void
    target: {@} 0x0
    selector: {:} addSubscriber:forID:appBundleID:fileURL:
    argument 2: {@} 0x7fa613e02e50
    argument 3: {@} 0x7fa613e01190
    argument 4: {@} 0x7fff78aab7c0
    argument 5: {@} 0x0

    Exception: decodeObjectForKey: Object of class "NSURL" returned nil from -initWithCoder: while being decoded for key (null)

Original comment by dpere...@gmail.com on 18 Sep 2013 at 8:59

GoogleCodeExporter commented 9 years ago
To me, the issues above seem symptomatic of use of something other than 
normalisation form D. 

If the following file system property is supported by MacZFS 74.3.0 then please 
consider the setting: 

normalization=formD

You should not expect the effect of the setting to be retrospective. 

Discussions: 

<http://forum.macbidouille.com/index.php?s=1b58b79ded51dfe92267c87d5d7a427a&show
topic=374137&view=findpost&p=3791024>

– and in the Google group for MacZFS development: 

NFD: normalization=formD (normalisation form D)
<https://groups.google.com/d/msg/maczfs-devel/afg0R2jITKc/IWxaKv5c6ggJ>

Original comment by grahampe...@gmail.com on 7 Oct 2013 at 12:02