Thanks for the recommendation, Brian - but I'm not sure that is the case.

Filesystem            Size  Used Avail Use% Mounted on
/dev/hda1             9.8G  6.3G  3.0G  68% /
/dev/hda2              65G   46G   15G  75% /home
none                  124M     0  124M   0% /dev/shm

I can also cp /var/lib/slocate/slocate.db
/var/lib/slocate/slocate.db2/3/4/5/6 etc... Until I'm blue in the face.

One thing I was wondering, I was speaking to a friend about this and he
suggested removing my slocate database my deleting  slocate.db - but in his
case it was in a different location. I was wondering if perhaps the last
action being taken is slocate is trying to move a file from the wrong
location to the wrong location - although the fact that it creates the .tmp
file in the correct place doubts this assumption; it's the only thing I can
think of right now!

-----Original Message-----
From: Brian Ashe [mailto:[EMAIL PROTECTED] 
Sent: 18 June 2003 17:09
To: [EMAIL PROTECTED]
Subject: Re: updatedb problem: last try!!


Michael,

On Wednesday June 18, 2003 11:25, [EMAIL PROTECTED] wrote:
> hi all,
>
> after doing a number of rpm updates to my system, updatedb appears to 
> have broken. i have posted this problem now twice to this list without 
> any response whatsoever, but lets see if my latest discovery helps 
> spur some answers on!
>
> i have finally discovered what is breaking it, but don't know what to 
> do about it. i went into /var/lib/slocate and deleted everything there 
> - so basically a clean slate.
> i ran updatedb
> it thought for a long time
> then got the broken pipe
> and ls /var/lib/slocate showed that it had successfully created
> /var/lib/slocate.db.tmp
> i did a mv slocate.db.tmp slocate.db
> and i could locate things perfectly.
>
> so it appears that the broken pipe occurs when slocate is trying to 
> move slocate.db.tmp -> slocate.db. and this even happens when 
> /var/lib/slocate.db doesn't exist.
>
> so, for the final time - any suggestions?

Most likely you are out of drive space (somewhere).

Do a "df -h" and see if there is a plenty of space left in all of your 
partitions.

The partition where /tmp is must have more space than the size of your DB 
because that's where it does it's sort operation.

The partition where /var is should have twice the free space of the DB.

These are not necessarily _exact_ figures, so make sure you have some float
in 
there as well.

If you used an "update tool" (such as up2date, apt-get or red carpet) it 
likely stored a bunch of extra stuff in /var somewhere and is the cause of 
the post update failure.

-- 
Brian Ashe                                                     CTO
Dee-Web Software Services, LLC.                  [EMAIL PROTECTED]
http://www.dee-web.com/


-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list


-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list

Reply via email to