Simon Gander

Hmmm ... question 1, are you sure that it is APFS formatted? Question 2, what does -d say?

Ok, will look into that ...

The superblock at position 0 is not always written, that's why on mount you have to search for the most recent superblock in the checkpoint area. Thus, this message is...

Are you sure that the volume is not encrypted using the T2 chip?

Has the volume been converted from HFS? If so, it might work now (see also #130).

Well, the options are uid=N, gid=N, and only numeric values are supported. Can you run it with an additional `-d 15` option, and tell me if you see something relevant?

Well, run apfs-fuse in one console, and execute the commands in another console. When running with debug flags, apfs-fuse will not return until the volume is unmounted. Because it will...

Did you mount as root and try to access it as user? If yes, did you mount with `-o allow_other`?

Hmmm ... looks like some filesystem corruption to me. You could also try mounting some older xid. This is not currently implemented though. In ApfsContainer.cpp, method ApfsContainer::Init(), line 105, change...

Actually, in the current version, there is a command line parameter for that ... no need to change source code anymore. But glad it worked :)