1 |
On Sunday 26 November 2006 13:33, Fabrice Delliaux wrote: |
2 |
> Le Sun, 26 Nov 2006 13:41:56 +0100, |
3 |
> |
4 |
> Harm Geerts a écrit : |
5 |
> > This only forces portage to retrieve *all* of portage's metadata from |
6 |
> > the server *again*. |
7 |
> |
8 |
> Yes. |
9 |
> |
10 |
> > If the corruption is local, a normal rsync will fix this. |
11 |
> |
12 |
> Not necessarily. See bug #145482. |
13 |
> Synchronization again and again (on several days) didn't resolve this. |
14 |
> I removed the entire cache, as suggested, and it magically worked. |
15 |
> And I discovered later that the filesystem was corrupted. |
16 |
> |
17 |
> > If the corruption is on the upstream rsync mirror, you will retrieve |
18 |
> > the same corrupt metadata again. |
19 |
> |
20 |
> I've never seen that case. |
21 |
> |
22 |
> > removing the metadata from the portage tree only results in more data |
23 |
> > transfers from the rsync mirror. |
24 |
> |
25 |
> Yes, but obviously, you must not do it every day. |
26 |
> |
27 |
> @Mick : I suggest that you run a fsck on your filesystem. |
28 |
|
29 |
Thanks. I did run fsck and everything seems fine. However, although |
30 |
emerge --metadata worked, the following emerge --sync failed with the same |
31 |
old error. |
32 |
|
33 |
So, this time I did emerge --regen and when it finished the emerge --sync |
34 |
worked without any more problems. |
35 |
|
36 |
Thanks for all the suggestions. |
37 |
-- |
38 |
Regards, |
39 |
Mick |