You could enable debug log on the org.apache.jackrabbit.oak.plugins.segment to see what it was attempting to do with your files
May be something in your log would suggest you whether it is safe to delete these (AEM might have tried to delete them, you would simply help to delete these manually)
But it does not feel right to delete files manually, better check permissions or anything else that can prevent file.delete() from execution.
Suspect, you are hitting this code:
// remove all obsolete tar generations Iterator<File> iterator = pendingRemove.iterator(); while (iterator.hasNext()) { File file = iterator.next(); log.debug("TarMK GC: Attempting to remove old file {}", file); if (!file.exists() || file.delete()) { log.debug("TarMK GC: Removed old file {}", file); iterator.remove(); } else { log.warn("TarMK GC: Failed to remove old file {}. Will retry later.", file); } }In which case it would be fairly safe to delete files.
As they are within the list of:
/** * List of old tar file generations that are waiting to be removed. */ private final LinkedList<File> toBeRemoved = newLinkedList();
P.S. really good talk from this years adaptto[1] [2] might help too
[1] https://adapt.to/content/dam/adaptto/production/presentations/2016/adaptTo2016-Into-the-tar-pit-a-Ta...
[2] https://adapt.to/content/dam/adaptto/production/presentations/2016/adaptTo2016-Into-the-tar-pit-a-Ta...
Regards,
Peter
