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

[Feature Request] Allow setting cryfs block size #278

Open
automorphism88 opened this issue Apr 5, 2024 · 2 comments
Open

[Feature Request] Allow setting cryfs block size #278

automorphism88 opened this issue Apr 5, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@automorphism88
Copy link

It appears that CryFS volumes created with DroidFS always use the default block size (currently 16k). But cryfs allows users to specify the block size with the --blocksize command line argument. Depending on the nature of the files stored and the underlying filesystem and device, users might have good reason to want to use a different block size. For example, for an exFAT filesystem, the usual block size is 128k. A CryFS volume stored there which uses the default block size of 16k will be wasting 7/8ths of the space in each filesystem block, since it will be creating files of size 16k that take up an entire 128k block on disk. In such a case, it would be far more space-efficient to use --blocksize 131072 when creating the CryFS filesystem. It seems that this is a primary use case for DroidFS, given that on an unrooted phone, you can't mount external storage formatted with ext4 or f2fs.

@hardcore-sushi
Copy link
Owner

Yes. It's also tracked there: #14.

@hardcore-sushi hardcore-sushi added the enhancement New feature or request label Apr 7, 2024
@serrq
Copy link

serrq commented Sep 29, 2024

Even 256k in my opinion. I have 556 items for just 8mb database. This increase time to copy a database.

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

No branches or pull requests

3 participants