IBM Support

Error: unable to set set-id on file

Technote (troubleshooting)


Problem(Abstract)

This technote explains why the creation of an IBM® Rational® ClearCase® VOB or view on UNIX® or Linux® fails with cleartool: Error: unable to set set-id on file and provides steps to resolve the problem.

Symptom

Attempt to create a VOB or view on UNIX or Linux (even if the storage is hosted on a NAS filer), results in the following error:

UID Error - example

cleartool: Error: unable to set set-id on file
/net/host/export/views/test_view.vws/.identity/uid: No such
file or directory
cleartool: Error: Failed to set identity on view: No such file or directory
cleartool: Error: Unable to create view
"/net/host/export/views/test_view.vws".



Cause

The entry in the dfstab on UNIX or Linux has a value of nosuid applied.

Cause 2

GID Error - example

cleartool: Error: unable to set set-id on file
/vob_store/test.vbs/.identity/group.1501: No such file or directory
cleartool: Error: Operation "server_save_ids_flag" failed: No such file
or directory.
cleartool: Error: Unable to create versioned object base

The user creating the VOB is a member of more than 16 groups.

Cause 3

Creating a VOB on NAS

cleartool: Warning: Storage pathname "/fas270/vob_test" may not reside on host "ux-host".
Registry password:
cleartool: Error: unable to set set-id on file /fas270/vob_test/test.vbs/.identity/uid: 0
cleartool: Error: unable to set set-id on file /fas270/vob_test/test.vbs/.identity/gid: 0
cleartool: Error: unable to set set-id on file /fas270/vob_test/test.vbs/.identity/group.10: No such file or directory
cleartool: Error: Operation "server_save_ids_flag" failed: No such file or directory.
cleartool: Error: Unable to create versioned object base "/fas270/vob_test/test.vbs".


The nosuid option was added for the VOB storage export on the NAS device in the exports configuration file.

Example: The VOB storage export is /vol/ccvol

%>/net/fas270/vol % more vol0/etc/exports

#Auto-generated by registry Tue Jan 23 15:09:36 GMT 2007
/vol/vol0       -ro,rw=128.126.65.1,root=128.126.65.1,nosuid
/vol/nfstest    -rw,root=128.126.65.1,nosuid
/vol/cifstest   -rw,root=128.126.65.1,nosuid
/vol/CM_vol     -rw,root=128.126.65.1,nosuid
/vol/ccvol      -rw,root=128.126.65.1,
nosuid


Resolving the problem

Check the entry in /etc/dfs/dfstab for an entry of nosuid.

If this entry exists, remove it.


Bad Example:

share  -F nfs  -o rw,anon=0,nosuid  -d "project dirs"  /export1


Good Example:

share  -F nfs  -o rw,anon=0  -d "project dirs"  /export1

Solution 2

If using ClearCase 7.0, use the CLEARCASE_GROUPS variable to help manage the 16 group limitation.

Review technote 1124574 for more details.

If using a version of ClearCase prior to ClearCase 7.0, remove the extra groups from the group list and recreate the VOB.

Solution 3

Remove the nosuid option from the export configuration file for the VOB storage and reboot the NAS filer to take effect.

Example: The VOB storage export is /vol/ccvol

%>/net/fas270/vol % more vol0/etc/exports

#Auto-generated by registry Tue Jan 23 15:09:36 GMT 2007
/vol/vol0       -ro,rw=128.126.65.1,root=128.126.65.1,nosuid
/vol/nfstest    -rw,root=128.126.65.1,nosuid
/vol/cifstest   -rw,root=128.126.65.1,nosuid
/vol/CM_vol     -rw,root=128.126.65.1,nosuid
/vol/ccvol      -rw,root=128.126.65.1


VOB creation will now succeed as expected.

Cross Reference information
Segment Product Component Platform Version Edition
Software Development Rational ClearCase Interop: NAS

Document information

More support for: Rational ClearCase
Operating System Configurations

Software version: 7.0, 2002.05.00, 2003.06.00

Operating system(s): AIX, HP-UX, IRIX, Linux, Solaris

Reference #: 1123541

Modified date: 27 October 2010