> (Also, the asset store contains the extracted text copies of files you > uploaded, but I wouldn't expect them to take up 3x the size of your > new files).
A single document in the assetstore, the `DSpace Architectural Futures: A White Paper' looks as follows #0, interestingly....the extracted text copy occupies less than ten percent of the original. Thanks. -- Van Ly -- #0 -- [r...@dabih dspace-data]# tree assetstore assetstore |-- 11 | `-- 58 | `-- 15 | `-- 115815019145092108673282291954599930771 `-- 86 `-- 99 `-- 05 `-- 86990559682600625622922454764247047595 [r...@dabih dspace-data]# find assetstore |xargs file assetstore: directory assetstore/11: directory assetstore/11/58: directory assetstore/11/58/15: directory assetstore/11/58/15/115815019145092108673282291954599930771: PDF document, vers\ ion 1.3 assetstore/86: directory assetstore/86/99: directory assetstore/86/99/05: directory assetstore/86/99/05/86990559682600625622922454764247047595: ASCII text [r...@dabih dspace-data]# find assetstore -type f |xargs ls -h --size 116K assetstore/11/58/15/115815019145092108673282291954599930771 \ 8.0K assetstore/86/99/05/86990559682600625622922454764247047595 -----Original Message----- From: Stuart Lewis [mailto:s.le...@auckland.ac.nz] Sent: Tue 26/05/2009 6:36 PM To: Van Ly Subject: RE: [Dspace-tech] archive_directory & assetstore growth Hi Van Ly, Have you tried running [dspace]/bin/cleanup to get rid of old stale bitstreams? (Also, the asset store contains the extracted text copies of files you uploaded, but I wouldn't expect them to take up 3x the size of your new files). Cheers, Stuart ________________________________ From: Van Ly [mailto:v...@library.usyd.edu.au] Sent: Tue 26/05/2009 19:55 To: DSpace-tech@lists.sourceforge.net Subject: [Dspace-tech] archive_directory & assetstore growth Hi, At the moment, I've an archive_directory of 51Gb occupying 89Gb of assetstore in DSpace. The archive_directory is like the one shown in dspace-1.4.2-source/docs/application.html#itemimporter and is a copy of all packages successfully imported in 1.4.2 DSpace with 8.1 Postgresql. When the archive_directory grew from 50-51Gb, that 1Gb difference grew the DSpace assetstore by 4Gb, is that supposed to happen? or are failed import attempts (and retries) responsible for leaving clutter in the assetstore? or are package replacement operations (and many repeats) responsible for leaving earlier duplicate copies of bitstreams behind? I was expecting a successful 1Gb feed to DSpace would grow the assetstore by about 1Gb plus & minus a little bit. Any `clue' is much appreciated. -- Van Ly
------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech