VixDiskLib.log Clarification Question

Last post 08-11-2015, 10:50 AM by Jazs. 2 replies.
Sort Posts: Previous Next
  • VixDiskLib.log Clarification Question
    Posted: 08-11-2015, 10:33 AM

    G'day all.

     

    I am seeing the following lines in some vixdisklib.log files.:

     

    14108 35cc  08/11 05:16:45 ### MemoryDbMappingsExpire: Expiring SSL ID mapping, hostname [snip]
    14108 35cc  08/11 05:16:45 ### MemoryDbMappingsExpire: Expiring SSL ID mapping, hostname [snip] 14108 35cc  08/11 05:16:46 ### FILE: FileRemoveDirectoryRetry: Non-retriable error encountered (C:\Windows\TEMP\vmware-SYSTEM\42318f5c-6f34-7b29-95d1-47f39aabf037-vm-10001\LOCK.lck): The directory is not empty (145)
    14108 35cc  08/11 05:16:46 ### VixDiskLib: VixDiskLib_Disconnect: Disconnect.
    8576  2bd0  08/11 05:16:51 ### DISKLIB-LIB   : numIOs = 700000 numMergedIOs = 0 numSplitIOs = 0
    14108 35cc  08/11 05:17:01 ### VixDiskLib: VixDiskLib_EndAccess: Disk access completed.

    &

    6196  1ea4  08/11 05:30:51 ### VMware VixDiskLib (6.0) Release build-2498720196  2958  08/11 05:30:51 ### 2015-08-11T05:30:51.306+02:00 info -[10584] [Originator@6876 sub=ThreadPool] Thread enlisted
    6196  2bbc  08/11 05:30:51 ### 2015-08-11T05:30:51.306+02:00 info -[11196] [Originator@6876 sub=ThreadPool] Thread enlisted
    6196  1ea4  08/11 05:30:51 ### FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
    6196  1ea4  08/11 05:30:51 ### FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
    6196  1ea4  08/11 05:30:51 ### FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
    6196  1ea4  08/11 05:30:51 ### FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
    6196  1ea4  08/11 05:30:51 ### FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
    6196  1ea4  08/11 05:30:51 ### PREF early PreferenceGet(poll.forceSelect), using default

    6196  1ea4  08/11 05:30:51 ### POLL Using the WSAPoll API Implementation for PollDefault
    6196  1ea4  08/11 05:30:51 ### VixDiskLibVim: VixDiskLibVim_Init: Initialization is completed.
    6196  357c  08/11 05:30:51 ### Mntapi_Init Asked - 2.2 Served - 2.2 was successful,TempDirectory: C:\Windows\TEMP\vmware-SYSTEM.
    6196  1ea4  08/11 05:30:51 ### VixDiskLib: VixDiskLib_Cleanup: Remove previous mount points and clean up .
    6196  1ea4  08/11 05:30:51 ### VixDiskLib: VixDiskLib_Connect: Establish connection.
    6196  1ea4  08/11 05:30:51 ### VixDiskLib: Resolve host.

     

    Where do these locations refer to? Is it the proxy or the vcenter or perhaps the esx node?

  • Re: VixDiskLib.log Clarification Question
    Posted: 08-11-2015, 10:39 AM
    • Aplynx is not online. Last active: 05-22-2019, 12:46 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,587

    This would be on the proxy machine where the log is located. This refers to a known VMware issue when utilizing HotAdd where the backups may fail because these folders are not empty. 

  • Re: VixDiskLib.log Clarification Question
    Posted: 08-11-2015, 10:50 AM

    Got it. The C:\windows\temp\vm-ware-system & C:\program data\vmware refer both to the C:\ partition of the proxy.

     

    Only the majority (if not all) subclients run on san mode (manually set). The one that has this issue is using san mode.

     

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy