4478 – portage will not run after crash

Bug 4478 - portage will not run after crash

Summary: portage will not run after crash

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Unclassified (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Martin Schlemmer (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-07-03 06:36 UTC by Jesse Throwe
Modified:	2011-10-30 22:17 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jesse Throwe 2002-07-03 06:36:59 UTC

If a gentoo based machine crashes during the middle of an emerge (ie. hardware
lockup), when rebooted and another emerge run, the emerge will stop functioning
after >>>> emerge <package> to /  running a top shows that sandbox is running
with 99.0% CPU, so it appears to be an issue with sandbox being terminated
unexpectedly.  I am currently running 1.3b_test, so i dont know if this is an
issue with 1.2.

Comment 1 Jesse Throwe 2002-07-03 12:17:31 UTC

more information:

It seems that portage gets hung up due to some files in /tmp that are left due
to the unclean shutdown.  Removing everything in tmp fixes the issue. 

Ive also noticed that sandbox will steadly eat up more memory until there is
none left in this non functional condition.

Comment 2 Martin Schlemmer (RETIRED) gentoo-dev

2002-09-29 08:04:51 UTC

This should be fixed by now.

Comment 3 Jesse Throwe 2002-10-02 14:50:59 UTC

I havent done any extensive testing, but it appears that its fixed with 1.4.1 rc1.

Thanks for all the hard work all.