Hide Forgot
Description of problem: After changing the number of virtual CPUs on a VM, the current sar data file becomes corrupt and unusable. Version-Release number of selected component (if applicable): sysstat-9.0.4-27.el6.x86_64 How reproducible: using a RHEL 6.7 KVM hosted VM. Customer was using VMware Steps to Reproduce: 1. Fire up a RHEL 6.7 VM 2. Check that sar is producing good output. Let the system run for a few collection cycles 3. Increase the number of CPUs. If system won't hotplug, reboot it. 4. Issue a sar command and the error message will result Actual results: error Expected results: sar data goodness Additional info:
Marc, changing the number of CPUs within one sa data file is supported since sysstat 10.3.1. Here are the commits from the upstream: https://github.com/sysstat/sysstat/commit/8a2b558892353ff1fdcc70be187106837aeea882 https://github.com/sysstat/sysstat/commit/cd31adf53381b6fa88b145a7e608bc83f0f454b4 https://github.com/sysstat/sysstat/commit/372339579ff08e92610303c3b96276f65faa5f51 https://github.com/sysstat/sysstat/commit/f4878ad79941bec3674946a9bb4ac921b8cec46e https://github.com/sysstat/sysstat/commit/cd625e9cad4acf03d0dda0059af337f70b90036b https://github.com/sysstat/sysstat/commit/331c3f97ad71fc86b6878c3412a20b7d25d7dd07 From the commits you can see that this is a huge change, and what is more, this change breaks backward compatibility of the sa data files, what disallow us to backport this feature to the RHEL-6. Unfortunately, RHEL-7 ships with sysstat 10.1.5, so it won't work there either.. peter
Peter, So what I'm hearing is "Yeah, not a chance." ;-) No worries, I think this is a real edge case and not worth the risk of even arguing a backport. We can close this as WONTFIX if necessary. Marc
Thanks Marc.