Resolved Micro Freezes in Mojave 10.14.6

[AshFriedrich]

Hi!

I've been getting micro freezes at least every minute at the same time as these messages appear in Console:

error    16:29:13.383189 +0200    deleted    unable to create CacheDeleteDaemonVolume for <private>
error    16:29:13.390466 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    16:29:13.411616 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    16:29:13.468017 +0200    sandboxd    Sandbox: deleted(470) deny(1) file-read-data /Volumes/HD1
error    16:29:41.661544 +0200    deleted    unable to create CacheDeleteDaemonVolume for <private>
error    16:29:41.669165 +0200    kernel    Sandbox: deleted(470) deny(1) file-read-data /Volumes/HD1
error    16:29:41.669420 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    16:29:41.671333 +0200    kernel    Sandbox: deleted(470) deny(1) file-read-data /Volumes/HD2
error    16:29:41.671418 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted

HD1 and HD2 are my two partitions used for storage (not OS). HD1 is SSD and HD2 is a regular HDD.

Anyone have any idea what could be causing this or how to go about fixing it?

I have a mid-2012 13" MBP (2.9GHz i7, 16GB RAM, Intel HD Graphics 4000) running Mojave 10.14.6

 

[Wando64]

Is the SSD external USB3 connected?
Asking because I was having similar problems (Freezes, sometimes not so "micro") with a Sandisk Extreme SSD. Got rid of it and the problem disappeared.
Probably a different issue, but... just in case.

 

[AshFriedrich]

Hi Wando
No, all the harddrives are internal. The SSD in the normal HD slot and the HDD in the Optical Drive slot (one of the reasons I love the old MBPs ) I've had them connected for a long time before this issue appeared.

 

[AshFriedrich]

For posterity: I fixed this by running the full maintenance task of this great app Onyx, which is also free. Still not sure why the issue happened in the first place but yey, no more freezes!

 

[AshFriedrich]

So no, it's not resolved after all, the freezes are coming back. I'd really like to understand what these processes are and why it's necessary for them to clog the system every minute.

error    13:39:54.063102 +0200    deleted    unable to create CacheDeleteDaemonVolume for <private>
error    13:39:54.070436 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    13:39:54.070403 +0200    kernel    Sandbox: deleted(646) deny(1) file-read-data /Volumes/HD2
error    13:39:54.075717 +0200    kernel    Sandbox: deleted(646) deny(1) file-read-data /Volumes/HD1
error    13:39:54.075753 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    13:40:23.293046 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    13:40:23.310385 +0200    kernel    Sandbox: deleted(646) deny(1) file-read-data /Volumes/HD2
error    13:40:23.312429 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    13:40:23.370448 +0200    deleted    unable to create CacheDeleteDaemonVolume for <private>
error    13:40:53.221891 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    13:40:53.253240 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    13:40:53.253210 +0200    kernel    Sandbox: deleted(646) deny(1) file-read-data /Volumes/HD1
error    13:40:53.302603 +0200    deleted    unable to create CacheDeleteDaemonVolume for <private>
error    13:40:54.051010 +0200    kernel    Sandbox: deleted(646) deny(1) file-read-data /Library/MessageTracer/SubmitDiagInfo.default.domains.searchtree

 

[Wando64]

So no, it's not resolved after all, the freezes are coming back. I'd really like to understand what these processes are and why it's necessary for them to clog the system every minute.

error    13:39:54.063102 +0200    deleted    unable to create CacheDeleteDaemonVolume for <private>
error    13:39:54.070436 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    13:39:54.070403 +0200    kernel    Sandbox: deleted(646) deny(1) file-read-data /Volumes/HD2
error    13:39:54.075717 +0200    kernel    Sandbox: deleted(646) deny(1) file-read-data /Volumes/HD1
error    13:39:54.075753 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    13:40:23.293046 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    13:40:23.310385 +0200    kernel    Sandbox: deleted(646) deny(1) file-read-data /Volumes/HD2
error    13:40:23.312429 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    13:40:23.370448 +0200    deleted    unable to create CacheDeleteDaemonVolume for <private>
error    13:40:53.221891 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    13:40:53.253240 +0200    deleted    Failed to enumerate snapshots for volume <private>: Operation not permitted
error    13:40:53.253210 +0200    kernel    Sandbox: deleted(646) deny(1) file-read-data /Volumes/HD1
error    13:40:53.302603 +0200    deleted    unable to create CacheDeleteDaemonVolume for <private>
error    13:40:54.051010 +0200    kernel    Sandbox: deleted(646) deny(1) file-read-data /Library/MessageTracer/SubmitDiagInfo.default.domains.searchtree

It looks as if the system is trying to create a snapshot but it is not succeeding.
The creation of snapshot is a normal operation during upgrades, updates, backups, but I have no idea why this should be failing.
Did you or any app recently installed changed any of the permissions on your disk?

Re: Snapshots

Working with macOS Snapshots

Snapshots are a feature of the Mac's APFS file system that allow you to roll back your Mac to a previous state. A good tool to have when you upgrading the OS.

blog.macsales.com

[automerge]1595592642[/automerge]
Did you try to run "First aid" on the drives?

 

[AshFriedrich]

It looks as if the system is trying to create a snapshot but it is not succeeding.
The creation of snapshot is a normal operation during upgrades, updates, backups, but I have no idea why this should be failing.
Did you or any app recently installed changed any of the permissions on your disk?

Did you try to run "First aid" on the drives?

