Hi Jonathan, > This machine is not clustered, so it isn't that. There has been no manual > intervention either. > > What sort of configuration issue would cause this?
Again, workspace/working file repository roots not being located on the same mount or the mount not supporting hard links. In a one box install, there is nothing that you can get wrong that I am aware of other than the above in terms of configuration. > Basically workspace/collection has 11G in it and files/collection has 42m in > it. They are not duplicates of each other. Pretty much all of the extra > space in workspace/collection is in ingest-temp. Ok, that may have something to do with failed ingests, where the ingest is not cleand up if the connection breaks. Do the files have a checksum file next to it (may be hidden)? Once the file has been written to the workspace, the checksum is created as well as the hard link to the working file repository. If ingests fails to write the file, it should definitely be removed from the workspace. > I'll ask our developers here to take a look at the workflows. A casual > glance though does show that the cleanup operation is in there. > > The cleanup operation in both our repository and the MH main one is > instructing it to: > > <configuration key="preserve-flavors">*/source,dublincore/*</configuration> > > That might explain all the stuff in the mediapackage directory. It does. Tobias _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
