On 16/01/2021 01:01, Bruce Williams wrote:
Hi all!
I THOUGHT I'd found a limit to the number of Collections that could be saved.
But it looks more and more like wherever my Collections are stored, darktable can
no longer write/execute on that location, as not only can I not store any NEW
Collection, I can't delete an existing one either.
I'm on Linux MInt 20 and dt 3.4.0+88~g0e4ecc1fa-dirty.
I have library, keyboardrc and .db files located in .cache in my user
filesystem area.
Yes, that's where the database and the 'more intimate' Darktable files are,
~/.config/darktable
But what do you mean by "Collections"? Do you mean the image files?
Those are kept on disk where ever you've chosen to keep them.
I keep all of mine under ~/MyPhotographs/
The unclassified I organise by date (year, month) with each year on a separate XFS
filesystem, the file systems being managed by LVM.
Why XFS? Why LVM? So I can grow it later if needed.
The "Classified" are according to the reason for classification - event, location,
project...
The point is that there is always file space to grow into, space were the images
can be saved.
Trust me: disks are cheap.
SSD is getting cheaper, but I'd use it for things like need more rapid access like
the root file system. As long as my chassis and motherboard can handle it I can
keep adding 'bulk storage'. If all fails I can add a NFS server for the purely
'data' storage, and the image files+sidebars fall into that category.
So: what do you mean by 'Collections'?
/a
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
