Untraceable long operation (query?) during backup

ts678 · May 22, 2020, 11:08am

I’m not sure it would log. I have it set, but the code is missing the parameter I guess it should give:

EDIT: had the wrong ExecuteNonQuery reference before

duplicati/duplicati/blob/41ea491bd77d39aaf33611ddf2e377c7e08c485a/Duplicati/Library/Main/Database/LocalBackupDatabase.cs#L733-L738


      
          if (!exclusionPredicate(path, size))
          {
              cmdAdd.SetParameterValue(1, row.GetInt64(1));
              cmdAdd.SetParameterValue(2, row.GetInt64(2));
              cmdAdd.ExecuteNonQuery();
          }

In terms of the ExecuteNonQuery call, I’m not sure where it’s wanting to go, but I wonder if it’s here:

github.com

duplicati/duplicati/blob/41ea491bd77d39aaf33611ddf2e377c7e08c485a/Duplicati/Library/Main/Database/ExtensionMethods.cs#L65-L68


      
          public static int ExecuteNonQuery(this System.Data.IDbCommand self, bool writeLog)

          {

              return ExecuteNonQuery(self, writeLog, null, null);

          }

Perhaps you can figure out the calling to see if you can get that INSERT loop logged, or breakpoint it.
It sure looks like a loop to me. You could try breakpoint and/or log something after loop, near Commit.
If Visual Studio can actually pause the program, some thread might be seen in the middle of the loop.
There are lots of threads though. My debug approach (using dnSpy) would probably try to breakpoint.