Anders =?iso-8859-1?Q?Th=F8gersen?= <anderslt@...> posted
20060511230451.GC8675@..., excerpted below, on Fri, 12 May
2006 01:04:51 +0200:
> I have been consistently getting a segfault when doing emerge sync.
> This has happened 3 times all while at 51%:
> Total bytes read: 3377649
> wrote 381 bytes read 3377649 bytes 14783.50 bytes/sec
> total size is 133702955 speedup is 39.58
> >>> Updating Portage cache: 51%Segmentation fault
> Emerge version:
> # emerge --version
> Portage 2.0.54 (default-linux/amd64/2005.1, gcc-3.4.5, glibc-2.3.5-r2, 2.6.14-gentoo-r2 x86_64)
> I am unsure of how to tackle this. Could it be a hardware problem?
That's almost certainly a portage cache corruption issue, not a hardware
problem, since it always happens at the same place when updating the cache.
Try emerge --metadata. (I think that command works with old/stable
portage, I'm running the ~amd64 portage-2.1-preX versions here, and have
been since they went ~amd64.) That should just update the cache without
doing the sync part first.
If it's really the cache, that too will probably fail. If it doesn't
fail, try another emerge --sync, as it should then be fixed. If it did
fail as it likely will, you'll need to delete the cache and then run
emerge --metadata again, to rebuild it.
The cache is /var/cache/edb. Don't directly delete it. Instead,
move/rename it to /var/cache/edb.bak or some such, thereby keeping a
backup, just in case. Run emerge --metadata, then emerge --sync, and see if
the problem is fixed. If it is, you can safely delete edb.bak. If not,
delete the new edb and move the backup version back into place. At that
point, you'll probably need a bit more advance help to figure out exactly
which file is corrupted. However, it's quite likely that removing edb and
letting portage rebuild it will fix the problem.
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
firstname.lastname@example.org mailing list