Object stuck in GC cycle, part N

Expected Behavior

Object deleted, object gone.

Current Behavior

Feb 24 08:31:24 metis1 neofs-node[161827]: info        log/log.go:13        local object storage operation        {"shard_id": "PRYXSqmUXp4ZNZDLqXsgcR", "address": "7ZVSQHtioVRiDT2btN9xEmQhczXV9vryCEAHUawfD8Sc/6GXUGR7SrPsZF9k77qtmrfyVSDRUDK9FPPzw8DSrWbz7", "op": "metabase DELETE"}
Feb 24 08:31:34 metis1 neofs-node[161827]: info        log/log.go:13        local object storage operation        {"shard_id": "PRYXSqmUXp4ZNZDLqXsgcR", "address": "7ZVSQHtioVRiDT2btN9xEmQhczXV9vryCEAHUawfD8Sc/6GXUGR7SrPsZF9k77qtmrfyVSDRUDK9FPPzw8DSrWbz7", "op": "metabase DELETE"}

Possible Solution

Fix something.

Steps to Reproduce (for bugs)

Unknown, but seems to be related to expiration handling and big objects.

Context

Mainnet, single shard of a single node.

Regression

Doesn't look like.

Your Environment

• Version used: 0.51.1
• Server setup and configuration: mainnet
• Operating System and version (uname -a): Debian stable

Start by tracing expiration handling for big objects and the metabase DELETE operation described in the logs. Reproduce the issue if possible on the reported 0.51.1 mainnet setup, then verify that an expired object is deleted once and no longer remains stuck in the GC cycle.