sysstat data corruption when adding or removing VCPUs

Bug #1470165 reported by Guillaume Penin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sysstat (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Using sysstat 10.0.3-1 on Ubuntu Precise 12.04 LTS.

When we add or remove VCPUs to virtual machines (KVM or VMWare in our case), sysstat data starts to be corrupted the next day. All sysstat data will be corrupted, until the current data file is deleted as a workaround.

- Symptom :

[root@server ~]# sar -A -f /var/log/sysstat/sa30
Invalid system activity file: /var/log/sysstat/sa30

- Workaround :

[root@server ~]# rm -f /var/log/sysstat/sa30

- Attachment :

Sysstat data archive with :

- Correct data : sa22, sa23
- Corrupted data : sa24 => sa29
- Correct data since workaround : sa30

Revision history for this message
Guillaume Penin (guillaume-penin) wrote :
Revision history for this message
Robert Luberda (robert-debian) wrote :

This was fixed by upstream:

2014/03/18: Version 10.3.1 - Sebastien Godard (sysstat <at> orange.fr)
          WARNING: Daily data files format has changed, and is *not*
          compatible with the previous one! [0x2173]
        * sar/sadc/sadf: Now take into account a change of CPU count
          in datafiles. The number of CPU is displayed in the RESTART
          messages.

Changed in sysstat (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.