Skip to main content
NetApp Knowledge Base

What is the meaning of 'On-Demand scan failed to set the scan status for the file. Reason: Stale NFS file handle'?

  1. Last updated
  2. Save as PDF
Views:
520
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

ONTAP 9.X

Answer

After On-Demand vscan, the following Internal Error is recorded on the scan report.

  • But this is the expected behavior.
  • If you encounter the same error messages after On-demand vscan, ignore it.


Sample: avod_XXX.log
===============================================================================
Vserver : XXXXXX
Task Name: XXXX
===============================================================================

********************************************************
Traversing path: /vol/XXXXXXXXX
********************************************************

/vol/Test/Test99/virus_test.txt: File scanned successfully by Vscanner: "XXX", Scan result: "File is infected", Vendor: "trendmicro", Version: "15.19580", Serviced by node: "XXX", Scan duration in ms: "126", Extended-status: "222200002".
/vol/Test/Test99/virus_test.txt.txt: On-Demand scan failed to set the scan status for the file. Reason: Stale NFS file handle.

/vol/Test/Test99/virus_test.com: File scanned successfully by Vscanner: "XXX", Scan result: "File is infected", Vendor: "trendmicro", Version: "15.19580", Serviced by node: "XXX", Scan duration in ms: "138", Extended-status: "222200002".
/vol/Test/Test99/virus_test.txt.com: On-Demand scan failed to set the scan status for the file. Reason: Stale NFS file handle.

/vol/Test/Test99/virus_test.zip: File scanned successfully by Vscanner: "XXX", Scan result: "File is infected", Vendor: "trendmicro", Version: "15.19580", Serviced by node: "XXX", Scan duration in ms: "123", Extended-status: "222200002".
/vol/Test/Test99/virus_test.zip: On-Demand scan failed to set the scan status for the file. Reason: Stale NFS file handle.

===============================================================================
Summary:
Number of Attempted Scans: 7
Number of Files Skipped from Scanning: 0
Number of Already Scanned Files: 0
Number of Successful Scans: 7
Number of Failed Scans: 0
Number of Timeout Scans: 0
Number of Clean Files: 4
Number of Infected Files: 3
Number of Internal Error: 3
===============================================================================
In vscan process, these are the steps if vscan has checked out the file is infected.

  1. Scanning the file just once.
The scanner reported that the file is infected and ONTAP will log scan result to report as following:

/vol/Test/Test99/virus_test.txt: File scanned successfully by Vscanner: "XXX", Scan result: "File is infected", Vendor: "trendmicro", Version: "15.19580", Serviced by node: "XXX", Scan duration in ms: "126", Extended-status: "222200002".
  1. Next step is trying to set the scan-status to inode for quarantine of infected file.
As the file was already deleted by Vscan software, ONTAP is unable to set scan-status to that file's inode and record the following error on the report.

/vol/Test/Test99/virus_test.zip: On-Demand scan failed to set the scan status for the file. Reason: Stale NFS file handle.

Additional Information

 

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.