Is it required to manually run e2fsck at regular intervals?
Is it required to manually run the e2fsck (used to check a Linux ext2/ext3/ext4 file system) at regular intervals, an if so, how often should I run it?
Or can I rely on a present S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology) system to report any errors, and then run e2fsck in case errors are reported?
linux hard-drive smart ext4 ext3
asked Jan 5 at 17:08
EquipDevEquipDev
14717
add a comment |
Is it required to manually run the e2fsck (used to check a Linux ext2/ext3/ext4 file system) at regular intervals, an if so, how often should I run it?
Or can I rely on a present S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology) system to report any errors, and then run e2fsck in case errors are reported?
linux hard-drive smart ext4 ext3
asked Jan 5 at 17:08
EquipDevEquipDev
14717
@KamilMaciorowski: Thanks for the comments, which lead to the improvements. I also read through and appreciate your previous answer referenced in the link.
– EquipDev
Jan 6 at 19:57
add a comment |
Is it required to manually run the e2fsck (used to check a Linux ext2/ext3/ext4 file system) at regular intervals, an if so, how often should I run it?
Or can I rely on a present S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology) system to report any errors, and then run e2fsck in case errors are reported?
linux hard-drive smart ext4 ext3
asked Jan 5 at 17:08
EquipDevEquipDev
14717
Is it required to manually run the e2fsck (used to check a Linux ext2/ext3/ext4 file system) at regular intervals, an if so, how often should I run it?
Or can I rely on a present S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology) system to report any errors, and then run e2fsck in case errors are reported?
linux hard-drive smart ext4 ext3
linux hard-drive smart ext4 ext3
asked Jan 5 at 17:08
EquipDevEquipDev
14717
asked Jan 5 at 17:08
EquipDevEquipDev
14717
asked Jan 5 at 17:08
EquipDevEquipDev
14717
asked Jan 5 at 17:08
EquipDevEquipDev
14717
asked Jan 5 at 17:08
EquipDevEquipDev
14717
14717
@KamilMaciorowski: Thanks for the comments, which lead to the improvements. I also read through and appreciate your previous answer referenced in the link.
– EquipDev
Jan 6 at 19:57
add a comment |
@KamilMaciorowski: Thanks for the comments, which lead to the improvements. I also read through and appreciate your previous answer referenced in the link.
– EquipDev
Jan 6 at 19:57
@KamilMaciorowski: Thanks for the comments, which lead to the improvements. I also read through and appreciate your previous answer referenced in the link.
– EquipDev
Jan 6 at 19:57
@KamilMaciorowski: Thanks for the comments, which lead to the improvements. I also read through and appreciate your previous answer referenced in the link.
– EquipDev
Jan 6 at 19:57
add a comment |
1 Answer
1
active
oldest
votes
SMART and e2fsck check different aspects of your harddisk.
SMART checks your harddive’s hardware (eg spinup time, bad blocks, temperature, working hours, etc.) e2fsck checks the integrity of the contents of your harddrive.
Let me introduce two more Linux commands here: fsck (man page) and tune2fs (man page).
fsckis a generic wrapper around several filesystem specific checkers, such ase2fsck.
tune2fssets different parameters for filesystems, among which the interval and/or frequency for which file systems are checked.
The manual of tune2fs is very clear about regularly checking the filesystem:
It is strongly recommended that either -c (mount-count-dependent) or
-i (time-dependent) checking be enabled to force periodic full e2fsck(8) checking of the filesystem. Failure to do so may lead to
filesystem corruption (due to bad disks, cables, memory, or kernel
bugs) going unnoticed, ultimately resulting in data loss or
corruption.
To check the current settings of your filesystem, you can use the following command (edit the device /dev/sda1 as appropriate):
sudo tune2fs -l /dev/sda1 | egrep -h 'Maximum mount count|Check interval|Last checked'
This will return the two parameters which can be set by the -c and -i parameters of tune2fs and the last time the filesystem is checked. To set those parameters to different values, you can use the following command (edit the device /dev/sda1 as appropriate) to check the filesystem every 8 mounts or once a month (whichever comes first):
sudo tune2fs -c 8 -i "1m" /dev/sda1
answered Jan 5 at 17:25
agtoeveragtoever
5,07911330
Thanks, I appreciate the manual reference, and I now understand how to read it.
– EquipDev
Jan 5 at 17:44
I edited the answer based on the insights of @KamilMaciorowski; @KamilMaciorowski: thanks for pointing this out!
– agtoever
Jan 5 at 18:46
Thanks for the update, and I can see that there are substantial changes for the previous (accepted) answer. I appreciate your update to the improved revision.
– EquipDev
Jan 6 at 19:56
add a comment |
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
});
}
});
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%2f1390938%2fis-it-required-to-manually-run-e2fsck-at-regular-intervals%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
SMART and e2fsck check different aspects of your harddisk.
SMART checks your harddive’s hardware (eg spinup time, bad blocks, temperature, working hours, etc.) e2fsck checks the integrity of the contents of your harddrive.
Let me introduce two more Linux commands here: fsck (man page) and tune2fs (man page).
fsckis a generic wrapper around several filesystem specific checkers, such ase2fsck.
tune2fssets different parameters for filesystems, among which the interval and/or frequency for which file systems are checked.
The manual of tune2fs is very clear about regularly checking the filesystem:
It is strongly recommended that either -c (mount-count-dependent) or
-i (time-dependent) checking be enabled to force periodic full e2fsck(8) checking of the filesystem. Failure to do so may lead to
filesystem corruption (due to bad disks, cables, memory, or kernel
bugs) going unnoticed, ultimately resulting in data loss or
corruption.
To check the current settings of your filesystem, you can use the following command (edit the device /dev/sda1 as appropriate):
sudo tune2fs -l /dev/sda1 | egrep -h 'Maximum mount count|Check interval|Last checked'
This will return the two parameters which can be set by the -c and -i parameters of tune2fs and the last time the filesystem is checked. To set those parameters to different values, you can use the following command (edit the device /dev/sda1 as appropriate) to check the filesystem every 8 mounts or once a month (whichever comes first):
sudo tune2fs -c 8 -i "1m" /dev/sda1
answered Jan 5 at 17:25
agtoeveragtoever
5,07911330
Thanks, I appreciate the manual reference, and I now understand how to read it.
– EquipDev
Jan 5 at 17:44
I edited the answer based on the insights of @KamilMaciorowski; @KamilMaciorowski: thanks for pointing this out!
– agtoever
Jan 5 at 18:46
Thanks for the update, and I can see that there are substantial changes for the previous (accepted) answer. I appreciate your update to the improved revision.
– EquipDev
Jan 6 at 19:56
add a comment |
SMART and e2fsck check different aspects of your harddisk.
SMART checks your harddive’s hardware (eg spinup time, bad blocks, temperature, working hours, etc.) e2fsck checks the integrity of the contents of your harddrive.
Let me introduce two more Linux commands here: fsck (man page) and tune2fs (man page).
fsckis a generic wrapper around several filesystem specific checkers, such ase2fsck.
tune2fssets different parameters for filesystems, among which the interval and/or frequency for which file systems are checked.
The manual of tune2fs is very clear about regularly checking the filesystem:
It is strongly recommended that either -c (mount-count-dependent) or
-i (time-dependent) checking be enabled to force periodic full e2fsck(8) checking of the filesystem. Failure to do so may lead to
filesystem corruption (due to bad disks, cables, memory, or kernel
bugs) going unnoticed, ultimately resulting in data loss or
corruption.
To check the current settings of your filesystem, you can use the following command (edit the device /dev/sda1 as appropriate):
sudo tune2fs -l /dev/sda1 | egrep -h 'Maximum mount count|Check interval|Last checked'
This will return the two parameters which can be set by the -c and -i parameters of tune2fs and the last time the filesystem is checked. To set those parameters to different values, you can use the following command (edit the device /dev/sda1 as appropriate) to check the filesystem every 8 mounts or once a month (whichever comes first):
sudo tune2fs -c 8 -i "1m" /dev/sda1
answered Jan 5 at 17:25
agtoeveragtoever
5,07911330
Thanks, I appreciate the manual reference, and I now understand how to read it.
– EquipDev
Jan 5 at 17:44
I edited the answer based on the insights of @KamilMaciorowski; @KamilMaciorowski: thanks for pointing this out!
– agtoever
Jan 5 at 18:46
Thanks for the update, and I can see that there are substantial changes for the previous (accepted) answer. I appreciate your update to the improved revision.
– EquipDev
Jan 6 at 19:56
add a comment |
SMART and e2fsck check different aspects of your harddisk.
SMART checks your harddive’s hardware (eg spinup time, bad blocks, temperature, working hours, etc.) e2fsck checks the integrity of the contents of your harddrive.
Let me introduce two more Linux commands here: fsck (man page) and tune2fs (man page).
fsckis a generic wrapper around several filesystem specific checkers, such ase2fsck.
tune2fssets different parameters for filesystems, among which the interval and/or frequency for which file systems are checked.
The manual of tune2fs is very clear about regularly checking the filesystem:
It is strongly recommended that either -c (mount-count-dependent) or
-i (time-dependent) checking be enabled to force periodic full e2fsck(8) checking of the filesystem. Failure to do so may lead to
filesystem corruption (due to bad disks, cables, memory, or kernel
bugs) going unnoticed, ultimately resulting in data loss or
corruption.
To check the current settings of your filesystem, you can use the following command (edit the device /dev/sda1 as appropriate):
sudo tune2fs -l /dev/sda1 | egrep -h 'Maximum mount count|Check interval|Last checked'
This will return the two parameters which can be set by the -c and -i parameters of tune2fs and the last time the filesystem is checked. To set those parameters to different values, you can use the following command (edit the device /dev/sda1 as appropriate) to check the filesystem every 8 mounts or once a month (whichever comes first):
sudo tune2fs -c 8 -i "1m" /dev/sda1
answered Jan 5 at 17:25
agtoeveragtoever
5,07911330
SMART and e2fsck check different aspects of your harddisk.
SMART checks your harddive’s hardware (eg spinup time, bad blocks, temperature, working hours, etc.) e2fsck checks the integrity of the contents of your harddrive.
Let me introduce two more Linux commands here: fsck (man page) and tune2fs (man page).
fsckis a generic wrapper around several filesystem specific checkers, such ase2fsck.
tune2fssets different parameters for filesystems, among which the interval and/or frequency for which file systems are checked.
The manual of tune2fs is very clear about regularly checking the filesystem:
It is strongly recommended that either -c (mount-count-dependent) or
-i (time-dependent) checking be enabled to force periodic full e2fsck(8) checking of the filesystem. Failure to do so may lead to
filesystem corruption (due to bad disks, cables, memory, or kernel
bugs) going unnoticed, ultimately resulting in data loss or
corruption.
To check the current settings of your filesystem, you can use the following command (edit the device /dev/sda1 as appropriate):
sudo tune2fs -l /dev/sda1 | egrep -h 'Maximum mount count|Check interval|Last checked'
This will return the two parameters which can be set by the -c and -i parameters of tune2fs and the last time the filesystem is checked. To set those parameters to different values, you can use the following command (edit the device /dev/sda1 as appropriate) to check the filesystem every 8 mounts or once a month (whichever comes first):
sudo tune2fs -c 8 -i "1m" /dev/sda1
answered Jan 5 at 17:25
agtoeveragtoever
5,07911330
edited Jan 6 at 16:42
answered Jan 5 at 17:25
agtoeveragtoever
5,07911330
answered Jan 5 at 17:25
agtoeveragtoever
5,07911330
answered Jan 5 at 17:25
agtoeveragtoever
5,07911330
5,07911330
Thanks, I appreciate the manual reference, and I now understand how to read it.
– EquipDev
Jan 5 at 17:44
I edited the answer based on the insights of @KamilMaciorowski; @KamilMaciorowski: thanks for pointing this out!
– agtoever
Jan 5 at 18:46
Thanks for the update, and I can see that there are substantial changes for the previous (accepted) answer. I appreciate your update to the improved revision.
– EquipDev
Jan 6 at 19:56
add a comment |
Thanks, I appreciate the manual reference, and I now understand how to read it.
– EquipDev
Jan 5 at 17:44
I edited the answer based on the insights of @KamilMaciorowski; @KamilMaciorowski: thanks for pointing this out!
– agtoever
Jan 5 at 18:46
Thanks for the update, and I can see that there are substantial changes for the previous (accepted) answer. I appreciate your update to the improved revision.
– EquipDev
Jan 6 at 19:56
Thanks, I appreciate the manual reference, and I now understand how to read it.
– EquipDev
Jan 5 at 17:44
Thanks, I appreciate the manual reference, and I now understand how to read it.
– EquipDev
Jan 5 at 17:44
I edited the answer based on the insights of @KamilMaciorowski; @KamilMaciorowski: thanks for pointing this out!
– agtoever
Jan 5 at 18:46
I edited the answer based on the insights of @KamilMaciorowski; @KamilMaciorowski: thanks for pointing this out!
– agtoever
Jan 5 at 18:46
Thanks for the update, and I can see that there are substantial changes for the previous (accepted) answer. I appreciate your update to the improved revision.
– EquipDev
Jan 6 at 19:56
Thanks for the update, and I can see that there are substantial changes for the previous (accepted) answer. I appreciate your update to the improved revision.
– EquipDev
Jan 6 at 19:56
add a comment |
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.
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%2f1390938%2fis-it-required-to-manually-run-e2fsck-at-regular-intervals%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
@KamilMaciorowski: Thanks for the comments, which lead to the improvements. I also read through and appreciate your previous answer referenced in the link.
– EquipDev
Jan 6 at 19:57