Hi Pascal Yes, we are using CQFS. We will upgrade immediately and see if it helps. Thank you for your help Niels
Pascal Mangold wrote: > hello nils > > we discovered this too. Are you using CQFS? If yes we were told that > this could be the problem. If you have time change to 2.1 RC1 with > jackrabbit filesystem then these problems should not occur again. > > PS: magnolia organization will provide the magnolia power-pack for > professional use see: > > http://www.magnolia.info/en/magnolia/products/magnolia-power-pack.html > > > Regards, > > Pascal Mangold > CEO obinary ltd. > > ---------------------------------------------------------------------- > [EMAIL PROTECTED] http://obinary.com > magnolia content management designed for jsr-170 http://magnolia.info > ---------------------------------------------------------------------- > > > > On 24.06.2005, at 13:58, Niels Sthen Hansen wrote: > >> Hi >> >> We have been running a Magnolia instance for a few weeks (2.1 nightly, >> revision 881). Our backup procedure has been to shut down the author >> instance and making a tar.gz of the repository directory (is this the >> recommended method of backing up Magnolia content?) >> >> This morning we got the following error after starting up the server: >> >> ERROR info.magnolia.cms.beans.config.ContentRepository >> ContentRepository.java(loadRepositories:257) 24.06.2005 05:08:21 >> System >> : Failed to load JCR "website" term out of order: term out of order >> info.magnolia.repository.RepositoryNotInitializedException: term out of >> order: term out of order: term out of order: term out of order: term >> out >> of order >> >> When inspecting the file >> repositories/website/workspaces/default/index.dat we found that the >> size >> of the file was 201GB! (which is impressive considering that the total >> disk size is 116GB). >> >> Stat of index.dat: >> File: `index.dat' >> Size: 215169786752 Blocks: 3576 IO Block: 4096 regular >> file >> Device: fd00h/64768d Inode: 9670563 Links: 1 >> Access: (0664/-rw-rw-r--) Uid: ( 1034/magnolia) Gid: ( 5001/ >> magnolia) >> Access: 2005-06-24 11:19:33.000000000 +0200 >> Modify: 2005-06-24 10:24:37.000000000 +0200 >> Change: 2005-06-24 11:23:53.027945069 +0200 >> >> We were able to solve the problem by removing index.dat and restarting >> the server. This created a new index.dat and everything seems to be >> working fine. >> >> However, we are somewhat concerned about this behaviour and would like >> to know if others have had this problem and how we can prevent this >> from >> occuring again? >> >> Best regards >> >> Niels >> >> >> >> >> >> ---------------------------------------------------------------- >> for list details see >> http://www.magnolia.info/en/community/developer/mailinglists.html >> ---------------------------------------------------------------- >> > > > ---------------------------------------------------------------- > for list details see > http://www.magnolia.info/en/community/developer/mailinglists.html > ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/community/developer/mailinglists.html ----------------------------------------------------------------
