HP StoreAll Storage - Manual (Page 93)

occur for 15 to 20 minutes. The client's copy will then continue without error if the retry timeout
has not expired. To work around this situation, take one of these steps:
•
Stop and restart the Likewise process on the affected file serving node:
# /opt/likewise/bin/lwsm stop lwreg && /etc/init.d/lwsmd stop
# /etc/init.d/lwsmd start && /opt/likewise/bin/lwsm start srvsvc
•
Power down the file serving node before failing it over, and do failback operations only during
off hours.
The following xcopy and robocopy options are recommended for copying files from a client to
a highly available CIFS server:
xcopy : include the option /C; in general, /S /I /Y /C are good baseline options.
robocopy : include the option /ZB; in general, /S /E /COPYALL /ZB are good baseline
options.
Copy operations interrupted by node failback
If a node failback occurs while xcopy or robocopy is copying files to a CIFS share, the copy
operation might be interrupted and need to be restarted.
Active Directory users cannot access CIFS shares
If any AD user is set to UID 0 in Active Directory, you will not be able to connect to CIFS shares
and errors will be reported. Be sure to assign a UID other than 0 to your AD users.
UID for CIFS Guest account conflicts with another user
If the UID for the Guest account conflicts with another user, you can delete the Guest account and
recreate it with another UID.
Use the following command to delete the Guest account, and enter yes when you are prompted
to confirm the operation:
/opt/likewise/bin/lw-del-user Guest
Recreate the Guest account, specifying a new UID:
/opt/likewise/bin/lw-add-user –-force --uid <UID_number> Guest
To have the system generate the UID, omit the --uid <UID_number> option.
Troubleshooting CIFS 93