Skip to main content
NetApp Knowledge Base

Application accessing CIFS share may fail when setting an atime of -2 on a file

Views:
88
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • CIFS

Issue

  • Application fails to write a log file to ONTAP CIFS share
  • Client sets atime value of -1 on filehandle, then some time after the client sets atime value of -2 on same filehandle and receives STATUS_USUCCESSFUL error.

Example from packet trace

10.6.1.123        10.6.4.28       SMB2    SetInfo Request FILE_INFO/SMB2_FILE_BASIC_INFO File: PATH\TO\FILE\file1.ext

SetInfo Request (0x11)
    [Filename: PATH\TO\FILE\file1.ext]
    StructureSize: 0x0021
    Class: FILE_INFO (0x01)
    InfoLevel: SMB2_FILE_BASIC_INFO (0x04)
    Setinfo Size: 40
    Setinfo Offset: 0x0060
    Reserved: 0
    Additional Info: 0x00000000
    GUID handle File: PATH\TO\FILE\file1.ext
    SMB2_FILE_BASIC_INFO
        Create: No time specified (0)
        Last Access: Not representable >>>>>>>> (i.e. 0xfffffffe)
        Last Write: No time specified (0)
        Last Change: No time specified (0)
        File Attributes: 0x00000000
        Reserved: 00000000

10.6.4.28       10.6.1.123        SMB2    SetInfo Response, Error: STATUS_UNSUCCESSFUL

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.