# Not able to remove chunks from the continuous oplog

**URL:** <https://forums.percona.com/t/not-able-to-remove-chunks-from-the-continuous-oplog/14058>\
**Category:** Percona Backup for MongoDB\
**Tags:** percona, mongodb, closed-no-reply\
**Created:** [January 23, 2022, 6:21pm UTC](https://forums.percona.com/t/not-able-to-remove-chunks-from-the-continuous-oplog/14058 "2022-01-23T18:21:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Divyansh\_Rai](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/divyansh_rai/32/5665_2.png) [@Divyansh\_Rai](https://forums.percona.com/u/Divyansh_Rai)\
**Post date:** [January 23, 2022, 6:21pm UTC](https://forums.percona.com/t/not-able-to-remove-chunks-from-the-continuous-oplog/14058/1 "2022-01-23T18:21:10Z")

</div>

If there’s a chunk like this,

```auto
PITR chunks [6.83MB]:
    2022-01-19T23:39:05 - 2022-01-23T01:00:38

```

executing the below command doesn’t seem to cut off the older than 21st PITR chunks

```auto
ec2-user@ip-xxx-xxx-xxx-xxx ~]$ pbm delete-pitr --older-than 2022-01-21T10:01:18
Are you sure you want delete chunks? [y/N] y

```

After executing the pbm status, I can see the same chunk with same size. These are the logs.

```auto
Jan 23 16:53:32 ip-xxx-xxx-xxx-xxx.us-west-1.compute.internal pbm-agent[106688]: 2022-01-23T16:53:32.000+0000 I got command deletePitr <ts: 1642956812>
Jan 23 16:53:32 ip-xxx-xxx-xxx-xxx.us-west-1.compute.internal pbm-agent[106688]: 2022-01-23T16:53:32.000+0000 I got epoch {1642955964 4}
Jan 23 16:53:32 ip-xxx-xxx-xxx-xxx.us-west-1.compute.internal pbm-agent[106688]: 2022-01-23T16:53:32.000+0000 D [deletePitr] get lock: duplicate operation: 61ed880cbf8928eb33a388a8 [Delete PITR chunks]
Jan 23 16:53:32 ip-xxx-xxx-xxx-xxx.us-west-1.compute.internal pbm-agent[106688]: 2022-01-23T16:53:32.000+0000 D [deletePitr] skip: lock not acquired

```

This makes it impossible to keep PIT recovery limited to the last 7 days as far as I can see. Is this a bug or am I doing something wrong?