Simon, In order for a dataset file to be removed from disk, no active library associations (LibraryDatasetDatasetAssociations) or history associations (HistoryDatasetAssociations) can be pointing to it. When no active association objects are pointing to a dataset file, it will ultimate be removed from disk via option -3 (the purge_datasets option) in the cleanup_datasets.py script. However, another factor in removing the file from disk is that the configured number of days must have passed since everything pointing to the file was marked as deleted. The default number of days in the script is 60. To remove files from disk on the same day they were marked as deleted, override the default by setting the -d flag to 0. Greg Von Kuster On Apr 30, 2011, at 4:59 PM, Simon Lank wrote:

Hi.

Our current galaxy database is ~ 600 gb, most of which are user deleted datasets.

I followed the instructions here: https://bitbucket.org/galaxy/galaxy-central/wiki/Config/PurgeHistoriesAndDat...

and ran the shell scripts in recommended order. One of them in particular (I think it was purge_histories.sh) took amost 24 hours to complete. However, it doesn't appear any / most of the files were actually deleted, since we still have ~ 600 gb of dataset files. Is there something obvious I can try to get the files purged correctly?

Thanks.

Simon

Simon Lank Research Specialist O'Connor Lab, WNPRC 555 Science Dr. Madison WI (608) 265-3389

___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list:

http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists, please use the interface at:

http://lists.bx.psu.edu/

Greg Von Kuster Galaxy Development Team greg@bx.psu.edu