database or disk full

[mdadvice]

When I want to compress my database, i get an error code "database or disk full"
catalog is 31,8 GB, disk empty space is 35.7 GB.
Someone can help me with this ?

[G8DHE]

I seem to recall that you need something like twice the amount of the existing database size spare to compact, looks like you will need to make some room on the disk! Yes see here viewtopic.php?p=123794#p123794

[vkfoto]

My thumbs db is just over 49,000,000 kb and the cat db is just over 9,000,000 kb. Both are on a 2 TB drive with 1.3 TB free space and yet I get a database or disk is full information popup when I run the compact both command. Since it is an info window, did the compact complete anyway and what should I do to prevent this message?

[Hert]

Can you post a screenshot of that message?

[vkfoto]

Just tried another compact and got the same message. First
[ external image ]
Then I see
[ external image ]
and
[ external image ]
When it ends I get this
[ external image ]
The disk has lots of space
[ external image ]
and the files are this size
[ external image ]

[fbungarz]

This typically happens because the way PSu compacts the database is by creating a copy of the database file as a safety backup. Only if that is successful, will the original database be compacted and the temporary backup copies subsequently be deleted.

Now, particularly the thumbnail databases can become fairly enormous in size. On my system idimager.thumbs.db occupies 30 GB. Not quite as large as yours, but still large enough to return that same error. The SSD on my system which that database resides has less than 30GB space left. Obviously a temporary file of 30GB doesn't fit onto residual space on the same harddrive that is smaller than the file to be created...

In my case compacting no longer works. I have to move the thumbnail database to a different harddisk, compact it there (using SQLite Expert) and copy it back to the harddrive, where it resides. I wish one could select another harddrive from the compact dialog in PSu. That would make things a lot easier.
Yes, harddisk space is cheap, but SSDs are expensive. And PSu is quite the resource hog. In my experience moving it to my SSD really helps speeding things up. But the SSD is simply too small for regular compacting (and all the writes, I am not even sure they do it any good anyways). ...

Well, back to your situation:

Adding up your idimager.thumbs.db+ idimager.db files you end up with 60GB free space required for the temporary files. Now on your system there remains 1.81TB. I would thought that would be quite sufficient. More than twice the space you need to compact both catalog and thumbnail database. Not sure what is going on...

[vkfoto]

More like almost 10 times the space. 10 * 60 GB is only 600 GB which is still less than half the 1.36 TB free space left. Even with some other files, I'm no where near reaching the disk limit unless there is another limiting factor. With slightly more than 300k images in the database, could that have an influence? Is the database full and not the disk?

[gcorbin]

I might be wrong, but I thought that the temporary copy of the database is created in the windows temporary directory, generally C drive, not in the database directory. If my memory is correct, you need to move the windows temporary directory to a drive with more space. Hert should be able to confirm whether I am going mad.

[Hert]

I might be wrong, but I thought that the temporary copy of the database is created in the windows temporary directory, generally C drive, not in the database directory. If my memory is correct, you need to move the windows temporary directory to a drive with more space. Hert should be able to confirm whether I am going mad.

That is correct, SQLite by default uses the Windows Temp folder for this. In PSU you can change that with a registry tweak. Check this page and search for "SQLiteTempDir"
https://michaelweidner.com/psu/

[vkfoto]

Just to be clear, where it says

SQLite scratch folder: This setting will move the SQLite scratch folder to somewhere else
WriteToRegistry('', 'SQLiteTempDir', 'c:\your folder here\');

Once I enter my folder choice, is this done inside PSU or in the Windows registry?

[Hert]

Run it with Tools-> Scripter from the upper left hamburger menu.

[vkfoto]

Found it. Ran the script, saved, exited and restarted PSU. Now doing the compacting and I see the temp file building in the new location.
Thanks for all the help.

[fbungarz]

Ahhh, this is great. Didn't know it.
And yes, I have my database on the system drive, same drive as the Windows Temp folder, that's why I assumed it was always the same drive.

[fbungarz]

However, before I apply the tweak:
By moving the scratch folder off the SSD to a normal harddrive - will that not result in slower performance? The reason I have the database on the SSD was to speed things up...

[Hert]

Frank, your database will keep performing good because regular operations all take place on the SSD. But compacting will be slower because the temp file is written in the scratch folder first.