dirfile_move (3) - Linux Manuals
dirfile_move: move a dirfile field between format file fragments
NAMEdirfile_move --- move a dirfile field between format file fragments
- int dirfile_move(DIRFILE *dirfile, const char *field_code, int new_fragment, int move_data);
If the flag move_data is non-zero, and field_code specifies a RAW field, the binary file associated with the field will be translated to account for the possibly different encoding, endianness, and frame offset of the new format file fragment. It will also be moved to a new directory, if necessary. If move_data is zero, no changes will be made to the binary file. If field_code specifies a field of type other than RAW, the move_data flag is ignored.
If the binary file is translated, and the frame offset of the destination fragment is larger than that of the source fragment, this will result in permanent deletion of data from the database. If the new frame offset is smaller than the old frame offset, the binary file will be padded at the front with zeroes.
RETURN VALUEOn success, dirfile_move() returns zero. On error, -1 is returned and the dirfile error is set to a non-zero error value. Possible error values are:
- The specified dirfile was opened read-only.
- The library was unable to allocate memory.
- The field specified by field_code was not found.
- The supplied dirfile was invalid.
- An attempt was made to move the immutable INDEX field.
- The new_fragment argument did not index a valid format file fragment.
- The metadata of the source or destination format file fragments was protected from change, or the binary data of the source or destination fragments was protected from change and binary file translation was requested.
- An I/O error occurred while attempting to translate a binary file.
- The encoding scheme of the source or destination fragment is unknown.
- The encoding scheme of the source or destination fragment does not support binary file translation. The dirfile error may be retrieved by calling get_error(3). A descriptive error string for the last error encountered can be obtained from a call to get_error_string(3).
NOTESA binary file translation occurs out-of-place. As a result, sufficient space must be present on the filesystem for both the binary file before translation and the binary file after translation.
SEE ALSOdirfile_metaflush(3), dirfile_open(3), get_error(3), get_error_string(3), dirfile(5), dirfile-format(5)