Why are these files created since installing Tahoe 26.1?

Deleting Time Machine local snapshots

Why are these files created since installing Tahoe 26.1? com.apple.TimeMachine.2025-11-09-051649.backup.

I read a few places and they suggest using tmutil to delete it, but it doesn't let me.

I get the following error message.

Failed to delete local snapshot '2025-11-17-031807'

POSIXError(_nsError: Error Domain=NSPOSIXErrorDomain Code=70 "Stale NFS file handle")

80GB lost and I can't recover it.

Please help.

Regards.

János


[Edited by Moderator]

Mac mini, macOS 26.1

Posted on Nov 21, 2025 12:51 AM

Reply
Question marked as Top-ranking reply

Posted on Nov 21, 2025 7:42 AM

The files are created by Time Machine. TM will create and store a local snapshot hourly for the last 24 hours plus the last complete backup for each TM destination that wasn't connected in the last 24 hours. Those are in addition to the backups written to the destination disk(s). TM does this for quick access to the backups (and so you have some backups even if the destination disk is not available). You can see that if you use the TM browser because the snapshots are available immediately, then if available the backup source is added.


The way to delete local TM snapshots (if you feel you must) is in Disk Utility. Select the Data volume in the sidebar (or the volume group, the right under the container disk) then select View menu > Show APFS Snapshots.



With that, you will see the snapshots listed.



You can select one or more and click the (–) button at the bottom to delete them. If you select them all and let DU calculate, it will show the summary 'private size' at the bottom, that's the total utilization of space for snapshots (it's not the sum of the individual sizes). Is that where you are getting the '80 GB lost' value? I ask because I don't see that usage anywhere in your screenshots.


You can delete them, but TM will just recreate them so the regained space is only temporary.


As colleagues have pointed out, you may need to reconnect the NAS as a TM backup to be able to get around the "Stale NFS file handle" error. Assuming you haven't erased the backups on the Synology NAS, if you select it as a TM destination you should be prompted to Claim the Backups, and you should choose that option.


Bigger picture, personally I have no issues with TM backups to a Synology DS223j. Five Macs in the house back up to it, and I also have a set of 4 TB SSDs that I use as secondary backups and connect once a week to run a backup then swap the SSDs to an office location (that's why my list of snapshots in the screenshot above has one from 11/11 and 11/18, those are the last successful backups to the SSDs and the others starring with 'yesterday' are the past 24 hours that are also backing up to the NAS).

14 replies
Question marked as Top-ranking reply

Nov 21, 2025 7:42 AM in response to weiszfrompest

The files are created by Time Machine. TM will create and store a local snapshot hourly for the last 24 hours plus the last complete backup for each TM destination that wasn't connected in the last 24 hours. Those are in addition to the backups written to the destination disk(s). TM does this for quick access to the backups (and so you have some backups even if the destination disk is not available). You can see that if you use the TM browser because the snapshots are available immediately, then if available the backup source is added.


The way to delete local TM snapshots (if you feel you must) is in Disk Utility. Select the Data volume in the sidebar (or the volume group, the right under the container disk) then select View menu > Show APFS Snapshots.



With that, you will see the snapshots listed.



You can select one or more and click the (–) button at the bottom to delete them. If you select them all and let DU calculate, it will show the summary 'private size' at the bottom, that's the total utilization of space for snapshots (it's not the sum of the individual sizes). Is that where you are getting the '80 GB lost' value? I ask because I don't see that usage anywhere in your screenshots.


You can delete them, but TM will just recreate them so the regained space is only temporary.


As colleagues have pointed out, you may need to reconnect the NAS as a TM backup to be able to get around the "Stale NFS file handle" error. Assuming you haven't erased the backups on the Synology NAS, if you select it as a TM destination you should be prompted to Claim the Backups, and you should choose that option.


