Migration path to deterministic file name version

[loungebob]

I know I could just create a new fs volume with deterministic file name option enabled and then copy all data from the "old" diriv version to the new diriv-less one.

but I really, really, really, really (goes on for ages) would appreciate a more elegant migration path.

It took me years to upload 2 PB of data to google drive. I really dont want to spend another few years copying stuff but I also really want to get rid of the diriv for so many reasons.

so, who do I have to lobby :-)

[rfjakob]

2 Petabytes?

Anyway, this could be possible in theory:

1. Copy your gocryptfs.conf to a new empty folder
2. Remove the DirIV feature flag
3. Create all files that you have, but as empty files. This gives you a directory structure "skeleton"
4. In your original filesystem, rename all encrypted files to match the skeleton, remove DirIV feature flag from gocryptfs.conf, delete all gocryptfs.diriv files

This is off the top of my head, so maybe try it with only one Petabyte first ;)

[loungebob]

2.31PB to be precise. I hoard.

I also am no good at all at scripting and scripts and stuff.

I was hoping for a one button automated process or something similarily simple. Bitte, bitte, bitteeee 🥰

Else, I’ll wait, maybe more demand arises :-) or I go and lobby bailey over at the windows version. Me windows drone.

Or, if I feel particularily brave, I’ll try your thing above at some point. Thanks for listening though!

[loungebob]

oh yay it's a feature request now! saturdaynightfeverdancingmanemoji