Confused about pruning... pruned revisions are still available?

Support
#1

I pruned a B2 repo with 1171 revsions, using -r 1-1170. The output showed a vast number of chunks permanently deleted.

When I ran check, it says all chunks referenced by the snapshot for revisions 1-1170 exist.

I did not expect that. B2 size is unchanged, and the bucket keeps only last version of the file.
Out of curiosity, I discovered that a restore allowed be to select the pruned revisions, and successsfully recover files.

What am I misunderstanding here? Does prune not delete the revisions?
Thanks!

#2

Show the full command. Did it finish successfully? Does the key have rename and delete access to the bucket?

#3

Using web

Running prune command from C:\Users\alf/.duplicacy-web/repositories/localhost/all
Options: [-log prune -storage m_docs -r 1-1170]
2026-03-27 21:55:21.792 INFO STORAGE_SET Storage set to b2://m-bkup/docs
2026-03-27 21:55:22.453 INFO BACKBLAZE_URL Download URL is: https://f002.backblazeb2.com
2026-03-27 21:55:42.607 INFO FOSSIL_COLLECT Fossil collection 1 found
2026-03-27 21:55:42.607 INFO FOSSIL_DELETABLE Fossils from collection 1 is eligible for deletion
2026-03-27 21:55:42.607 INFO PRUNE_NEWSNAPSHOT Snapshot m_docs_b2 revision 1171 was created after collection 1
2026-03-27 21:55:43.313 INFO CHUNK_DELETE The chunk a7b14e9ffaadefc6ead4f3571806b758287ae4aa14a267fb3b045d1aa62f7341 has been permanently removed
2026-03-27 21:55:43.994 INFO CHUNK_DELETE The chunk cdda64c91e6e6c6cb3209b6b8f0ef406939f468a2a5879e97e04d2fb1df22b1c has been permanently removed
2026-03-27 21:55:44.770 INFO CHUNK_DELETE The chunk 5e9eeba720a397d567e4291a72d2e461bfe2051754c0cfeb88e62ad0d235f44e has been permanently removed

Etc…

Rerunning this command:

Running prune command from C:\Users\alf/.duplicacy-web/repositories/localhost/all
Options: [-log prune -storage m_docs -r 1-1170]
2026-03-28 12:52:39.375 INFO STORAGE_SET Storage set to b2://m-bkup/docs
2026-03-28 12:52:39.715 INFO BACKBLAZE_URL Download URL is: https://f002.backblazeb2.com
2026-03-28 12:52:58.612 INFO SNAPSHOT_NONE No snapshot to delete

Key capabilities:
deleteFiles, listBuckets, listFiles, readBucketEncryption, readBucketReplications, readBuckets, readFiles, shareFiles, writeBucketEncryption, writeBucketReplications, writeFiles

#4

Try adding -id argument, to avoid relying on default detection

   -id <snapshot id>            delete revisions with the specified 
                                snapshot ID instead of the default one
   -all, -a                     match against all snapshot IDs

https://github.com/gilbertchen/duplicacy/wiki/prune

#5

Thanks. Adding the -id removed the revisions from the B2 snapshots folder. The original B2 chunks are all still present, though “duplicacy check” indicates the storage dropped to 30% of what it had been. I’m unsure if this is a B2 thing, or the orphaned chunks remain until a second prune occurs. Any thoughts here?

As a side note -all alone, had no effect on B2.