gd_raw_filename(3) GETDATA gd_raw_filename(3)NAME
gd_raw_filename -- retrieve the pathname of a binary file in a dirfile
SYNOPSIS
#include <getdata.h>
const char *gd_raw_filename(DIRFILE *dirfile, const char *field_code);
DESCRIPTION
The gd_raw_filename() function retrieves the pathname of the file backing the RAW field specified by field_code in the dirfile specified by
dirfile. If field_code contains a valid representation suffix, it will be ignored.
RETURN VALUE
On success, gd_raw_filename() returns the full pathname of the binary file associated with the specified field. On error, NULL is returned
and the dirfile error is set to a non-zero error value. Possible error values are:
GD_E_ALLOC
The library was unable to allocate memory.
GD_E_BAD_CODE
The field specified by field_code was not found.
GD_E_BAD_DIRFILE
The supplied dirfile was invalid.
GD_E_BAD_FIELD_TYPE
The field specified by field_code was not a RAW field.
GD_E_BAD_REPR
The representation suffix specified in field_code was not recognised.
GD_E_UNKNOWN_ENCODING
The encoding scheme of the specified field could not be determined or was not understood by GetData.
The dirfile error may be retrieved by calling gd_error(3). A descriptive error string for the last error encountered can be obtained from
a call to gd_error_string(3).
SEE ALSO gd_entry(3), gd_error(3), gd_error_string(3), dirfile(5), dirfile-encoding(5), dirfile-format(5)Version 0.7.0 16 July 2010 gd_raw_filename(3)
Check Out this Related Man Page
gd_fragment_index(3) GETDATA gd_fragment_index(3)NAME
gd_fragment_index -- retrieve the fragment containing a dirfile field
SYNOPSIS
#include <getdata.h>
int gd_fragment_index(const DIRFILE *dirfile, const char *field_code);
DESCRIPTION
The gd_fragment_index() function queries a dirfile(5) database specified by dirfile and returns the index number of the fragment defining
the field specified by field_code. If field_code contains a representation suffix, it will be ignored.
RETURN VALUE
Upon successful completion, gd_fragment_index() returns the requested fragment index. On error, gd_fragment_index() returns -1 and sets
the dirfile error a non-zero error value. Possible error values are:
GD_E_BAD_DIRFILE
The supplied dirfile was invalid.
GD_E_BAD_CODE
The field specified by field_code was not found in the database.
GD_E_BAD_REPR
The representation suffix specified in field_code was not recognised.
The dirfile error may be retrieved by calling gd_error(3). A descriptive error string for the last error encountered can be obtained from
a call to gd_error_string(3).
SEE ALSO gd_open(3), gd_entry(3), gd_error(3), gd_error_string(3), gd_fragmentname(3), gd_parent_fragment(3), dirfile(5)Version 0.7.0 15 July 2010 gd_fragment_index(3)
Dear,
How to copy update without interactive confirmation?
I am using
#cp -Rfu dirfile dirfile
But the interactive confirmation still exist.
Thank you. (0 Replies)
Hi,
We have a new server which has 2.7 TB RAW Disk.Outof this we want to convery 1.2 TB to filesystem and nfs mount it on one of the servers.
After our activity we need to convert this back to RAW Disks.
Please let me know if this is possible and the complexity involved.
Regards,
VN (1 Reply)