Summary: Problem with Solstice Backup index file and perhaps max file size

From: Detlev Habicht (habicht@ims.uni-hannover.de)
Date: Thu Jun 04 1998 - 10:15:35 CDT


Hi all!

Some days ago, i have a problem with Solstice Backup 4.2.2 SingleServer
on a Solaris 2.5.1 server.

I got a bootstrap message like this:

* obelix:/ save: File index error, client file index is too large
* obelix:/ save: Cannot open save session with obelix
* obelix:/usr save: File index error, client file index is too large
* obelix:/usr save: Cannot open save session with obelix
* obelix:/var save: File index error, client file index is too large
* obelix:/var save: Cannot open save session with obelix
* obelix:/opt save: File index error, client file index is too large
* obelix:/opt save: Cannot open save session with obelix

and so on ...

Well, the index file of the database was to big:

# pwd
/export/nsr/index/obelix
# ls -l
total 4114692
-rw-r--r-- 1 root other 1901 Apr 6 08:52 README
-rw------- 1 root root 2106548224 May 14 10:16 db
# nsrls

obelix: 8332053 files requiring 1692048 KB
/export/nsr/index/obelix/db is currently 83% utilized
#

Solstice Backup 4.2.2 and Solaris 2.5.1 has a file size limit of 2GB.
I try to check the database und reclaim space, but it doesn't work.
I think, the file was to big, to do something.
I get some answers, but no solution to fix this problem.

So i try something - perhaps not very cool, but it helps me:

I cut the db-file to a size of 1,4 GB and started rebuilding the database.
This works without errors. The new db-file was then 1,9 GB (i don't know
why it grow). Then i reclaim space again. And now the system was working again.

Thanx for all hints - and don't laugh about my solution .... :-}

Detlev

-- 
 Detlev  | Institut fuer Mikroelektronische Systeme, Uni Hannover
 Habicht | D-30167 Hannover +49 511 7624992 habicht@ims.uni-hannover.de
 --------+-------- Handy    +49 172 5415752 ---------------------------



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:41 CDT