Status of Data Files
[
Data-Distribution
]
Handling Collections with "bad" files
Bad Files
A file is considered as bad if
- it shows read errors (e.g.: using KanCopyUtil -r)
- it is lost, e.g.: due to a broken tape
If one file of a collection is bad the collection is considered as bad.
The following actions are taken to mark the collection as bad in the bookkeeping.
- Collection status is set to bad (dse_status=2)
- The isLocal flag is unset.
- The file status of the bad file is modified. In stead of status good it will be
changed to "lost" or "corrupted"
(List of file statuses).
File Properties Mismatch
The file properties (checksum, size and uuid) in the bookkeeping might not agree with
the ones of the physical file. One reason for this mismatch is that collections were
produced twice with the same name. They contain the same events but the file properties
will be different.
The following criteria will be used to decide if the collection is good, in
which case the file properties will be updated.
- The UUID of the files doesn't agree with the one in the Bookkeeping.
- KanCopyUtil -r <CollectionName> returns no error.
- The number of events reported by KanCopyUtil agrees with the number of
events in the bookkeeping.
If any of the above conditions fails the collection will be marked as bad:
- Collection status is set to bad (dse_status=2)
- The file status of the bad file is set to "property mismatch".
Last modified: Wed Apr 19 08:18:31 PDT 2006
|
