Deleting files from a catalog *copies* files

peter Frings

• 2016年08月30日 21:40

I tried to delete many RAW files from a catalog and noticed the following:
- it is very slow,
- after 30 minutes, the mac complained that the startup disk was full.

The catalog is on my internal SSD (which limited in space), and the images are on an external hard disk. Now, when you delete an image from the catalog, C1 moves that file to the trash of the user's home folder. That means that it *copies* those files from the external disk onto the internal SSD (and then effectively deletes it from the external disk). No wonder it's slow and filled up my internal SSD!

In contrast, when you delete an image from the external disk using the Finder, the image is simply moved to the trash folder of that external disk: lightning fast and not requiring a single extra bit.

(An additional, but far less problematic side-effect is that you can't "Put back" those images from the trash.)

I just logged a support case for this, but in the mean time, beware of deleting large amounts of images at once! If your internal disk is low on disk space, delete the images in small amounts and empty the trash between each batch. (Of course, there is no problem if those images are already on the startup disk (or more correctly, the same disk as your home folder.)

Cheers,
Peter.

0

• 

  peter Frings

  • 2016年08月31日 13:23

  Got an answer from support:
  
  

  
  We are aware of this issue, however at this time I do not have a timeline for it being resolved.
  

  
  
  Hooray for the first part, bummer for the second 😊
  
  Peter.

  0
• 

  Permanently deleted user

  • 2016年08月31日 16:52

  I've logged this twice and both times got the response you did. Thank you for also logging it. Apparently C1 isn't getting enough complaints to fix this fundamental, long-standing bug.
  
  When you "trash" images, C1 COPIES the "trashed" file(s) to your User Trash folder and DELETES it from the original location. This takes time and generates extra I/O activity to the boot device (not something we really want for our nice SSDs). Your situation is exactly what I've warned them about: ever-smaller Mac boot devices will unexpectedly fill up with large numbers of files are deleted.
  
  Also, if you later decide to "untrash" files, you'll end up COPYING them back to the original location while leaving the original "trashed" file in your User trash folder. This takes more time, more disk activity, and still leaves your boot device full.
  
  Workaround: I've created a "C1 Trash" folder on my photo drive. Instead of trashing files, I manually drag them to the "C1 Trash" folder, manually trash the folder's contents, and then have C1 and trash— which of course contain no files, so all C1 does is complain that it can't find the offline files.

  0
• 

  peter Frings

  • 2016年09月03日 22:21

  It's odd, one would think that this would be easy to fix. Just call the proper system function and it's done.
  
  In the mean time, my workaround is to move the files in C1 to a trash folder as you did, and then select to remove them from the catalog. I can then use the finder to trash them. That avoids the 'offline' complaints.
  
  Peter.

  0

投稿コメントは受け付けていません。