However, if you traverse the directory tree by choosing the Time Machine folder (leading to a slow search),Įvery - even identical - version of every backup will be searched, and the same file will be found multiple times as it resides under This means that you find every different file only once. When you search the entire disk (which uses the fast 'CatSearch' mode), then every real file will onlyīe found once, even if it's hardlinked multiple times. If TM performs several backups a day, most files and folder contents do not change, and therefore TM does simply link to the same files andįolders from within different backup times. Time Machine (TM) backups use so-called 'folder hardlinks' to alias unchanged data between multiple backups: To keep found items around in the results even if they're getting deleted after being found, check the option Deleted Items Remain Visible in the Results menu. Keep in mind that the Find window tells you how many it found during its search process, whereas the Results window keeps updating when any of the found items get moved, renamed or deleted. Lastly, if the Find window shows that it found N items but the items shown in the Results window are fewer, it's likely that some of the found items have been deleted in the mean time. If the search then finds more files, these extra files should be the other hard links to the files the fast search had found. by holding down the Option (alt) key when clicking on the 'Name' popup menu, then choose 'Slow mode', setting it to 'Yes'. To verify this, force a 'slow' search, e.g. In this case, only one instance of the several hard links will be found. With checking its 'Slow' box, in order to prevent FAF from using the disfunctional CatSearch function on that volume.Īnother, quite rare, reason why some files may not be found by FAF is that you are finding hard linked files when searching an entire disk (volume).Īn example would be some SDK files inside Apple's Xcode.app In this case, either re-mount the volume in SMB format, or add the volume to the 'Special Folders' (find it in FAF's menu or type cmd-shift-,), If it's AFP (identified by the prefix 'afp://' under Server or by 'AppleShare' under Format), then you are dealing with a known bug with Linux / NAS drivers related toĬatSearch. Next, if the volume you search is a network server (NAS) volume, check if it's mounted as AFP instead of SMB (ctrl-click on the volume's icon in Finder and choose 'Information' See Rogue Amoeba's article on this topic.įAF does not display all the files it should have found.įirst, make sure that the options for Invisibles, Package Contents and Trashed in the Results window are all set to Show and not to Hide or to Only.

There also used to be a issue caused by an update of Airfoil from Rogue Amoeba in August 2011.

For more detailed instructions on how to go about sorting out the offending software causing the crash, you may follow this guide of mine: How To Identify and Disable software extensions on OS X that cause other Apps to crash Unfortunately, it's out of my control to fix FAF in this Remove their contents temporarily, then reboot, to see if FAF works then. To keep using FAF, check the folders named InputManagers and Input Methods in your startup disk's Library folder and While these are not generally harmful, they are, regrettably, causing problemsįor Find Any File.

Installed, such as SIMBL or Spell Catcher. If you get a crash saying Find Any File was quit unexpectedly, you may have a conflicting Input Manager or Input Method.Please update to at least 10.6.4, that should fix it.

That contains the text UITools.NewPictureFromPicWithMask, then you may be running an outdated Mac OS X Snow Leopard version. If you get a window shown by FAF that mentions Internal Error (exception) and creates a text file on your desktop.If that happens, please check your Login Items (in System Preferences, Users & Groups) for any missing items (they'll have a generic icon), and remove them. Some users experience a slow start of FAF.Check the beta page and see if that version resolves the issue. The crash may already be fixed in the latest beta (prerelease) version.

Findanyfile