Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

For backup purposes we have Cifs file Server running that contains encrypted containers for backing up the more sensitive data. The container is mounted with cryptsetup and loop as a local filesystem and the rsync is used for backups.

Because the Cifs server is not the fastest machine ever built, running the rsync process results in an iowait on the servers running the backup which in turn drives Nagios into an email frenzy. The question is, how do reduce the iowait on the server? Configuring Nagios to not report seems more like a workaround then a solution. Stretching the backups over different time intervals is already done with little effect and spending money is also not an option because apparently, we are talking about a "non-critical system".

share|improve this question

Your most effective solution here will be to rebuild the backup box with a CPU that supports the AES-NI instructions, and a Linux kernel that supports that instruction. This will make the encryption operations much, much faster and should reduce iowait.

However, you specified $nospend="True"

About all you have left is --bwlimit on your rsync processes to reduce the amount of data being thrown at the cifs box. And if that doesn't work, you'll just have to live through the email storms until funding become available to fix it right.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.