Skip to main content
Participating Frequently
December 10, 2018
質問

Upgraded from 1TB to 4TB scratch disk: "Scratch disks are full" when 2TB left and then "Couldnt save file / preferences because of a program error" + crashes

  • December 10, 2018
  • 返信数 2.
  • 874 ビュー

hi, recently replaced two 1TB scratch disks for a single 4TB hdd and problems started.

When the scratch files fill this 4TB disk up to around 2TB left, i start getting scratch disks full error, and zero sized scratch files start appearing on it everytime i try save and get the error.

Sometimes purging caches then lets me save (the zero files dont get removed tho) but i think from there on something is wrong and sooner or later i also start getting error: Couldnt save file due to program error, which keeps producing new zero sized .tmp files at the document path everytime i try to save and get this error. Also even if i add additional scratch disks after the 4TB one, they wont get utilized and there is still 2TB free on the first one. there is plenty of space on the disk where the .psb documents are located.

Note that also at this stage if i try open preferences, it will crash photoshop without any error message.  or if i close the documents normally and close photoshop at this stage, i will most likely get error: Couldnt save preferences due to program error just before it closes.

im using old win8.1 64 (hasnt been patched for years). When formatting the new drive, i got prompted to use GPT instead of MBR to fully use the 4TB, so i did. also disabled indexing.

the work consists of like 10 .psb files of 1-6gb each open at same time (up to 200k x 200k pixels each), alot of switching between them, moving and merging pixels and layers between them, saving several of them in background while further working on others so there is alot of constant complex scratch file traffic going i assume.

Autosave+compatibility+previews is disabled, no other apps are accessing the scratch disks, always enough space on OS + PS app/preffs disk as well as 100GB+ free on the PS documents disk. 64GB ram, set up so theres always at least 15gb free, even during the problem. so it shouldnt be a memory problem.

im kind of suspecting the OS not letting PS properly use the 4TB disk or something although i have no problem copying random files to fill all 4TB manually.

why the "cant save preferences error" though, as that doesnt need to access the scratch disk.

But moving everything to win10 would take a few days so im looking for some opinions that could help me decide whether i really need to that or if it could still be caused something else based on the observations.

PS version 19.1.0

win 8.1 64bit (not updated for years)

i will post more details about hw and ps settings etc if needed.

thanks for any input

    このトピックへの返信は締め切られました。

    返信数 2

    Premultiplied作成者
    Participating Frequently
    December 14, 2018

    latest summary of the problem:

    so i finally tested it on win10 pro 64bit with the latest ps2019 20.0.1 64bit (both trial and full), clean installs, wiped preference files, and the problem persists. now i know that its whenever scratch size goes over around 2.4TB (i have around 20 .psb docs open at same time, 1-6gb each), any further brush strokes or operations that require the creation of additional scratch file will throw "scratch disks are full" even if there is plenty of space and further disks free. also unable to open further docs at that stage (throws "couldnt open file because of program error"), and when closing ps at that point will produce "couldnt save preferences because of program error". purging cache doesnt help.

      the last scratch file is smaller, like when you genuinely run out of space, it tries to fit in a last small one, even if there is another 1TB left...  it sounds like some filesystem/64bit problem, something not allowing ps to use more or a ps limitation? the big disks are indeed formatted as GPT.  tried different disks with the new 4TB completely disconnected and also with it solo. all sata. also it can happen even when the current active scratch disk is still at 99% free space once i hit the 2.4TB wall, so it doesnt seem to have anything to do with the actual storage hardware.

    only thing i can't test is a different computer. could it be my older mb (Asus P9X79) ? or something in bios? or not enough ram to allow ps to work with larger scratch? (i got 64gb  (i have yet to test limiting it vs letting ps use all of it and see if it affects the scratch limit)

    starting to get puzzled, as the manual says the 64bit photoshop supports exabytes of doc size and scratch and maximum canvas size 300k x 300k (unless all that only applies when a SINGLE document is open (i have 15-20 docs open, 1-6gb each, canvas sizes are from 50k to 150k x 150k) or perhaps its an untested statement because very few users probably use that much scratch so there are no reports? i would really appreciate if someone could test this so i know the problem is just on my side or whether its an actual photoshop limitation.

    December 11, 2018

    Hi

    Why have you not updated Photoshop, a lot of issues where fixed, up until the most recent version of CC2018 19.1.7 more info

    Fixed issues in Adobe Photoshop CC

    Premultiplied作成者
    Participating Frequently
    December 12, 2018

    i've now updated to 19.1.7 and the problem persists but found out that it has nothing to do with the actual new 4TB disk but happens simply once the scratch files reach around 2.5TB in size combined, no matter on which disks they are or what order.

    after that, it says scratch disks are full no matter how much free space there is left on the disk or any further disks in the scratch drive priority menu and the subsequent problems described in the op remain the same.

    (before getting the 4TB drive i didnt have enough space to reach the 2.5TB scratch size problem point, so i couldnt encounter it earlier, and thus blamed the new disk as thats when it started happening)

    D Fosse
    Community Expert
    Community Expert
    December 12, 2018

    Premultiplied  wrote

    i've now updated to 19.1.7

    The current version is 20.0.1.

    EDIT: or is 20 not supported in Win 8?