Lines Matching full:operation
16 system crashes. The status of the operation is recorded in an extra field
19 auxiliary file, so that if the operation is interrupted, it can be completed
20 the next time an append operation is attempted.
47 foo.add file are sufficient to recover an interrupted append operation. The
50 well as the crc and length of the gzip data before the append operation.
54 operation is interrupted, the data to add will still be there. If due to
56 operation was interrupted and when recovery is attempted, the gzip file will
60 foo.add file are sufficient to recover an interrupted compress operation.
66 Again, the foo.add file is maintained during the compress operation in case
72 operation.
75 the new dictionary after a compress operation. Once compression is
102 an "atomic" operation. That is, either all of the extra field is written
103 to the file, or none of it is, if the operation is interrupted right at the
126 lost after a compress operation is interrupted.
133 an append operation is interrupted.
142 data in the compress operation, overwriting the previous first stored
144 reconstructed on the off chance that a compression operation was
146 - The operation in process. This is the next two bits in the last byte (the
157 - Load the extra field from the foo.gz file, and see if an operation was in
165 - Put what to append in the foo.add file so that the operation can be
167 - Mark the foo.gz extra field with the append operation in progress.
170 append operation was interrupted.
175 - Write over the extra field (with a single write operation) with the new
179 completed operation, it is truncated when writing new data to it.
196 a compress operation.) During this process, the foo.lock file is
271 /* values for the operation (2 bits) */
407 expected. op is the current operation in progress last written to the extra
432 /* Write over the extra field contents, marking the operation as op. Use fsync
434 operation, and only this operation, is assumed to be atomic in order to
565 file, since the compress operation may have been interrupted before that was
569 the replace operation may have been interrupted after the rename is done,
601 and is the data provided in data[0..len-1]. If this operation is
709 /* mark as being in the replace operation */
713 /* execute the replace operation and mark the file as done */
734 /* Recover the interrupted operation op. First read foo.add for recovering an
735 append or compress operation. Return -1 if there was an error reading or
773 /* recover the interrupted operation */
891 recovery operation if needed */
920 field information (it probably changed), recover last operation if
1006 field information (it probably changed), recover last operation if
