| 1 |
Anders =?iso-8859-1?Q?Th=F8gersen?= <anderslt@×××××.com> posted |
| 2 |
20060511230451.GC8675@××××××.mydomain, excerpted below, on Fri, 12 May |
| 3 |
2006 01:04:51 +0200: |
| 4 |
|
| 5 |
> I have been consistently getting a segfault when doing emerge sync. |
| 6 |
> This has happened 3 times all while at 51%: |
| 7 |
> |
| 8 |
> [...] |
| 9 |
> |
| 10 |
> Total bytes read: 3377649 |
| 11 |
> |
| 12 |
> wrote 381 bytes read 3377649 bytes 14783.50 bytes/sec |
| 13 |
> total size is 133702955 speedup is 39.58 |
| 14 |
> |
| 15 |
> >>> Updating Portage cache: 51%Segmentation fault |
| 16 |
> |
| 17 |
> Emerge version: |
| 18 |
> |
| 19 |
> # emerge --version |
| 20 |
> 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) |
| 21 |
> |
| 22 |
> |
| 23 |
> I am unsure of how to tackle this. Could it be a hardware problem? |
| 24 |
|
| 25 |
That's almost certainly a portage cache corruption issue, not a hardware |
| 26 |
problem, since it always happens at the same place when updating the cache. |
| 27 |
|
| 28 |
Try emerge --metadata. (I think that command works with old/stable |
| 29 |
portage, I'm running the ~amd64 portage-2.1-preX versions here, and have |
| 30 |
been since they went ~amd64.) That should just update the cache without |
| 31 |
doing the sync part first. |
| 32 |
|
| 33 |
If it's really the cache, that too will probably fail. If it doesn't |
| 34 |
fail, try another emerge --sync, as it should then be fixed. If it did |
| 35 |
fail as it likely will, you'll need to delete the cache and then run |
| 36 |
emerge --metadata again, to rebuild it. |
| 37 |
|
| 38 |
The cache is /var/cache/edb. Don't directly delete it. Instead, |
| 39 |
move/rename it to /var/cache/edb.bak or some such, thereby keeping a |
| 40 |
backup, just in case. Run emerge --metadata, then emerge --sync, and see if |
| 41 |
the problem is fixed. If it is, you can safely delete edb.bak. If not, |
| 42 |
delete the new edb and move the backup version back into place. At that |
| 43 |
point, you'll probably need a bit more advance help to figure out exactly |
| 44 |
which file is corrupted. However, it's quite likely that removing edb and |
| 45 |
letting portage rebuild it will fix the problem. |
| 46 |
|
| 47 |
-- |
| 48 |
Duncan - List replies preferred. No HTML msgs. |
| 49 |
"Every nonfree program has a lord, a master -- |
| 50 |
and if you use the program, he is your master." Richard Stallman |
| 51 |
|
| 52 |
-- |
| 53 |
gentoo-amd64@g.o mailing list |
Archives