Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

C1 uses up ALL my disk space by writing a giant log file

Comments

4 comments

  • SFA
    I would suggest that you create a Support Case with the C1 Team and get their advice.

    Meanwhile if you are running a Catalogue it might be worth running a Verify process on it to see if anything is reported.

    I would suggest taking a look at the log file to see what it is reporting but realistically that would not be very practical at the size you mention so the question would then be how do you get a smaller version of the log file that still covers the events being reported.

    Is there anything appearing in the Windows Events or other Windows diagnostic tools that tell you anything?


    Grant
    0
  • Robert Whetton
    [quote="AveryTingWong" wrote:
    all this writing can't be good for my SSD.

    So where's your pagefile?
    0
  • Samoreen
    [quote="Bobtographer" wrote:
    [quote="AveryTingWong" wrote:
    all this writing can't be good for my SSD.

    So where's your pagefile?


    The pagination file can be easily moved to another partition or preferably to another hard disk.
    0
  • NNN636169364019449853
    I'm glad the OP posted this. I'm in no danger of filling up my drive, but I am concerned about the size of my ever increasing backup files. I have a 120GB SSD for my Win10 OS and all applications. All data is on a second multi-terrabyte HD.

    I followed the chain: Main->Users->(Me)->Appdata->Local->CaptureOne and found the following file sizes:

    Batch120 5.94 Gb
    Batch70 4Gb
    LLC 10 Gb
    Styles 10 Gb

    That is about 30 Gb of storage use that I was not aware of. However, Win10 says that the parent CaptureOne directory is only 10 Gb in total size, so there must be quite some overlap in these files.

    I am tempted to just delete these files, but it would be prudent to ask first what dangers there may be.

    Regards, AB7YD
    0

Post is closed for comments.