Description | The following error message is displayed in the FSE error log: |
| [2005/03/02 10:39:56, fse_host, 002680, PMG, <PartitionName>, 0, ] CRITICAL ERROR: File: |
| fsc_nsDirEntry.lrf vector at index 6042669 of size 4 was released twice. |
| A DB recovery needs to be done in near future. Pack DB and contact support for further steps. |
Explanation | n/a |
Workaround | Recover the File System Catalog (FSC) of the FSE partition PartitionName. For details, see |
|
Description | The following error message is displayed in the FSE error log: |
| [2005/03/02 10:39:56, fse_host, 002680, PMG, <PartitionName>,, 0, ] CRITICAL ERROR: File: |
| hsmDirEntry.lrf vector at index 6042669 of size 4 was released twice. |
| A DB recovery needs to be done in near future. Pack DB and contact support for further steps. |
Explanation n/a
Workaround Recover the Hierarchical Storage Management Database (HSMDB) of the FSE partition PartitionName by performing the following steps:
1.Unmount the belonging HSM file system.
2.Delete the HSMDB directory from the local system. Linux specific
Path of the HSMDB directory is /var/opt/fse/part/PartitionName/hsm. Windows specific
Path of the HSMDB directory is %InstallPath%\var\part\PartitionName\hsm.
The value of %InstallPath% depends on the choice made in the FSE installation process. It defaults to C:\Program
3.Mount the HSM file system.
4.Manually put all dirty files on the HSM file system on the migration candidate list.
5.Manually release files on the release candidate list or perform any other change on the HSM file system, but do not change the files on the migration candidate list.
The release candidate files will be automatically added to the release candidate list after migration.
Description | When trying to configure a new FSE resource using the |
| interface, the command fails and reports the following error message: |
| ERROR: 3000: Parser error. 'Undefined member function Assign(str, str). at line number:0' |
Explanation | You may have used a hyphen character |
| for the FSE resource, and removed the surrounding double quote characters ("). |
Workaround | Enclose the value of the problematic variable in double quotes (") and retry adding the FSE |
| resource. |
272 Troubleshooting