Reported by Teng Wang.

Some Darshan logs on Cori report 0 POSIX_READS and POSIX_WRITES, but non-zero POSIX_SEQ_READS or POSIX_SEQ_WRITES. This shouldn't be possible, as the latter is a subset of the former.

After investigating some log examples, this looks to be a problem in darshan-logutils when upconverting from logs generated with Darshan 3.0.1 to produce 3.1.6-compatible output.

Those older logs have counters for a few stdio operations (POSIX_F{OPENS|READS|WRITES|SEEKS}) integrated into the POSIX counters. These can't be displayed correctly in newer Darshan utilities because STDIO has a dedicated module now with its own format. The current upconvert logic just discards those 4 counters, but it does not change other auxiliary counters, like the SEQ_READS and SEQ_WRITES, leading to an inconsistency for the file record.

It isn't practical from a software maintenance point of view to fully convert these records to new stdio module records.

One option is to convert those counters to POSIX_{OPENS|READS|WRITES|SEEKS}) which would make all counters consistent with each other, but that is misleading because there will be no indication that stdio was used on that record.

Another option is to discard file records that meet these conditions and print a warning that an older version of the Darshan parser would have to be used to retrieve that information.