1 |
On Wednesday 09 June 2010 09:32:40 Neil Bothwick wrote: |
2 |
> On Wed, 9 Jun 2010 06:03:51 +0000, Mick wrote: |
3 |
> > Thanks I used reiser4progs to check and repair the fs. The weird |
4 |
> > thing is that I had to repeat this on the /var partition, after I |
5 |
> > zero'ed it, reformatted it and reinstalled gentoo on it. O_O |
6 |
> > |
7 |
> > How is it possible that the same directory/file gets corrupted again |
8 |
> > after a reinstall? |
9 |
> |
10 |
> The first thing I'd do it set PORTAGE_TMPDIR to somewhere less important |
11 |
> than /var. You don't want to risk corrupting system files while sorting |
12 |
> this out. It would also show whether the problem was with an ebuild or |
13 |
> the filesystem. Use a tmpfs filesystem if you have the memory. |
14 |
|
15 |
I had to reinstall because I didn't catch this early enough the first time and |
16 |
it corrupted my other system partitions. This corruption happened when I |
17 |
installed gcc-4.4.3-r2. |
18 |
|
19 |
After I reinstalled and while still running the LiveCD I updated gcc to the |
20 |
same gcc-4.4.3-r2 version. As I said, again I ended up with a corrupted |
21 |
'/var/tmp/portage/sys-devel/gcc-4.4.3- |
22 |
r2/work/gcc-4.4.3/libjava/classpath/resource/gnu/java/locale' directory. |
23 |
|
24 |
Running fsck.reiser4 --check and then --fix corrected the corruption and that |
25 |
was that. Before I reinstalled, the corruption must have been more pervasive |
26 |
because fsck.reiser4 could not fix it - a simple reboot would bring it back. |
27 |
|
28 |
So, my conclusion from this sad story is that on my system reiser4 was |
29 |
attacked by gcc! O_O |
30 |
|
31 |
I'd be interested to know if any other gentoo systems running a separate /var |
32 |
partition on reiser4 noticed this, in which case I'd file a bug for it. If |
33 |
I'm alone in having this problem then I'll wait until it happens again before |
34 |
I open a bug report. |
35 |
-- |
36 |
Regards, |
37 |
Mick |