No way to know when a file is written

[GoogleCodeExporter]

Fuse-zip creates the archive in RAM and only writes the changes to file
storage after the unmount command is given. If a large file is created and
the writeout takes a lot of time, there is no way to know when the write is
complete, because even the unmount command is returned before the file is
written.

I understand that this has been done for speed purposes, but it really
makes fuse-zip unisable for any real work. If I write a file to a folder, I
expect it to start writing as soon as possible and finish writing before
returning from 'sync' or 'umount' commands.

Holding the whole archive changeset in RAM also makes this unsutable for
any kind of backup usage (backups tend to have several Gbs of files).

Original issue reported on code.google.com by aigar...@gmail.com on 7 Sep 2009 at 11:32

[GoogleCodeExporter]

Yes, It is a known issue. Today I don't know how to tell FUSE to wait until
fusezip_destroy() finishes.

As a workaround you can mount file system with -f (don't detach from terminal) 
option
and wait until fuse-zip process finished.

Also I think that it is better to use 'zip' command for backup purposes.

Original comment by alexander.galanin on 7 Sep 2009 at 6:26

• Changed state: Duplicate