我以前也遇到过类似的问题，当时是VOB Storage下的.hostname文件损坏造成不能注册，最后手工删除.hostname文件，并重新执行"cleartool register -replace"命令后，问题得到解决。
关于这个问题，IBM Rational的technote写的非常详细，里面把各种可能出现的情况都列举了出来，楼主的问题也许就是其中之一，可以参考一下：
Failed to record hostname
Problem(Abstract)
This technote explains how to resolve the error, cleartool Error: Failed to record hostname, when trying to register or create an IBM® Rational® ClearCase® VOB or View on Microsoft® Windows®, UNIX® or Linux®.
Symptom
Attempts to register or create a VOB or view results in the following error:
cleartool Error: Failed to record hostname in storage directory
VOB Example:
D:\>cleartool register –vob \\Hostname\ClearCaseStorage\CCVobs\vob1.vbs
cleartool Error: Failed to record hostname “Hostname” in storage directory “\\Hostname\ClearCaseStorage\Ccvobs\vob1.vbs”. Check that root or the ClearCase administrators group has permission to write to this directory
View Example:
View Tool
Error creating view - '<view-tag>'
Fail to record hostname " HOST " in storage directory "<path to view storage>. Check that root or the ClearCase administrators group has permission to write to this directory.
UNable to create view "<global path to view storage>".
Cause
The cause of the error ultimately stems from the inability of ClearCase to successfully record the hostname in the .hostname file located in the storage directory of the VOB or view.
KNOWN CAUSES:
Some of the known reasons why this problem occurs are below. The related solutions are presented in the same order.
The .hostname file is corrupt.
The permissions on the VOB or view server are incorrect or too restrictive.
The VOB or view storage and/or its contents are incorrect.
This is a common occurrence after a VOB or view is moved or restored, and the file permission on the .vbs/.vws directory are too strict and need repair.
Note: The .identity file on UNIX and Linux tends to have the wrong permission in this instance. If this file is missing, you are safe to copy over from another VOB storage (provided the permissions are the same).
The VOB or view storage location may have the wrong permissions set. When a VOB or view is created, it takes on the ACL from the storage directory (among other things). If the permissions on the storage directory is faulty, the .hostname will be created with the wrong permissions. When ClearCase attempts to write to this file, the error will occur.
Note: On Windows, this may include the permissions set at the root of the partition as the ACLs are inherited.
The Windows client is using a different ClearCase server process group or clearcase_albd account than that of the host to which the view is being stored. For example, clientA is attempting to create a view on serverA. ClientA is configured to use the clearcase group named clearcase_1 while the serverA is using a clearcase server group called clearcase_2. This includes differences in domain Qualification as well (DOMAINA\clearcase vs. DOMAINB\clearcase)
Note: Same scenario may also apply with different clearcase_albd accounts.
If the VOB is moved to another host and if there are additional groups in the .identity file that do not exist on the new host, this error will occur while attempting to register the VOB.
Resolving the problem
Solution 1
If the file is corrupt, the .hostname file must be deleted or renamed, and a new one will get recreated when cleartool register is run.
Windows Example:
Rename the .hostname file:
C:\Rational\Storage\VOB\vob1.vbs>ren .hostname old.hostname
Register the VOB or view:
cleartool register -replace -vob \\Hostname\ClearCaseStorage\CCVobs\vob1.vbs
Note: The -replace switch is used because cleartool register created some entries for the VOB or view even though the command had failed previously.
The VOB or view storage directory will now contain a new .hostname:
C:\Rational\Storage\VOB\vob1.vbs>dir *.hostname
Volume in drive C has no label.
Volume Serial Number is 8723-79C9
Directory of C:\Rational\Storage\VOB\vob1.vbs
04/07/2006 02:18 PM 17 .hostname
03/17/2006 02:37 PM 17 old.hostname
...
For more information on the cleartool sub-commands used in this technote, refer to IBM Rational ClearCase Command Reference, or run cleartool man <sub-command>.
Solution 2
The file system permission must be corrected on the VOB or view storage and/or its contents.
The quickest solution would be to run the fix_prot utility against the problematic VOB or view storage. Review technote 1142606 for more details.
An alternate route to resolving this issue is to compare the permission of the .vbs/.vws for a working VOB or view with the output for the non-working VOB or view, then change the permission of the non-working VOB or view to match the working VOB or view:
On UNIX (and Linux), do an ls -alR in the .vbs/.vws directory to determine the permission of the .vbs/.vws directory for a working and non-working VOB or view.
On Windows, consult your system administrator or operating system manuals for assistance with checking the file permission.
To correct the protections on a VOB or view storage directory and its contents, refer to technote 1211784 for details on the appropriate commands.
The file system permission must be corrected on the VOB or view storage location and or the root of the partition.
If the cleartool mkstgloc command was used to create the storage location, remove the storage location (cleartool rmstgloc) and create a new one.
Note: This command does not remove the physical storage location, it only removes the registry entry in the ClearCase registry.
If that fails, make sure the directory and/or share of the storage location has the appropriate permissions to allow the ClearCase users and groups (including the ClearCase service accounts such as the clearcase_albd on Windows) access to read and write.
Also check the each directory up to and including the root of the partition on Windows as the ACLs are inherited from the parent folder.
Solution 3
Make sure the Windows client is configured to use the same ClearCase server process group and or clearcase_albd account as the server (or vice versa).
Hint: You can run the ClearCase Doctor on the client and server to verify the ClearCase Server Process group and account information.
If the account is different on the client, the only supported method to resolve this issue is to reinstall ClearCase from the correct release area to update the server process information.
Note: Manually changing the account in the registry or services may not be enough as there are permission issues on the file system to manage as well.
Review the ClearCase Administrator's Guide on the section titled Rational ClearCase and Windows domains for more information regarding the correct configuration required to share ClearCase data in a Windows domain environment.
Solution 4
Remove the invalid additional group entries in the .identity directory.
As VOB owner or root, change directory to <vob-storage-dir>/.identity
Run, rm group.<one-group-too-many>, to remove the files
Run the cleartool register command once again.
[
本帖最后由 cn_chenfeng 于 2008-5-3 22:51 编辑 ]
