Limit tar read speed












3














I'm using tar do make backups of a machine. But, it is using a lot of I/O and slows down the whole machine.



So, is there a way to limit the read speed of tar?



I know about pv, but it limit only the write speed. Because I do incremental backups with tar --listed-incremental, this will work only with the first full backup (subsequent incremental backups will then consume a lot of read I/O if there is only small changes).



I've tried to lower the overall priority of the backup with a combination of nice and ionice, but this not really change anything.



Informations: it's Debian 9 machine, and the files are residing on an ext4 file-system on top of a LVM volume.










share|improve this question




















  • 1




    As a side note, sorry if I'm not posting the question on the right website. I'm a bit confused about the difference between unix.stackexchange, Super User and Server Fault since this question seems to be on-topic for these 3 websites.
    – Zoddo
    Dec 16 at 12:01






  • 1




    check out cpulimit as in this answer: unix.stackexchange.com/a/39730/3375
    – ojblass
    Dec 16 at 12:27










  • Have you tried limiting the output of tar using something like pv, as you mentioned?
    – Andrew Henle
    Dec 16 at 21:53










  • Be careful, gtar in general is unable to restore it's incremental backups. This only works in case that the differences between two incrementals are trivial and do not include renamed directories.
    – schily
    Dec 17 at 16:23
















3














I'm using tar do make backups of a machine. But, it is using a lot of I/O and slows down the whole machine.



So, is there a way to limit the read speed of tar?



I know about pv, but it limit only the write speed. Because I do incremental backups with tar --listed-incremental, this will work only with the first full backup (subsequent incremental backups will then consume a lot of read I/O if there is only small changes).



I've tried to lower the overall priority of the backup with a combination of nice and ionice, but this not really change anything.



Informations: it's Debian 9 machine, and the files are residing on an ext4 file-system on top of a LVM volume.










share|improve this question




















  • 1




    As a side note, sorry if I'm not posting the question on the right website. I'm a bit confused about the difference between unix.stackexchange, Super User and Server Fault since this question seems to be on-topic for these 3 websites.
    – Zoddo
    Dec 16 at 12:01






  • 1




    check out cpulimit as in this answer: unix.stackexchange.com/a/39730/3375
    – ojblass
    Dec 16 at 12:27










  • Have you tried limiting the output of tar using something like pv, as you mentioned?
    – Andrew Henle
    Dec 16 at 21:53










  • Be careful, gtar in general is unable to restore it's incremental backups. This only works in case that the differences between two incrementals are trivial and do not include renamed directories.
    – schily
    Dec 17 at 16:23














3












3








3







I'm using tar do make backups of a machine. But, it is using a lot of I/O and slows down the whole machine.



So, is there a way to limit the read speed of tar?



I know about pv, but it limit only the write speed. Because I do incremental backups with tar --listed-incremental, this will work only with the first full backup (subsequent incremental backups will then consume a lot of read I/O if there is only small changes).



I've tried to lower the overall priority of the backup with a combination of nice and ionice, but this not really change anything.



Informations: it's Debian 9 machine, and the files are residing on an ext4 file-system on top of a LVM volume.










share|improve this question















I'm using tar do make backups of a machine. But, it is using a lot of I/O and slows down the whole machine.



So, is there a way to limit the read speed of tar?



I know about pv, but it limit only the write speed. Because I do incremental backups with tar --listed-incremental, this will work only with the first full backup (subsequent incremental backups will then consume a lot of read I/O if there is only small changes).



I've tried to lower the overall priority of the backup with a combination of nice and ionice, but this not really change anything.



Informations: it's Debian 9 machine, and the files are residing on an ext4 file-system on top of a LVM volume.







linux tar disk io






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 16 at 13:53









Jeff Schaller

38.7k1053125




38.7k1053125










asked Dec 16 at 11:55









Zoddo

161




161








  • 1




    As a side note, sorry if I'm not posting the question on the right website. I'm a bit confused about the difference between unix.stackexchange, Super User and Server Fault since this question seems to be on-topic for these 3 websites.
    – Zoddo
    Dec 16 at 12:01






  • 1




    check out cpulimit as in this answer: unix.stackexchange.com/a/39730/3375
    – ojblass
    Dec 16 at 12:27










  • Have you tried limiting the output of tar using something like pv, as you mentioned?
    – Andrew Henle
    Dec 16 at 21:53










  • Be careful, gtar in general is unable to restore it's incremental backups. This only works in case that the differences between two incrementals are trivial and do not include renamed directories.
    – schily
    Dec 17 at 16:23














  • 1




    As a side note, sorry if I'm not posting the question on the right website. I'm a bit confused about the difference between unix.stackexchange, Super User and Server Fault since this question seems to be on-topic for these 3 websites.
    – Zoddo
    Dec 16 at 12:01






  • 1




    check out cpulimit as in this answer: unix.stackexchange.com/a/39730/3375
    – ojblass
    Dec 16 at 12:27










  • Have you tried limiting the output of tar using something like pv, as you mentioned?
    – Andrew Henle
    Dec 16 at 21:53










  • Be careful, gtar in general is unable to restore it's incremental backups. This only works in case that the differences between two incrementals are trivial and do not include renamed directories.
    – schily
    Dec 17 at 16:23








1




1




As a side note, sorry if I'm not posting the question on the right website. I'm a bit confused about the difference between unix.stackexchange, Super User and Server Fault since this question seems to be on-topic for these 3 websites.
– Zoddo
Dec 16 at 12:01




As a side note, sorry if I'm not posting the question on the right website. I'm a bit confused about the difference between unix.stackexchange, Super User and Server Fault since this question seems to be on-topic for these 3 websites.
– Zoddo
Dec 16 at 12:01




1




1




check out cpulimit as in this answer: unix.stackexchange.com/a/39730/3375
– ojblass
Dec 16 at 12:27




check out cpulimit as in this answer: unix.stackexchange.com/a/39730/3375
– ojblass
Dec 16 at 12:27












Have you tried limiting the output of tar using something like pv, as you mentioned?
– Andrew Henle
Dec 16 at 21:53




Have you tried limiting the output of tar using something like pv, as you mentioned?
– Andrew Henle
Dec 16 at 21:53












Be careful, gtar in general is unable to restore it's incremental backups. This only works in case that the differences between two incrementals are trivial and do not include renamed directories.
– schily
Dec 17 at 16:23




Be careful, gtar in general is unable to restore it's incremental backups. This only works in case that the differences between two incrementals are trivial and do not include renamed directories.
– schily
Dec 17 at 16:23















active

oldest

votes











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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489292%2flimit-tar-read-speed%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489292%2flimit-tar-read-speed%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Morgemoulin

Scott Moir

Souastre