Changeset 34357
- Timestamp:
- Aug 25, 2012, 11:46:07 AM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/eam_branches/ipp-20120805/Ohana/src/dvomerge/doc/failsafe.txt
r33963 r34357 1 2 20120809 3 4 more on failsafe 5 6 I need to improve the technique I'm using for failsafe ops / rerun. 7 8 * Image.dat PHU keywords: 9 DVO_DB_ID : %s : hex string with 32 byte "unique" string for DB 10 DM_NMERGE : %d : number of databases merged into this onea 11 DM_nnnnnn : %s : DVO_DB_ID of merge (nnnnn) 12 13 Note: nnnnnn may be greater than NMERGE if entries are skipped 14 (only a total of NMERGE nnnnnn values are allowed) 15 16 * region.cpt PHU keywords: 17 DM_NMERGE : %d : number of databases merged into this one (needed?) 18 MS_nnnnnn : %d : size of merged db entry nnnnnn 19 MT_nnnnnn : %s : date/time of merged db entry nnnnnn 20 21 Is there a reason for the image entries? (additional record keeping) 22 23 24 25 26 201206?? 1 27 2 28 we have a problem with dvomerge and flaky hosts. the problem is that
Note:
See TracChangeset
for help on using the changeset viewer.
