Does constant writing to “files” in `/proc` or `/sys` reduce the life of my SSD due to its limited number...
My laptop has a SSD drive and I run a script which writes every other second to /sys/class/thermal/cooling_device4/cur_state. I don't think this would count as writing to the SSD and thus reducing its remaining number of writing cycles, since procfs and sysfs are virtual filesystems.
Or am I overlooking something and this is an issue?
linux files filesystems proc ssd
asked Dec 8 at 11:29
Jayjayyy
2258
add a comment |
My laptop has a SSD drive and I run a script which writes every other second to /sys/class/thermal/cooling_device4/cur_state. I don't think this would count as writing to the SSD and thus reducing its remaining number of writing cycles, since procfs and sysfs are virtual filesystems.
Or am I overlooking something and this is an issue?
linux files filesystems proc ssd
asked Dec 8 at 11:29
Jayjayyy
2258
1
You are right. Not writing to the SSD doesn't count as writing to the SSD. The same would hold for a RAM drive such astmpfs.
– glglgl
Dec 8 at 12:29
add a comment |
My laptop has a SSD drive and I run a script which writes every other second to /sys/class/thermal/cooling_device4/cur_state. I don't think this would count as writing to the SSD and thus reducing its remaining number of writing cycles, since procfs and sysfs are virtual filesystems.
Or am I overlooking something and this is an issue?
linux files filesystems proc ssd
asked Dec 8 at 11:29
Jayjayyy
2258
My laptop has a SSD drive and I run a script which writes every other second to /sys/class/thermal/cooling_device4/cur_state. I don't think this would count as writing to the SSD and thus reducing its remaining number of writing cycles, since procfs and sysfs are virtual filesystems.
Or am I overlooking something and this is an issue?
linux files filesystems proc ssd
linux files filesystems proc ssd
asked Dec 8 at 11:29
Jayjayyy
2258
asked Dec 8 at 11:29
Jayjayyy
2258
asked Dec 8 at 11:29
Jayjayyy
2258
asked Dec 8 at 11:29
Jayjayyy
2258
asked Dec 8 at 11:29
Jayjayyy
2258
2258
1
You are right. Not writing to the SSD doesn't count as writing to the SSD. The same would hold for a RAM drive such astmpfs.
– glglgl
Dec 8 at 12:29
add a comment |
1
You are right. Not writing to the SSD doesn't count as writing to the SSD. The same would hold for a RAM drive such astmpfs.
– glglgl
Dec 8 at 12:29
1
1
You are right. Not writing to the SSD doesn't count as writing to the SSD. The same would hold for a RAM drive such as
tmpfs.– glglgl
Dec 8 at 12:29
You are right. Not writing to the SSD doesn't count as writing to the SSD. The same would hold for a RAM drive such as
tmpfs.– glglgl
Dec 8 at 12:29
add a comment |
1 Answer
1
active
oldest
votes
You're entirely correct: virtual filesystems like procfs and sysfs are not stored on disk at all. Their contents are generated on-demand based on kernel data structures in RAM, and writing into them (if possible at all) translates into making changes to in-memory kernel settings.
Writing to procfs or sysfs cannot possibly have any impact to SSD lifetime.
answered Dec 8 at 11:48
telcoM
15.8k12143
But if I'm nit-picking, is that possible writing to /sys control the state of your SSD controller so it will have some impact to the hardware?
– 炸鱼薯条德里克
Dec 8 at 12:39
1
No, repeated writing to/sys/class/thermal(as the original poster asked) won't have any impact to SSD hardware :-) To have any significant effect, you would have to write into/sys/block/<device name>/and basically deliberately pick the worst possible settings for a SSD. Even so, modern consumer SSDs have plenty of writing cycles and efficient wear leveling: typically the vendors promise that you could write more than a terabyte every day and the SSD would still have the expected lifetime. Of course, sometimes those promises can be mistaken or less than truthful otherwise...
– telcoM
Dec 8 at 12:53
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f486750%2fdoes-constant-writing-to-files-in-proc-or-sys-reduce-the-life-of-my-ssd%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
You're entirely correct: virtual filesystems like procfs and sysfs are not stored on disk at all. Their contents are generated on-demand based on kernel data structures in RAM, and writing into them (if possible at all) translates into making changes to in-memory kernel settings.
Writing to procfs or sysfs cannot possibly have any impact to SSD lifetime.
answered Dec 8 at 11:48
telcoM
15.8k12143
But if I'm nit-picking, is that possible writing to /sys control the state of your SSD controller so it will have some impact to the hardware?
– 炸鱼薯条德里克
Dec 8 at 12:39
1
No, repeated writing to/sys/class/thermal(as the original poster asked) won't have any impact to SSD hardware :-) To have any significant effect, you would have to write into/sys/block/<device name>/and basically deliberately pick the worst possible settings for a SSD. Even so, modern consumer SSDs have plenty of writing cycles and efficient wear leveling: typically the vendors promise that you could write more than a terabyte every day and the SSD would still have the expected lifetime. Of course, sometimes those promises can be mistaken or less than truthful otherwise...
– telcoM
Dec 8 at 12:53
add a comment |
You're entirely correct: virtual filesystems like procfs and sysfs are not stored on disk at all. Their contents are generated on-demand based on kernel data structures in RAM, and writing into them (if possible at all) translates into making changes to in-memory kernel settings.
Writing to procfs or sysfs cannot possibly have any impact to SSD lifetime.
answered Dec 8 at 11:48
telcoM
15.8k12143
But if I'm nit-picking, is that possible writing to /sys control the state of your SSD controller so it will have some impact to the hardware?
– 炸鱼薯条德里克
Dec 8 at 12:39
1
No, repeated writing to/sys/class/thermal(as the original poster asked) won't have any impact to SSD hardware :-) To have any significant effect, you would have to write into/sys/block/<device name>/and basically deliberately pick the worst possible settings for a SSD. Even so, modern consumer SSDs have plenty of writing cycles and efficient wear leveling: typically the vendors promise that you could write more than a terabyte every day and the SSD would still have the expected lifetime. Of course, sometimes those promises can be mistaken or less than truthful otherwise...
– telcoM
Dec 8 at 12:53
add a comment |
You're entirely correct: virtual filesystems like procfs and sysfs are not stored on disk at all. Their contents are generated on-demand based on kernel data structures in RAM, and writing into them (if possible at all) translates into making changes to in-memory kernel settings.
Writing to procfs or sysfs cannot possibly have any impact to SSD lifetime.
answered Dec 8 at 11:48
telcoM
15.8k12143
You're entirely correct: virtual filesystems like procfs and sysfs are not stored on disk at all. Their contents are generated on-demand based on kernel data structures in RAM, and writing into them (if possible at all) translates into making changes to in-memory kernel settings.
Writing to procfs or sysfs cannot possibly have any impact to SSD lifetime.
answered Dec 8 at 11:48
telcoM
15.8k12143
answered Dec 8 at 11:48
telcoM
15.8k12143
answered Dec 8 at 11:48
telcoM
15.8k12143
answered Dec 8 at 11:48
telcoM
15.8k12143
15.8k12143
But if I'm nit-picking, is that possible writing to /sys control the state of your SSD controller so it will have some impact to the hardware?
– 炸鱼薯条德里克
Dec 8 at 12:39
1
No, repeated writing to/sys/class/thermal(as the original poster asked) won't have any impact to SSD hardware :-) To have any significant effect, you would have to write into/sys/block/<device name>/and basically deliberately pick the worst possible settings for a SSD. Even so, modern consumer SSDs have plenty of writing cycles and efficient wear leveling: typically the vendors promise that you could write more than a terabyte every day and the SSD would still have the expected lifetime. Of course, sometimes those promises can be mistaken or less than truthful otherwise...
– telcoM
Dec 8 at 12:53
add a comment |
But if I'm nit-picking, is that possible writing to /sys control the state of your SSD controller so it will have some impact to the hardware?
– 炸鱼薯条德里克
Dec 8 at 12:39
1
No, repeated writing to/sys/class/thermal(as the original poster asked) won't have any impact to SSD hardware :-) To have any significant effect, you would have to write into/sys/block/<device name>/and basically deliberately pick the worst possible settings for a SSD. Even so, modern consumer SSDs have plenty of writing cycles and efficient wear leveling: typically the vendors promise that you could write more than a terabyte every day and the SSD would still have the expected lifetime. Of course, sometimes those promises can be mistaken or less than truthful otherwise...
– telcoM
Dec 8 at 12:53
But if I'm nit-picking, is that possible writing to /sys control the state of your SSD controller so it will have some impact to the hardware?
– 炸鱼薯条德里克
Dec 8 at 12:39
But if I'm nit-picking, is that possible writing to /sys control the state of your SSD controller so it will have some impact to the hardware?
– 炸鱼薯条德里克
Dec 8 at 12:39
1
1
No, repeated writing to
/sys/class/thermal (as the original poster asked) won't have any impact to SSD hardware :-) To have any significant effect, you would have to write into /sys/block/<device name>/ and basically deliberately pick the worst possible settings for a SSD. Even so, modern consumer SSDs have plenty of writing cycles and efficient wear leveling: typically the vendors promise that you could write more than a terabyte every day and the SSD would still have the expected lifetime. Of course, sometimes those promises can be mistaken or less than truthful otherwise...– telcoM
Dec 8 at 12:53
No, repeated writing to
/sys/class/thermal (as the original poster asked) won't have any impact to SSD hardware :-) To have any significant effect, you would have to write into /sys/block/<device name>/ and basically deliberately pick the worst possible settings for a SSD. Even so, modern consumer SSDs have plenty of writing cycles and efficient wear leveling: typically the vendors promise that you could write more than a terabyte every day and the SSD would still have the expected lifetime. Of course, sometimes those promises can be mistaken or less than truthful otherwise...– telcoM
Dec 8 at 12:53
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2funix.stackexchange.com%2fquestions%2f486750%2fdoes-constant-writing-to-files-in-proc-or-sys-reduce-the-life-of-my-ssd%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
1
You are right. Not writing to the SSD doesn't count as writing to the SSD. The same would hold for a RAM drive such as
tmpfs.– glglgl
Dec 8 at 12:29