Solved

File System Agent issue on Windows, Optimized Scan fails

  • 8 December 2021
  • 1 reply
  • 529 views

Badge

Hello

 

I am wondering if anyone has any insight as to my issue.

Backs up for failing for one drive(D) on a windows machine.

The error is below:

Optimized scan could not complete scan on volume [D:\] as the database processing reported disk full error. This volume has [87591624704] bytes of free space available. SQLite is using [C:\Windows\TEMP\] as the path for its temporary usage, and this volume has [33618767872] bytes of free space available.

 

Here is the logs:

80  500   11/30 01:59:56 1397513 CWorkerBasic::ProcessDCError(4395) - DC DB processing interrupted due to SQLite reporting disk full error when scanning volume [D:\]; This volume has [102383620096 bytes] of free space available; SQLite is using [C:\Windows\TEMP\] as the path for its temporary usage, and this volume has [57228607488 bytes] of free space available
1880  500   11/30 01:59:56 1397513 CWorkerBasic::ProcessFoldersFilesAndHardLinks(2136) - --- 134:45.645470 DatabasePath=[\\?\Volume{b9177a39-0000-0000-0000-100000000000}\System Volume Information\Commvault\Data Classification\dc_001.db], ModifiedPath=[D:\]
1880  500   11/30 01:59:56 1397513 CWorkerBasic::ProcessPathsUsingOptimizedScan(1939) - ProcessFoldersFilesAndHardLinks failed, DatabasePath=[\\?\Volume{b9177a39-0000-0000-0000-100000000000}\System Volume Information\Commvault\Data Classification\dc_001.db], ModifiedPath=[D:\], error=0xEDB0000D:{CWorkerBasic::ProcessFoldersFilesAndHardLinks(2187)} + {CDataClassifierDatabase::GenerateSnapshot(1582)} + {FX::CDatabaseBase::Execute(719)/Failed to execute, Command=[INSERT OR REPLACE INTO temp.ParentPaths (FileId, ParentFileId, FullPath, MetaFullPath, IsMetaData, CaseSensitiveFlags) SELECT l.FileId AS FileId, ifnull(r.ParentFileId,0) AS ParentFileId, ifnull(nullif(r.FullPath,'\'),'')||'\'||l.FullPath AS FullPath, ifnull(nullif(r.MetaFullPath,'\'),'')||'\'||l.MetaFullPath AS MetaFullPath, l.IsMetaData OR r.IsMetaData AS IsMetaData, l.CaseSensitiveFlags AS CaseSensitiveFlags FROM temp.ParentPaths l LEFT JOIN temp.ParentPaths r ON l.ParentFileId=r.FileId AND r.FileId<>0 WHERE l.ParentFileId<>0;]} + {FX::CDatabaseBase::Execute(716)/SQL.0xD.(13 (0xD): Insertion failed because database is full)-SQLite Exception, SQLITE_FULL[13]: database or disk is full}
1880  500   11/30 01:59:56 1397513 CWorkerBasic::ProcessPathsUsingOptimizedScan_ReviewPaths(2045) - Identifying mount paths to process, FollowMountPath=[1]
1880  500   11/30 01:59:56 1397513 CWorkerBasic::ProcessPathsUsingOptimizedScan(1526) - --- 134:45.667430 1 paths to process
1880  500   11/30 01:59:56 1397513 CWorkerBasic::ProcessPathsUsingOptimizedScan_UnscannedDisposition(2123) - 1 paths could not be scanned using Optimized Scan; Falling back to the other scan methods
1880  500   11/30 01:59:56 1397513 CWorkerBasic::ProcessPathsUsingOptimizedScan_UnscannedDisposition(2127) - OriginalPath=[D:\], MountPath=[]
1880  500   11/30 01:59:56 1397513 CWorkerBasic::ProcessPathsUsingChangeJournal(3315) - +++ 1 paths to process
1880  500   11/30 01:59:56 1397513 CWorkerBasic::ProcessPathGroupUsingChangeJournal(3432) - +++ Volume=d:\, PathCount=1
1880  500   11/30 01:59:56 1397513 CChangeJournalFind::addScanPath(412) - Adding Scan Path D:\
1880  500   11/30 01:59:56 1397513 CWorkerBasic::ChangeJournalIteration(2885) - Processing Change journal scan, disabling the job progress update by bytes and using the [LineBased] collect file splitting
1880  500   11/30 01:59:56 1397513 CWorkerBasic::ChangeJournalIteration(2902) - Starting Change Journal scan, Volume=[d:\]
1880  500   11/30 01:59:56 1397513 CChangeJournal::addFilterPath(1683) - Adding target FRN Index map entry [0x0005000000000005] for path [D:\]
1880  500   11/30 01:59:56 1397513 CChangeJournalFind::scanOnVolume(794) - Scan, Volume=D:\
1880  500   11/30 01:59:56 1397513 CChangeJournal::doesExistingCJNeedToBeReCreated(591) - Latest expected size [4096]MB is greater than stored calculated size [1279 MB]; change journal for volume [\\?\Volume{b9177a39-0000-0000-0000-100000000000}\] will be re-created
1880  500   11/30 01:59:56 1397513 CChangeJournal::EnableJournaling(723) - User override key for change journal size not found; The size will be calculated for volume [\\?\Volume{b9177a39-0000-0000-0000-100000000000}\]
1880  500   11/30 01:59:56 1397513 CChangeJournal::EnableJournaling(754) - For volume [\\?\Volume{b9177a39-0000-0000-0000-100000000000}\], calculated change journal size is [0x100000000] bytes and allocation delta size is [0x33334000] bytes; (4194304 KB / 838864 KB) (4194 MB / 838 MB)
1880  500   11/30 01:59:56 1397513 CVPlatformInfo::setRegValue() - Invalid arguments.
1880  500   11/30 01:59:56 1397513 CChangeJournal::EnableJournaling(820) - Could not set actual size of volume [\\?\Volume{b9177a39-0000-0000-0000-100000000000}\] that we need to monitor, in registry.
1880  500   11/30 01:59:56 1397513 CChangeJournalFind::scanOnVolume(818) - Previous job did not complete; using last good USN from backup status info, Volume=\\?\Volume{b9177a39-0000-0000-0000-100000000000}\
1880  500   11/30 01:59:56 1397513 CChangeJournalFind::scanOnVolume(836) - Volume=[D:\], Volume=\\?\Volume{b9177a39-0000-0000-0000-100000000000}\, RefTime=2021/11/17 21:00:42.000000, FullUsn=213360256, LastUsn=3640115200, LastGoodUsn=1430356288, JournalId=132671164490433581 (2021-06-02 8:07:29 AM), Volume Serial Number=480124061, Bag=[<~~>]
1880  500   11/30 01:59:56 1397513 CChangeJournalFind::scanOnVolume(862) - Starting USN for scan is 1430356288

 

 

 

 

One interesting is that twice in the past 3 weeks the jobs actually worked.

Got the same error about the optimized scan failing, but it fell back to the regular scan, and that seemed to work.

 

icon

Best answer by Mike Struening 8 December 2021, 21:19

View original

1 reply

Userlevel 7
Badge +23

Thanks for the post!

How much space does the drive normally have?  There may be something on the server that is filling up drives if this is happening intermittently.  Due to the SQLite temp usage, there’s only 30 GB free on the C: drive (which is relative to the volume metadata need).

Take a look at the doc below.  Optimized Scan uses a database to track the metadata which is likely why it is failing:

https://documentation.commvault.com/11.25/expert/18464_file_scan_methods_for_windows_file_system_agent.html

Can the size of the c: volume be increased?

 

Reply