User's Manual

210 Troubleshooting
Migration problems
Description All migrations are waiting for disk buffer and data transfer to FSE media does not start.
Explanation Regardless of the operating system, if jobs are aborted, killed or they die for reasons unknown,
it can happen that the disk buffer file they created will remain on the system, using up disk
space, and will never be removed by FSE. The file fse.log will show jobs reporting FSE disk
buffer as being full. They will be in a waiting state and none of them will start writing to tape.
Workaround If this happens, the solution is to stop FSE using the fse --stop command, remove the
specified files, and restart FSE using the fse --start command.
Linux specific
Remove all files in the directory /var/opt/fse/diskbuf.
Windows specific
Remove all files in the directory %InstallPath%\var\diskbuf.
The value of %InstallPath% depends on the choice made in the FSE installation process. It
defaults to C:\Program Files\Hewlett-Packard\FSE.
Description fse-hsm process terminates abnormally because all i-nodes on the HSM file system are used
(Linux-system specific).
Explanation A possible cause of this problem is in all i-nodes on the HSM file system being used.
Workaround If this happens, you should extend the HSM file system using the command e2fsadm.