User's Manual

hp StorageWorks File System Extender User Guide 217
Description FSE backup problems (Linux FSE server-specific).
Explanation Backup uses tar to pack all data that needs to be backed up. If a tar command has already
been started and in the meantime a backup job is aborted, the job hangs until the tar
command completes. This might be time consuming if FSE contains a lot of data to be backed
up.
Workaround In this case, the FSE server system must be cleaned up after the abort command. To clean up
the FSE server, proceed as follows:
1. Kill all processes named fse-dd or tar (using the directory /tmp/.fse).
2. Unmount all mounted volumes in the /tmp/.fse directory.
3. Remove all snap logical volumes. The example shows removing snap logical volumes in the
/dev/vg_fse directory, but make sure you use the FSE volume groups on your system:
lvremove -f /dev/vg_fse/fsevar_snap
Similarly, when a backup job hangs, the system must be cleaned up using the described
procedure before a new backup job is started. This happens because any unfinished backup
job prevents a new backup from being started.
Description At the end of an HSM file system recovery, some files are reported as being reserved in the
output of the fserecover command.
Explanation The word reserved means that file IDs were assigned to new files on the HSM file system, but
these files had been either deleted or changed before they could have been migrated using
these particular file IDs. Such file IDs were only recorded in the File System Catalog. These files
have been migrated using other, newly generated, file IDs. The “reserved” entries therefore, do
not indicate data loss.
Workaround None