Professional Documents
Culture Documents
Perform the following steps when the issue occurs, in order to isolate the client(s) that are performing
the large delete operations that lead to the issue being observed:
If cifs latency is seen high then run stats show cifs latency command. Below is command with sample
outout
Note: Get into vfiler context if the issue is on the vfiler using command vfiler context <vfiler_name>
2. Get the CIFS SESSIONS output to check if '#files' for a particular session are excessively larger than
others:
> cifs sessions -c
3. Get the CIFS STAT output to review Current Pending DeleteOnClose Requests, to determine if it is
greater than or equal to the hard-set limit shown in the value associated with Max Pending
DeleteOnClose Requests on the same line, which is when the issue occurs:
> cifs stat
CIFS sessions output will provide a list of all open sessions and the number of files that are open:
172.12.12.12(workstation) (DOMAIN\username - pcuser)
2 126702 <<<< 126702 open files
To fix this:
1. Clear all the CIFS locks and break the locks so that the pending deletes gets processed.
To Check for the locks :
> lock status -p cifs
To break the locks:[ The below command will break all the CIFS locks currently held]
> lock break -p cifs
b. To view the CIFS per client statistics run the command below:
> cifs top
Once identified check with your host team on the Clients that are on top of the list. Check if there is any
application or some script that is continuously sending delete requests.