HP 800 CIFS/9000 Client Release Note, June 2002 - Page 13

CIFS/9000 Client A.01.08 Known Problems and Workarounds Known Problems and Workarounds For the CIFS/9000 Client • The CIFS/9000 Client with ASU/9000 Servers There is a known, infrequent problem between the CIFS/9000 Client and ASU. If you find that a connection to an ASU server becomes inaccessible, turn off opportunistic locks (oplocks) for communications with ASU, in the CIFS Client configuration file /etc/opt/cifsclient/cifsclient.cfg. Oplocks can be turned off globally, in the defaultServer section, by setting requestOplock=no. A preferred method is to turn off oplocks only for ASU servers. To do so, first add the following lines, if they are not already present, to the serverClasses section. Then, to turn off oplocks for only this class of server, set requestOplock=no: { // Match ASU: OS = "*"; LanManager = "*Advanced Server*"; config = { disableSmbs = ( // these are additional to other config setattrTrans2SetFile, // don't use trans2/setfileinfo setattrTrans2SetPath, // don't use trans2/setpathinf ); requestOplock = no; }; } • Removing a Directory and its Contents Removing a directory and its contents in one step using the command, rm -rf , may fail on directories located on a cifsmount. If the directory contains ~30 or more files, only part of the directory contents will be removed and the directory itself will remain since its contents have not been removed A workaround is to remove the directory and its contents in two steps 1. rm -rf /* 2. rmdir # Remove directory contents. # Remove directory itself. Chapter 1 13