Timemachine is disabled in preferences and I get these messages literaly every minute. I am not doing any upgrades, updates or backups. I have done "First Aid" on all drives, including the OS drive.

I have not changed any permissions on the disks. It's hard to say if any app has done it. I checked permissions on the base levels of the disks, they look like this:

drwxrwxr-x  65 root  wheel   2.2K 17 Oct  2019 HD1/
drwxrwxr-x  38 root  staff   1.3K 22 Jun 18:04 HD2/
lrwxr-xr-x   1 root  wheel     1B 16 Jul 12:32 OS@ -> /

I also tried to disable snapshots with Terminal: "sudo tmutil disable" but the OS is still trying to make snapshots. Is there another way to totally disable snapshots being taken?

The two drives are formatted as HFS+ while my OS drive is APFS. Could this be part of the problem?

 

[Wando64]

I also have a mixture of internal APFS and external HFS+ but I am not seeing any problem.

Sorry, this is now beyond me. Hopefully someone else will step in with some advice.

 

[doyouspeakwingdings]

Timemachine is disabled in preferences and I get these messages literaly every minute. I am not doing any upgrades, updates or backups. I have done "First Aid" on all drives, including the OS drive.

I have not changed any permissions on the disks. It's hard to say if any app has done it. I checked permissions on the base levels of the disks, they look like this:

drwxrwxr-x  65 root  wheel   2.2K 17 Oct  2019 HD1/
drwxrwxr-x  38 root  staff   1.3K 22 Jun 18:04 HD2/
lrwxr-xr-x   1 root  wheel     1B 16 Jul 12:32 OS@ -> /

I also tried to disable snapshots with Terminal: "sudo tmutil disable" but the OS is still trying to make snapshots. Is there another way to totally disable snapshots being taken?

The two drives are formatted as HFS+ while my OS drive is APFS. Could this be part of the problem?

Did you ask Apple? What do they say?

 

[AshFriedrich]

I have asked in discussions.apple.com but not gotten any reply there. It seems to be more active here.

 

[Airs0urce]

Same thing for me. Some moment I get freezes, then I look in Activity Monitor and I see "deleted" process eats 70% cpu all the time. Then I open Console, filter messages by "deleted" and I see a lot of errors like these:

error 13:38:22.639004+0700 deleted_helper APFSIOC_GET_PURGEABLE_STATS: Inappropriate ioctl for device
error 13:41:46.045212+0700 deleted fs_snapshot_list failed: Operation not supported
error 13:41:46.045248+0700 deleted Failed to enumerate snapshots for volume <private>: Operation not supported
error 13:41:46.047553+0700 deleted_helper APFSIOC_GET_PURGEABLE_STATS: Inappropriate ioctl for device


And logs keep going fast. After that the only thing I can do is to reboot my laptop (I have Macbook Pro 13 2020).
Another solution I just started using - I installed App Tamper app and restricted "deleted" process using more than 1% of CPU. Also wrote to Apple in Feedback Assistant, but not sure if they will read, last couple years they stopped responding my bugreports

 

[AshFriedrich]

Same thing for me. ...

Sorry to hear and also interesting since you have a 2020 MBP and I have a 2012 MBP. So we can at least safely assume it's a pure software problem not tied to any specific MBP model. I'm guessing you also tried the methods mentioned above to "completely" disable snapshots and timemachine?

I'd be interested to check out the app you mention, could you post a link to it? I tried googling for it but maybe the name is just to common. Sounds like a very useful thing if it can restrict CPU usage on a process basis.

 

[Airs0urce]

Sorry to hear and also interesting since you have a 2020 MBP and I have a 2012 MBP. So we can at least safely assume it's a pure software problem not tied to any specific MBP model. I'm guessing you also tried the methods mentioned above to "completely" disable snapshots and timemachine?

I'd be interested to check out the app you mention, could you post a link to it? I tried googling for it but maybe the name is just to common. Sounds like a very useful thing if it can restrict CPU usage on a process basis.

I didn't try to disable snapshots and timemachine. I'm using TimeMachine and just don't want disabling it. Didn't research about Snapshots too.
And here is the link to the application: https://www.stclairsoft.com/AppTamer/index.html

 

[Airs0urce]

Huh, I made mistake. Name of the app is App Tamer, not App Tamper

 

[AshFriedrich]

Huh, I made mistake. Name of the app is App Tamer, not App Tamper

Thanks for that, I'm checking it out. I never thought about restricting the process so I did some more research and there's a command called 'renice' that we can use in terminal too to lower the priority of processes. I'm gonna try some different things with this and report back here.

Did it make any difference for you to disable snapshots/timemachine Airs0urce?

 

[Airs0urce]

Thanks for that, I'm checking it out. I never thought about restricting the process so I did some more research and there's a command called 'renice' that we can use in terminal too to lower the priority of processes. I'm gonna try some different things with this and report back here.

Did it make any difference for you to disable snapshots/timemachine Airs0urce?

Lower the priority and restricting cpu usage are different things. Not sure how App Tamer does it under the hood, but it just doesn't let process to use more than you set even if there is still free cpu resources.
But renice as I know will only change priority, which means that yes, you can get rid of freezes, but when you don't do any activity on laptop, that process still can use free resources (and wasting battery/making computer hot) that you don't use to move windows or something else.

About snapshots and TimeMachine - I didn't try to disable them.

 

[AshFriedrich]

Thank you for this, I'm trying to figure out the app now it looks promising.

 

[doyouspeakwingdings]

Thank you for this, I'm trying to figure out the app now it looks promising.

Have you figured it out?