filesystem becomes corrupt in OS X quickly if volume has files edited or added

[Former user]

Originally reported on Google Code with ID 42

I've written a Service which adds "Mount zipfile as volume" to the Services contextual
menu if the selected file is a zipfile (either by UTI type recognition or by file extension
for unregistered types), but I notice that if changes are made to the volume and then
the volume's ejected, subsequent mounts of that zipfile result in a corrupt filesystem
on that volume (added/modified files do not appear in Finder but do in the "ls" command;
"ls -la" results in "ls: MODIFIEDFILENAME: Input/output error").

If I Duplicate a file inside the volume, it does not inherit the attributes of the
original according to BetterZip's QuickLook.

Bear in mind that I'm using OS X's umount instead of fusermount because brew doesn't
install fusermount.

Altering the location of the temp directories for these mounts or disabling the "-o
local" option (which makes it visible as an ejectable volume under Shared" in the Finder
sidebar) does not seem to have an effect on this behavior. As far as I know, the script
in document.wflow's COMMAND_STRING section (lines 62-69) is how fuse-zip should mount
a zipfile to a temporary directory.

nota bene: editing this Service in Automator will corrupt the Service's info.plist
because Automator doesn't recognize custom FileTypes and overwrites them with a generic
FileTypes section.

Reported by ydoomenaud on 2014-04-01 18:28:23

<hr> * Attachment: Mount zipfile as volume.zip

[Former user]

> I notice that if changes are made to the volume and then the volume's ejected, subsequent
mounts of that zipfile result in a corrupt filesystem on that volume (added/modified
files do not appear in Finder but do in the "ls" command; "ls -la" results in "ls:
MODIFIEDFILENAME: Input/output error").

Firstly you must check that fuse-zip process are finished before doing subsequent mount
of the same file. This can be done by querying running process list.

Otherwise two file system process can share one file (one fro writing and one fro reading)
and this may be a cause of file corruption.

> If I Duplicate a file inside the volume, it does not inherit the attributes of the
original according to BetterZip's QuickLook.

What attributes do you mean: file owner, date, permissions or any other attributes?
Currently fuse-zip lacks support for posix extandede attributes (xattr).

Reported by alexander.galanin on 2014-04-06 14:14:25

[Former user]

Reported by alexander.galanin on 2014-04-06 18:16:34 - Status changed: NeedInfo

[Alexander Galanin]

No additional data provided for a while.