Is it risky to completely fill up a hdd with a veracrypt container?
1
I always use all my hard drives only between 75% and 80% of their capacities (after having formatting them),
I leave the rest to allow windows to properly perform maintenance on my hard drives.
I would like to create a veracrypt container of 99 GB (I do not want to encrypt the entire partition or the entire hard disk)
in a 100 GB hard drive, is it dangerous to damage my hard drive?
Will my datas be more at a risk than if i create a veracrypt container of 80 GB?
Is it risky to fill a veracrypt container to the limit of its capacity?
What are the worst mistakes to avoid with a veracrypt container?
container veracrypt
asked Dec 17 '18 at 23:05
Gabriel PGabriel P
61
add a comment |
1
I always use all my hard drives only between 75% and 80% of their capacities (after having formatting them),
I leave the rest to allow windows to properly perform maintenance on my hard drives.
I would like to create a veracrypt container of 99 GB (I do not want to encrypt the entire partition or the entire hard disk)
in a 100 GB hard drive, is it dangerous to damage my hard drive?
Will my datas be more at a risk than if i create a veracrypt container of 80 GB?
Is it risky to fill a veracrypt container to the limit of its capacity?
What are the worst mistakes to avoid with a veracrypt container?
container veracrypt
asked Dec 17 '18 at 23:05
Gabriel PGabriel P
61
Welcome to Superuser! Your question seems to have questions inside a question and borderline opinion based. Try focusing your question on one specific issue to get a more detailed responses. Head over to ask your own question page to get some handy hints on how to ask the best question you can regarding your specific issue.
– angelofdev
Dec 17 '18 at 23:42
Why are you against using FDE?
– Ramhound
Dec 18 '18 at 0:12
I don't think it is risky. The 80% watermark is a filesystem management thing, as when filesystems get full they tend to fragment and take a big performance hit. This probably does not apply as much when using a file as a block device - but you might want to defragment the drive once the file is created and avoid creating it as a sparse file.
– davidgo
Dec 18 '18 at 10:44
Somehow, i am under the impression that FDE bring a higher probability of mechanical problems in the hdd, and associate the hdd with a specific hardware config (if my mobo die then i lost all my datas) , and with a container, i can copy the entire file to another hdd on my backup server, then (when needed) i open both container and synchronise them with freefilesync.
– Gabriel P
Dec 18 '18 at 18:52
I agree that "as when filesystems get full they tend to fragment and take a big performance hit" .I think that i will keep on not using more than 75% to 80%, for safety and for a higher performance. But then, if a container is the same as a hdd, i wonder if i should also not use more than 75% to 80% of the capacity of the container?, wich would mean 80% of a container the size of 80% of the size of my hdd (100 GB), 100GB x 80% (80 GB) x 80% = 64GB, i loose 33% of the capacity of the hdd, but it looks like the safest way
– Gabriel P
Dec 18 '18 at 19:05
add a comment |
1
1
1
I always use all my hard drives only between 75% and 80% of their capacities (after having formatting them),
I leave the rest to allow windows to properly perform maintenance on my hard drives.
I would like to create a veracrypt container of 99 GB (I do not want to encrypt the entire partition or the entire hard disk)
in a 100 GB hard drive, is it dangerous to damage my hard drive?
Will my datas be more at a risk than if i create a veracrypt container of 80 GB?
Is it risky to fill a veracrypt container to the limit of its capacity?
What are the worst mistakes to avoid with a veracrypt container?
container veracrypt
asked Dec 17 '18 at 23:05
Gabriel PGabriel P
61
I always use all my hard drives only between 75% and 80% of their capacities (after having formatting them),
I leave the rest to allow windows to properly perform maintenance on my hard drives.
I would like to create a veracrypt container of 99 GB (I do not want to encrypt the entire partition or the entire hard disk)
in a 100 GB hard drive, is it dangerous to damage my hard drive?
Will my datas be more at a risk than if i create a veracrypt container of 80 GB?
Is it risky to fill a veracrypt container to the limit of its capacity?
What are the worst mistakes to avoid with a veracrypt container?
container veracrypt
container veracrypt
asked Dec 17 '18 at 23:05
Gabriel PGabriel P
61
asked Dec 17 '18 at 23:05
Gabriel PGabriel P
61
asked Dec 17 '18 at 23:05
Gabriel PGabriel P
61
asked Dec 17 '18 at 23:05
Gabriel PGabriel P
61
asked Dec 17 '18 at 23:05
Gabriel PGabriel P
61
61
Welcome to Superuser! Your question seems to have questions inside a question and borderline opinion based. Try focusing your question on one specific issue to get a more detailed responses. Head over to ask your own question page to get some handy hints on how to ask the best question you can regarding your specific issue.
– angelofdev
Dec 17 '18 at 23:42
Why are you against using FDE?
– Ramhound
Dec 18 '18 at 0:12
I don't think it is risky. The 80% watermark is a filesystem management thing, as when filesystems get full they tend to fragment and take a big performance hit. This probably does not apply as much when using a file as a block device - but you might want to defragment the drive once the file is created and avoid creating it as a sparse file.
– davidgo
Dec 18 '18 at 10:44
Somehow, i am under the impression that FDE bring a higher probability of mechanical problems in the hdd, and associate the hdd with a specific hardware config (if my mobo die then i lost all my datas) , and with a container, i can copy the entire file to another hdd on my backup server, then (when needed) i open both container and synchronise them with freefilesync.
– Gabriel P
Dec 18 '18 at 18:52
I agree that "as when filesystems get full they tend to fragment and take a big performance hit" .I think that i will keep on not using more than 75% to 80%, for safety and for a higher performance. But then, if a container is the same as a hdd, i wonder if i should also not use more than 75% to 80% of the capacity of the container?, wich would mean 80% of a container the size of 80% of the size of my hdd (100 GB), 100GB x 80% (80 GB) x 80% = 64GB, i loose 33% of the capacity of the hdd, but it looks like the safest way
– Gabriel P
Dec 18 '18 at 19:05
add a comment |
Welcome to Superuser! Your question seems to have questions inside a question and borderline opinion based. Try focusing your question on one specific issue to get a more detailed responses. Head over to ask your own question page to get some handy hints on how to ask the best question you can regarding your specific issue.
– angelofdev
Dec 17 '18 at 23:42
Why are you against using FDE?
– Ramhound
Dec 18 '18 at 0:12
I don't think it is risky. The 80% watermark is a filesystem management thing, as when filesystems get full they tend to fragment and take a big performance hit. This probably does not apply as much when using a file as a block device - but you might want to defragment the drive once the file is created and avoid creating it as a sparse file.
– davidgo
Dec 18 '18 at 10:44
Somehow, i am under the impression that FDE bring a higher probability of mechanical problems in the hdd, and associate the hdd with a specific hardware config (if my mobo die then i lost all my datas) , and with a container, i can copy the entire file to another hdd on my backup server, then (when needed) i open both container and synchronise them with freefilesync.
– Gabriel P
Dec 18 '18 at 18:52
I agree that "as when filesystems get full they tend to fragment and take a big performance hit" .I think that i will keep on not using more than 75% to 80%, for safety and for a higher performance. But then, if a container is the same as a hdd, i wonder if i should also not use more than 75% to 80% of the capacity of the container?, wich would mean 80% of a container the size of 80% of the size of my hdd (100 GB), 100GB x 80% (80 GB) x 80% = 64GB, i loose 33% of the capacity of the hdd, but it looks like the safest way
– Gabriel P
Dec 18 '18 at 19:05
Welcome to Superuser! Your question seems to have questions inside a question and borderline opinion based. Try focusing your question on one specific issue to get a more detailed responses. Head over to ask your own question page to get some handy hints on how to ask the best question you can regarding your specific issue.
– angelofdev
Dec 17 '18 at 23:42
Welcome to Superuser! Your question seems to have questions inside a question and borderline opinion based. Try focusing your question on one specific issue to get a more detailed responses. Head over to ask your own question page to get some handy hints on how to ask the best question you can regarding your specific issue.
– angelofdev
Dec 17 '18 at 23:42
Why are you against using FDE?
– Ramhound
Dec 18 '18 at 0:12
Why are you against using FDE?
– Ramhound
Dec 18 '18 at 0:12
I don't think it is risky. The 80% watermark is a filesystem management thing, as when filesystems get full they tend to fragment and take a big performance hit. This probably does not apply as much when using a file as a block device - but you might want to defragment the drive once the file is created and avoid creating it as a sparse file.
– davidgo
Dec 18 '18 at 10:44
I don't think it is risky. The 80% watermark is a filesystem management thing, as when filesystems get full they tend to fragment and take a big performance hit. This probably does not apply as much when using a file as a block device - but you might want to defragment the drive once the file is created and avoid creating it as a sparse file.
– davidgo
Dec 18 '18 at 10:44
Somehow, i am under the impression that FDE bring a higher probability of mechanical problems in the hdd, and associate the hdd with a specific hardware config (if my mobo die then i lost all my datas) , and with a container, i can copy the entire file to another hdd on my backup server, then (when needed) i open both container and synchronise them with freefilesync.
– Gabriel P
Dec 18 '18 at 18:52
Somehow, i am under the impression that FDE bring a higher probability of mechanical problems in the hdd, and associate the hdd with a specific hardware config (if my mobo die then i lost all my datas) , and with a container, i can copy the entire file to another hdd on my backup server, then (when needed) i open both container and synchronise them with freefilesync.
– Gabriel P
Dec 18 '18 at 18:52
I agree that "as when filesystems get full they tend to fragment and take a big performance hit" .I think that i will keep on not using more than 75% to 80%, for safety and for a higher performance. But then, if a container is the same as a hdd, i wonder if i should also not use more than 75% to 80% of the capacity of the container?, wich would mean 80% of a container the size of 80% of the size of my hdd (100 GB), 100GB x 80% (80 GB) x 80% = 64GB, i loose 33% of the capacity of the hdd, but it looks like the safest way
– Gabriel P
Dec 18 '18 at 19:05
I agree that "as when filesystems get full they tend to fragment and take a big performance hit" .I think that i will keep on not using more than 75% to 80%, for safety and for a higher performance. But then, if a container is the same as a hdd, i wonder if i should also not use more than 75% to 80% of the capacity of the container?, wich would mean 80% of a container the size of 80% of the size of my hdd (100 GB), 100GB x 80% (80 GB) x 80% = 64GB, i loose 33% of the capacity of the hdd, but it looks like the safest way
– Gabriel P
Dec 18 '18 at 19:05
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1385383%2fis-it-risky-to-completely-fill-up-a-hdd-with-a-veracrypt-container%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1385383%2fis-it-risky-to-completely-fill-up-a-hdd-with-a-veracrypt-container%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Welcome to Superuser! Your question seems to have questions inside a question and borderline opinion based. Try focusing your question on one specific issue to get a more detailed responses. Head over to ask your own question page to get some handy hints on how to ask the best question you can regarding your specific issue.
– angelofdev
Dec 17 '18 at 23:42
Why are you against using FDE?
– Ramhound
Dec 18 '18 at 0:12
I don't think it is risky. The 80% watermark is a filesystem management thing, as when filesystems get full they tend to fragment and take a big performance hit. This probably does not apply as much when using a file as a block device - but you might want to defragment the drive once the file is created and avoid creating it as a sparse file.
– davidgo
Dec 18 '18 at 10:44
Somehow, i am under the impression that FDE bring a higher probability of mechanical problems in the hdd, and associate the hdd with a specific hardware config (if my mobo die then i lost all my datas) , and with a container, i can copy the entire file to another hdd on my backup server, then (when needed) i open both container and synchronise them with freefilesync.
– Gabriel P
Dec 18 '18 at 18:52
I agree that "as when filesystems get full they tend to fragment and take a big performance hit" .I think that i will keep on not using more than 75% to 80%, for safety and for a higher performance. But then, if a container is the same as a hdd, i wonder if i should also not use more than 75% to 80% of the capacity of the container?, wich would mean 80% of a container the size of 80% of the size of my hdd (100 GB), 100GB x 80% (80 GB) x 80% = 64GB, i loose 33% of the capacity of the hdd, but it looks like the safest way
– Gabriel P
Dec 18 '18 at 19:05