From 0857e81a6ccc98d2f495f09ef73e1f1e3d213cf1 Mon Sep 17 00:00:00 2001 From: Mechiel Lukkien Date: Sat, 8 Mar 2025 09:03:41 +0100 Subject: [PATCH] Prevent spurious warnings about thread ids not being correct for messages that are expunged but not yet erased. Erasing a message (removing the message file from the file system) was made a separate step a few days ago. The verifydata command checks for consistency of the data, but didn't correctly skip checking expunged-but-not-yet-erased messages, leading to the warning. A similar consistency check in store/account.go does check for that. I was warned by my nightly backup+veridata script. --- verifydata.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/verifydata.go b/verifydata.go index 9e60c4a..6149ea1 100644 --- a/verifydata.go +++ b/verifydata.go @@ -310,7 +310,7 @@ possibly making them potentially no longer readable by the previous version. } for i, pid := range m.ThreadParentIDs { am := store.Message{ID: pid} - if err := db.Get(ctxbg, &am); err == bstore.ErrAbsent { + if err := db.Get(ctxbg, &am); err == bstore.ErrAbsent || err == nil && am.Expunged { continue } else if err != nil { return fmt.Errorf("get ancestor message: %v", err)