SparkFS

I was impressed by ArcTree, and it worked for me. ;) Almost.

I mistakenly assumed I could update the first Volume’s archive with newer software versions. The net result was that I managed to corrupt the whole archive (Volume 1) using SparkFS 1.56 and a Samba share, which I accessed from OmniClient—Pi3B and Pi4B

I trust this post helps others avoid the same assumptions I’d made.

The volumes are just ordinary zip archives, no reason you can’t update them by hand.
The program was written with the idea of the destination being blank space.
Could you write to a folder containing a previous set of volumes (?) – maybe – bad things could happen like a zip file going over the 2GB limit.
Many possibilities, like allowing the volumes to be updated, balancing the contents better – at the moment it quits one volume when adding the next file would push it over the limit. It could seek out smaller files to bring the volume up to the limit.
Mixing things like SparkFS and network file systems didn’t use to work – long time since I have heard of problems…

Mixing things like SparkFS and network file systems didn’t use to work – long time since I have heard of problems…

That’s the kinf of thing that’s ends up with “LanManFS in use” on my machine.

Mixing things like SparkFS and network file systems didn’t use to work – long time since I have heard of problems…

I think I still get problems sometimes when opening a zip file via ShareFS. I just avoid it as much as possible, so I cannot be sure of the circumstances.