On May 13, 2011, at 10:19 AM, Ernst Bunders wrote:
> > hello > > We were recently hit by the unfortunate of a full file system. This > caused a lot of webapps to crash and all kind of corrupt files like > for instance the Magnolia index files. > Two causes were identified: > - xml dumps imported in the repository through admin central (upload) > were not removed after use. These were big files, gigs of data. http://jira.magnolia-cms.com/browse/MAGNOLIA-3688 > - the activation exchange files are not deleted after the operation is > completed (both on author and public instances) Those should be deleted always, except for when debug log is enabled on activation in which case files are stored to allow analysis of activation issues. I failed to reproduce this on 4.4.3 HTH, Jan > > This was a bit unexpected for me. Of course we can (and will) do > something about this ourself, perhaps with a cron job that chucks out > all of yesterdays files. But I wonder why Magnolia does not take care > of this. Is there a reason? is there some hidden functionality that > can do it? Is there anything to say about this topic? > > regards, > > -- > Ernst Bunders > Ontwikkelaar VPRO > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
