Skip to main content
Question

Strange log entries regarding pruning blocks from DDB - is this a cause for concern?

  • August 8, 2025
  • 2 replies
  • 48 views

Hello Commvault Community!

In one environment, we noticed that strange entries appeared in the logs regarding block pruning as part of deduplication:

 

SIDBPrune.log - from August 5, 2025


11512 5468  08/05 03:00:45 ### 1-3 OpenIdx:3330 Cannot lock chunk [2499152].
11512 5468  08/05 03:00:45 ### 1-3 PruneChunk:1391 Cannot get child information. Folder [E:\LOCAL_STG\Folder_06.17.2016_11.59\CV_MAGNETIC\V_393205\CHUNK_2499152], Error [0x80070003:{CQiDirectory::Open(106)/SearchPath=[E:\LOCAL_ABC\Folder_06.17.2016_11.59\CV_MAGNETIC\V_393205\CHUNK_2499152\*]} + {FXFile::CVFindFirstFile(1821)/W32.3.(The system cannot find the path specified. (ERROR_PATH_NOT_FOUND.3))-FindFirstFileW failed, Path=[\\?\E:\LOCAL_ABC\Folder_06.17.2016_11.59\CV_MAGNETIC\V_393205\CHUNK_2499152\*]}]
11512 4f14  08/05 03:00:45 ### 1-3 PruneChunk:1391 Cannot get child information. Folder [E:\LOCAL_ABC\Folder_06.17.2016_11.59\CV_MAGNETIC\V_393205\CHUNK_2499152], Error [0x80070003:{CQiDirectory::Open(106)/SearchPath=[E:\LOCAL_STG\Folder_06.17.2016_11.59\CV_MAGNETIC\V_393205\CHUNK_2499152\*]} + {FXFile::CVFindFirstFile(1821)/W32.3.(The system cannot find the path specified. (ERROR_PATH_NOT_FOUND.3))-FindFirstFileW failed, Path=[\\?\E:\LOCAL_ABC\Folder_06.17.2016_11.59\CV_MAGNETIC\V_393205\CHUNK_2499152\*]}]
11512 4640  08/05 03:00:45 ### 1-3 PruneChunk:1421 Chunk [E:\LOCAL_STG\Folder_06.17.2016_11.59\CV_MAGNETIC\V_393205\CHUNK_2499152] does not exist
11512 45a4  08/05 03:00:45 ### 1-3 PruneChunk:1421 Chunk [E:\LOCAL_STG\Folder_06.17.2016_11.59\CV_MAGNETIC\V_393205\CHUNK_2499152] does not exist

 

However, strangely enough, in another log from the previous day, we see that this chunk was deleted, and on August 5th, the system was still querying for it.

 

SIDBPrune.log - from August 4, 2025

11512 5a78  08/04 13:02:16 ### 1-1 DedupPrnPhase1:4984 Vol [E:\LOCAL_ABC\Folder_06.17.2016_11.59\CV_MAGNETIC\V_393205], # Chunks [2]
11512 5a78  08/04 13:02:16 ### 1-1 DedupPrnPhase1:5012 Chunk [2499152]
11512 5a78  08/04 13:02:16 ### 1-1 PruneChunk:1572 Removed [E:\LOCAL_ABC\Folder_06.17.2016_11.59\CV_MAGNETIC\V_393205\CHUNK_2499152\CHUNK_META_DATA_2499152]
11512 5a78  08/04 13:02:16 ### 1-1 PruneChunk:1572 Removed [E:\LOCAL_ABC\Folder_06.17.2016_11.59\CV_MAGNETIC\V_393205\CHUNK_2499152\CHUNK_META_DATA_2499152.idx]
11512 5a78  08/04 13:02:16 ### 1-1 DedupPrnPhase1:5012 Chunk [2499773]

 

 

SIDBPhisicalDeletes.log
 

 5a78 08/04 13:02:16 Deletion      MountPathID=1   v_393205\chunk_2499152           Chunk-metadata-file
  5a78 08/04 13:02:16 Deletion      MountPathID=1   v_393205\chunk_2499152           Chunk-metadata-index-file
  45a4 08/05 03:00:45 Deletion      MountPathID=1   v_393205\chunk_2499152\sfile_1  
  45a4 08/05 03:00:45 Deletion      MountPathID=1   v_393205\chunk_2499152           SIDX
  5468 08/05 03:00:45 Deletion      MountPathID=1   v_393205\chunk_2499152           0
  5468 08/05 03:00:45 Deletion      MountPathID=1   v_393205\chunk_2499152           0  CTRL               
  4640 08/05 03:00:45 DoesNotExist  MountPathID=1   v_393205\chunk_2499152          
  45a4 08/05 03:00:45 DoesNotExist  MountPathID=1   v_393205\chunk_2499152          
  5468 08/05 03:00:45 DoesNotExist  MountPathID=1   v_393205\chunk_2499152          
  4640 08/05 03:00:45 Deletion      MountPathID=1   v_393205\chunk_2499152           CHUNKMAP_TRAILER_2499152
  45a4 08/05 03:00:45 Deletion      MountPathID=1   v_393205\chunk_2499152           CHUNKMAP_TRAILER_2499152
  5468 08/05 03:00:45 Deletion      MountPathID=1   v_393205\chunk_2499152           CHUNKMAP_TRAILER_2499152
  4f14 08/05 03:00:45 DoesNotExist  MountPathID=1   v_393205\chunk_2499152 

 

The CommCell Console GUI doesn’t show any block pruning delays, DataAging errors, or hanging data waiting to be deleted in the DiskLibrary structure. We're just wondering if this is a cause for concern or if this might be standard behavior for the Commvault system.

 

Thanks&Regards,
Kamil Gniado

2 replies

Forum|alt.badge.img+9
  • Vaulter
  • August 13, 2025

Hi ​@Kamil,

 

The below error indicates that the system cannot find the specified path during

{FXFile::CVFindFirstFile(1821)/W32.3.(The system cannot find the path specified. (ERROR_PATH_NOT_FOUND.3))-FindFirstFileW failed, Path=[\\?\E:\LOCAL_ABC\Folder_06.17.2016_11.59\CV_MAGNETIC\V_393205\CHUNK_2499152\*]}]

→ Verify Path Accessibility: Ensure that the path specified in the error message exists on the MA. 

→ Check Antivirus Exclusions: Make sure that antivirus software is not locking the files or directories involved in the pruning process. Configure antivirus exclusions for Commvault directories.https://documentation.commvault.com/v11/expert/8665_antivirus_exclusions_for_windows.html

 

Regards,

Wasim


sbhatia
Vaulter
Forum|alt.badge.img+9
  • Vaulter
  • August 13, 2025

To start with, you did a great job identifying that the chunks in question were already deleted. What you’re seeing in the logs is part of normal pruning and data aging checks, where the system verifies chunk existence before removing any remaining references. The “cannot find the path specified” or “does not exist” messages simply confirm that those folders are no longer present. Since the Console shows no pruning or data aging issues, this is routine cleanup behavior and not a cause for concern. Just ensure antivirus exclusions are in place to avoid any file lock interference, but otherwise everything looks normal.