File relocation through an application process, General file relocation considerations, File relocation examples – HP NonStop G-Series User Manual

Page 88

Advertising
background image

File Relocation Facility

HP NonStop Storage Management Foundation User's Guide523562-008

5-2

File Relocation Through an Application Process

The FUP RELOCATE command must be issued on the system where the file resides,
and it must be issued only by a member of the super group (255,n) or the owner of the
file. Note that a file that has been relocated has a new physical name.

File Relocation Examples

The following command moves all files matching the fileset $L.A.B* to the physical
volume $P4. Any files that already reside on $P4 are not moved.

FUP RELOCATE $L.A.B*, $P4

The following command moves the file $S.G.F to a new location on a different physical
volume selected by SMF.

FUP RELOCATE $S.G.F

The File Utility Program is described in the File Utility Program (FUP) Reference
Manual
.

File Relocation Through an Application Process

A file relocation operation from an application process is accomplished by using the file
system routine SMS_RELOCATEFILE_. This routine initiates the SMF file relocation
server RELOCSRV.

The call to SMS_RELOCATEFILE_ must be issued on the system where the file
resides. The call can be issued only by an application process running as a member of
the super group (255,n) or as the owner of the file. Upon completion, the file system
routine returns a status code, plus additional information on any error: for example, any
file system error that might have occurred, or the physical file that had the error, and so
on. The call to SMS_RELOCATEFILE_ is waited; the application suspends until the
relocation finishes. If the relocation operation is successful, SMS_RELOCATEFILE_
returns the new physical volume name for the relocated file.

A file relocation operation initiated by an application process supports relocation of only
one object at a time.

This and other SMF file system routines are described in

Section 8, Guardian

Procedures

.

General File Relocation Considerations

The following summarizes some file relocation operational considerations:

Concurrent data access. A file cannot be relocated if there are other processes
that have it open. If this condition exists, an FEINUSE error is returned.

Concurrent operations. The file to be relocated is not available for concurrent
operations. Attempts to open, alter, or purge the file while the relocation operation
is in progress are rejected with an FEINUSE error. A second relocate operation

Advertising