Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration of filesystems encrypted with PRE-1.4.4.0 version to latest version without diriv files #164

Open
san-r opened this issue Jun 11, 2022 · 7 comments

Comments

@san-r
Copy link

san-r commented Jun 11, 2022

cppcryptfs version 1.4.4.0 implements the "deterministic names" feature which makes diriv files unnecessary. This is very significant for me.

I have several folders encrypted with previous cppcryptfs version which have diriv files. My question is - Is there a faster way to convert those encrypted folders to the newer version (without diriv files) other than mounting both older and newer filesystems and then copying all files from older location to newer location?

@san-r san-r changed the title Migration of filesystems encrypted with PRE-1.4.4.0 version to the current 1.4.4.0 version Migration of filesystems encrypted with PRE-1.4.4.0 version to latest version without diriv files Jun 12, 2022
@bailey27
Copy link
Owner

Currently, the only way to migrate is to copy everything.

@loungebob
Copy link

no. nooo. nooooooo. I was afraid something like this was going to happen. I need a migration path for multiple Petabytes of gocryptfs volumes. copying is just not an option. I'll go and lobby jakob.

@san-r
Copy link
Author

san-r commented Jun 24, 2022

I was kind of hoping that the migration process should involve just -

  • updating the config file
  • deleting the diriv files
  • without touching the encrypted data files.

@loungebob
Copy link

me too.

@ccchan234
Copy link

ccchan234 commented Jul 14, 2022

#metoo

it would be nice if implement of "longnamemax" didn't need to COPY files to change container too.

I got around 30TB files on gdrive.

thanks

@yfdyh000
Copy link
Contributor

yfdyh000 commented Jul 14, 2022

I think this is doable by retrofitting the https://github.com/slackner/gocryptfs-inspect. But I don't have enough time to do this. In any case, I recommend whoever implements it to keep shadows, logs and tests intact in case any files are missing or crash halfway through.

In short, full rename log, renaming old diriv files to .bak first and backup them, and let user check number / names of files inside volume before cleaning.

@yfdyh000
Copy link
Contributor

#metoo

it would be nice if implement of "longnamemax" didn't need to COPY files to change container too.

I got around 30TB files on gdrive.

thanks

Upvoted this, I've encountered sync failures due to max paths exceeding sync software limits, from long base path, no way to change after the volume is created, I had to shorten the naming of existing folders to the shortest possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants