Release Notes

hp StorageWorks File System Extender Release Notes 25
5 Known issues and workarounds
Description After starting FSE daemons with the command fse --start, the following error appears in the
FSE error log:
ERROR: *** NO OWNER set for INO... *** File must be migrated again! fileID= <FileID>
file <DirectoryPath>/<FileName>
Explanation While FSE daemons on a particular FSE client are stopped and modifications are made on an
HSM file system located on the client, it may happen that a file system event is lost. The file
owner information for the file DirectoryPath/Filename in the HSMDB is not complete.
This error can be detected earlier using fsecheck --fsc-hsmfs, and is logged when the
migration of the file is started.
Workaround Manually put the file and the directory where the file is located on the migration candidate list
using the command fsefile --migrate DirectoryPath Filename.
Description In an FSE implementation with highly loaded FSE server, after numerous FSE operations
(migrations, releases, recalls) are running for a long period time, either of the following
symptoms are noticed: recalls and possibly other FSE operations start failing, FSE partitions are
reported to be in the unmounted state but the corresponding HSM processes are running.
Inspection of the FSE error log may reveal the following errors:
omniORB: Unrecoverable error for this endpoint: giop:tcp:10.65.1.38:3504, it will no longer
be serviced.
omniORB: Error: Unable to create an endpoint of this description: giop:tcp:10.65.1.38:3513
PM->Recall() failed: 6004: Caught Corba exception.
'CORBA::TRANSIENT#TRANSIENT_ConnectFailed'
Explanation For explanation of this problem, see chapter ”Recommendations”, section ”General
recommendations”, subsection ”Preventing exhaustion of CORBA sockets” on page 16.
Workaround For workaround for this problem, see chapter ”Recommendations”, section ”General
recommendations”, subsection ”Preventing exhaustion of CORBA sockets” on page 16.
Description Running the fsefile -l * command on the top directory of an HSM file system results in the
following message:
Warning: System Volume Information: cannot get file state (5: Access is denied. 'CreateFile').
(Windows system specific)
Explanation The message appears because the directory System Volume Information is a special
Windows directory which refuses access from other applications.
Workaround The command completes successfully and you may ignore the message.