A remotely mounted veracrypt volume stored on the main array performs monstrously slow. Locally, it bursts some amount of data to make it appear to the user as being super fast, but after said amount, it grinds down to like 4MB/s.
This only occurs with the combination of being stored on Unraid AND and using veracrypt.
In other words, normal files perform well. And a veracrypt volume mounted on a local disk performs fine as well. It's the combination that kills performance (after faking it with that bursting behaviour).
This has been reported over at veracrypt as well: https://github.com/veracrypt/VeraCrypt/issues/1277
I'm running the latest stable Unraid, but this has been happening for a very long time. I can't remember when I first noticed this behaviour.
Some people claim it doesn't kill performance when a volume is stored on a non-raid volume, and I guess in unraid-terms that would be a share without parity. I don't have enough disks laying around to test that. I do have SSDs in a ZFS raid-5 array, and storing the volume on there causes the same troubles.
With respect, I'm hoping you, the unraid devs, and the veracrypt devs can work out a solution together, or at least the root cause. I don't think it's very productive if I have to play the middle man.
Recommended Comments
There are no comments to display.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.