6.5 HP StoreAll OS User Guide

3. To disable autocommit, you must unmount the file system, modify the data retention settings,
and mount the file system again. See “Changing the retention profile for a file system”
(page 279) for more information.
If required, you can renable the registry setting after the migration. Run the same commands as
for disabling the registry setting, but change the value of AllowPVFSFilemodeChange to 1. You
can also renable autocommit after the migration, if required.
Troubleshooting SMB
Changes to user permissions do not take effect immediately
The SMB implementation maintains an authentication cache that is set to four hours. If a user is
authenticated to a share, and the user's permissions are then changed, the old permissions will
remain in effect until the cache expires, at four hours after the authentication. The next time the
user is encountered, the new, correct value will be read and written to the cache for the next four
hours.
This is not a common occurrence. However, to avoid the situation, use the following guidelines
when changing user permissions:
• After a user is authenticated to a share, wait four hours before modifying the user's permissions.
• Conversely, it is safe to modify the permissions of a user who has not been authenticated in
the previous four hours.
Robocopy errors occur during node failover or failback
If Robocopy is in use on a client while a file serving node is failed over or failed back, the
application repeatedly retries to access the file and reports the error The process cannot
access the file because it is being used by another process. These errors
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 processes 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 SMB 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 an SMB share, the copy
operation might be interrupted and need to be restarted.
Active Directory users cannot access SMB shares
If any AD user is set to UID 0 in Active Directory, you will not be able to connect to SMB shares
and errors will be reported. Be sure to assign a UID other than 0 to your AD users.
Troubleshooting SMB 117