Handled the .tmp.driveupload issue identified during the SAIL folder sweep. I inspected /Users/samaguiar/Documents/.tmp.driveupload, confirmed it was actively changing, and verified both Google Drive and a macOS Virtualization VM process had open handles in the folder.
I did not delete the whole folder. Instead, I removed only stale, closed temp entries: files older than seven days that were not currently open according to lsof at the time of each pass.
Cleanup removed four manifests: 16,681 entries, 6,526 entries, 3,048 entries, and 4,503 entries, for 30,758 manifest entries total. Each manifest reported zero remaining paths afterward.
Local cleanup report: /Users/samaguiar/Documents/Projects/admin/session_logs/tmp-driveupload-cleanup-2026-05-20/summary.md.
The folder is still active. Final checks still showed Google Drive and com.apple.Virtualization.VirtualMachine touching .tmp.driveupload. Folder size was about 14G after cleanup, and the file count continued moving during verification. The largest remaining entries include hard-linked temp files, including one about 8.2G.
The current Data volume free space ended around 154Gi available. The earlier 60G number from the SAIL sweep was not stable by the time this cleanup ran; the folder measured about 19G at the start of this dedicated cleanup, then about 14G after safe passes.
The safe stale closed-file cleanup is complete. I stopped because the remaining bulk appears tied to active Google Drive or VM processing. Continuing to chase files while the folder is live would increase risk without much immediate benefit.
A future agent can rerun the same inspection after Google Drive is idle. If the folder remains large then, map the largest remaining hard-linked entries to their other paths before deleting anything. Do not delete the whole .tmp.driveupload folder while Google Drive or the VM has open handles.
Use the manifest folder as the source of truth: /Users/samaguiar/Documents/Projects/admin/session_logs/tmp-driveupload-cleanup-2026-05-20. The deletion manifests are deleted-manifest.txt, deleted-manifest-pass2.txt, deleted-manifest-pass3.txt, and deleted-manifest-pass4.txt. Open-handle snapshots are also saved there.
Importance: High. Status: pending follow-up because cleanup reduced stale residue but did not touch active sync files.