Bigger picture, personally I have no issues with TM backups to a Synology DS223j. Five Macs in the house back up to it, and I also have a set of 4 TB SSDs that I use as secondary backups and connect once a week to run a backup then swap the SSDs to an office location (that's why my list of snapshots in the screenshot above has one from 11/11 and 11/18, those are the last successful backups to the SSDs and the others starring with 'yesterday' are the past 24 hours that are also backing up to the NAS).

Nov 21, 2025 8:46 AM in response to weiszfrompest

Here is an Apple article with instructions to view & delete APFS snapshots. You must first enable the "View --> Show APFS Snapshots...." option while you have the "Data" volume selecting within Disk Utility:

View APFS snapshots in Disk Utility on Mac - Apple Support


FYI, the other day someone else was trying to delete APFS snapshot using the command line & was unsuccessful, but succeeded when using Disk Utility.


As for using TM with a NAS, you must be using SMB and making sure only ASCII characters are used in the name of the share. AFP networking is no longer supported.


You may need to make sure your NAS is completely up to date for its OS and firmware & is properly configured. You may need to contact Synology support if you still encounter issues.


Nov 21, 2025 3:46 AM in response to weiszfrompest

This is above my pay grade


From what I have read elsewhere


When Time Machine can’t reach the network backup destination (your DS215j) or when the destination returns stale metadata, macOS creates local snapshots so it can still preserve rollback points.


" Failed to delete local snapshot '2025-11-17-031807'

POSIXError(_nsError: Error Domain=NSPOSIXErrorDomain Code=70 "Stale NFS file handle") "

means the APFS snapshot record exists, but the underlying data cannot resolve because the metadata references a file handle that Time Machine recorded when talking to the network drive.


In short: The snapshot is corrupted / orphaned.


You won’t be able to delete it with regular tmutil commands.


How to fix this is where I am sorry to say - I do not know how

Nov 21, 2025 4:46 AM in response to weiszfrompest

You are welcome


I am aware there are several Other Contributors who use NAS for Time Machine Backups


Perhaps 1 or more may chip in on your question and offer a safe solution


For me and me alone


I tend to think NAS backups are ok sort of


Not suggesting you alter your setup


But NAS backups are only reliable when they are reliable and are dependent on a reliable and fast Internet Connection


Not always the case when the backup is required and usually when an Internet Connection is not available


Even the maker of Carbon Copy Cloner tends to shy away from using this type of a setup


Not compatible with Migration Assistant, no backup versioning


Nov 23, 2025 9:00 AM in response to weiszfrompest

Hello!

As you can see in the previous screenshots, those lines are not showing up for me.

In the disk management, the Show APFS menu item is dimmed in the view.

I'm afraid this will result in a complete reinstall, which I'd like to avoid.

I changed the Time Machine connection to SMB on the NAS, as Tahoe has indicated since 26.1 that APFS is no longer supported. I've already deleted the old backup.

I know, I'm on a difficult path.

Regard.

WJ

Nov 21, 2025 2:32 AM in response to weiszfrompest

Follow the previous advise - First


Though, must ask


When was the last time you ran Time Machine


" 80GB lost " due to Time Machine Snapshots seems excessive like about 7 - 8 Days of not running TM Backup


I use a different way to backup - Carbon Copy Cloner and do a manual backup once a day


From the screen shot below


Each days backup ranges from about 1.14 GB up to 2.04 GB




Tested using a M4 Mac Mini with macOS 26.1 Tahoe

Nov 23, 2025 9:57 AM in response to weiszfrompest

The deletion was successful. The trash has been freed up.

Now all that needs to be fixed is the Time Machine backup.

I created a new connection on the Synology NAS.

Unfortunately, the error still persists.

Unfortunately, the image is in Hungarian.

I retrieved the log with the

log show --predicate 'process == "backupd"' --last 10m

command.

Can you help me with this?

Thanks in advance.

WJ



2025-11-23 18:52:24.690485+0100 0x76b5   Default   0x0         499  0  backupd: (libxpc.dylib) [com.apple.xpc:connection] [0xc60c5cc00] activating connection: mach=false listener=false peer=true name=com.apple.backupd.sandbox.xpc.peer[936].0xc60c5cc00

2025-11-23 18:52:24.691469+0100 0x76b5   Default   0x0         499  0  backupd: (libxpc.dylib) [com.apple.xpc:connection] [0xc60c5cc00] invalidated because the client process (pid 936) either cancelled the connection or exited

2025-11-23 18:52:24.691527+0100 0x76b5   Error    0x0         499  0  backupd: (TimeMachine) [com.apple.TimeMachine:General] com.apple.backupd.sandbox.xpc: connection invalid

Why are these files created since installing Tahoe 26.1?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.