![]() folder inode numbers change when the volume is remounted. We have seen other related aberrant behavior on these volumes, e.g. sometimes the condition is absent when running the task again at a later time, and sometimes it recurs immediately after remounting the source volume. In the handful of cases we're tracking, the issue appears to be both transient and recurrent, e.g. ![]() CCC (6.1.4+) identifies this result, reports it as an error, and suspends any deletion/archival activity on the destination when this condition is encountered to avoid errantly removing content from the destination that was copied in a previous backup task. ![]() infinite loop) condition and refuse to enumerate the content of the corrupted subfolder. fts) identify this (correctly) as an insane "directory cycle" (i.e. Some filesystem enumeration facilities (e.g. We have seen a handful of cases where a folder's inode number is identical to the inode number of its parent folder. We're tracking a new ExFAT-specific filesystem bug in macOS Ventura. Erasing the volume is the only remaining recourse. macOS has documented functionality to remove that role, but that functionality does not work (FB7208067, Sept 2019). The underlying cause of this problem is the presence of an irrevocable "Data" role applied to that volume by Apple's ASR replication utility. Solution: Erase the volume in Disk Utility and start the backup from scratch. Hold down Command+Option while dragging the revealed volume to your Desktop to create an alias.Choose as Columns from the Finder's View menu.Right-click on your backup volume in CCC's sidebar and choose Reveal in Finder.Workaround: You can create an alias of the volume on your Desktop: Some backup volumes may still not appear in the Finder sidebar, but they should appear on the Desktop and in the window that appears when you choose Computer from the Finder's Go menu. Update March 2023: Apple mostly addressed this issue in the 13.3 update. We reported this issue to Apple (FB9739492) in November 2021. In Ventura, this volume no longer appears in any of these locations, regardless of your Finder preferences to show external volumes in the sidebar, and regardless of any attempts to drag the volume explicitly into the sidebar. Prior to Ventura, the remaining Data volume would appear just fine on the Finder Desktop, and also in the volume list when you select "Computer" from the Finder's Go menu, but not in the sidebar. If you created a bootable copy of Catalina, Big Sur, or Monterey in the past, and then proceed with CCC backups to that volume on Ventura without specifically using the Legacy Bootable Copy Assistant, CCC will remove the incompatible System volume from the destination. ![]() Some backup volumes don't appear in the Finder (sidebar, nor Desktop, nor Computer) We cite known problems that Apple introduced in the new OS below. CCC 6.1.3 (and later), published in September 2022, is fully compatible with macOS Ventura. Apple published macOS Ventura in November 2022. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |