Skip to main content
K
Kurt323639330udd
Participant
September 18, 2023
Question

Corrupt Large PSB files

  • September 18, 2023
  • 2 replies
  • 449 views

We regularly save very large PSB files. We recently found two extremely large files (larger than our usual) both around 1.2 gigapixels that were corrupted. Both were saved last year one in early June of 2022 in Photohsop 2021 (v22.5) with a file size of 18GiB (27835x43470px, 16bit/chan RGB) and in late June of 2022 saved in Photoshop 2022 (v23.3) with a file size of 26GiB (37971x33933px, 16bit/chan RGB). We confirmed that the checksums are unchanged from when they were stored in our DAM, so it does not seem to be file degridation but likely an issue with saving. Further more at least one of the files is openable but the corruption is isolated to a single layer in the image. Files were saved on a Mac Pro (last intel version) workstation with 192GB of RAM and plenty of (more than 1TB free) SSD storage spce.

 

We would be able to provide files to Adobe if you want to investigate.

This topic has been closed for replies.

2 replies

K
Kurt323639330uddAuthor
Participant
September 18, 2023

Files were saved locally, checksums were made when uploaded to DAM. In the files one layer (in one case the background, in another a separate image layer) seem to be partially modified... looks as if the green channel was inverted for the bottom 40% of the image in one... the other has a weird purple haze over part of another layer. The checksums show the files were not changed since they were saved.

 

We have since insituted a policy of re-opening large files to make sure there were no issues with the saving process before uploading to our network storage, but was curious if there were any issues with specific previous versions that we should be aware of.

    D Fosse
    Community Expert
    D FosseCommunity Expert
    Community Expert
    September 18, 2023

    File corruption is always caused by failing hardware, and a subset of that is saving directly over a network. Never do that. It is not supported and at your own risk. Save locally, then copy over.

     

    At work I've seen a lot of corrupted files on our company server.  I maintain my own set of local disks for my archive. From that I copy over to the server. Even then, corrupted files occasionally have to be replaced from my original local copies.

     

    The bigger the file is, the higher the risk of network corruption. It's just statistics. If a "corruption event" happens every x GB on average, the chances increase it will happen to that file the bigger it is. You can save 1000 or 10 000 small word or excel files before corruption happens, for each Photoshop file.

     

    https://helpx.adobe.com/photoshop/kb/networks-removable-media-photoshop.html 

     

    "There are many different types of network configurations (for example, client-server or peer-peer) or types (for example, ethernet or IP) that many different companies make. Each configuration requires specialized software and hardware, with varying setups, preferences, and updates. This additional layer of software and hardware increases the chances of an error occurring (for example, from line noise, RF interference, or packet collisions).

     

    Multiple factors affect data transmission over a network, including file servers, routers, bridges, network cards, software, cables, connectors, power cables, and power supplies. Network connections can suddenly become unavailable, increasing the risk of data loss and application errors. During transmission and reception, network software verifies that data has been sent and received. The depth of verification depends on the network software package and sometimes isn't accessible by the operating system. When you try to save files across a network, you could receive the error. For example: "Could not complete the request because the file is locked," or "Could not save because of a disk error." However, the network and operating system could not notify you if a Photoshop image file contains damaged or incomplete information."

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices