| 1 |
On Fri, Feb 26, 2010 at 9:38 AM, daid kahl <daidxor@×××××.com> wrote: |
| 2 |
> On 26 February 2010 12:33, Mark Knecht <markknecht@×××××.com> wrote: |
| 3 |
>> So I got my wife's machine booted today using a install disk and |
| 4 |
>> played a bit with e2fsck. The machine stopped being happy last night |
| 5 |
>> due to some sort of corruption on the /var partition. e2fsck |
| 6 |
>> complained about 3 or 4 files and then repaired the partition. The |
| 7 |
>> machine booted cleanly as far as I can tell. |
| 8 |
>> |
| 9 |
>> So, something went bad and I managed to sneak around it for a while |
| 10 |
>> and now I'm sort of living with the machine wondering what to do. |
| 11 |
>> |
| 12 |
>> Do I just watch the logs looking for problems? I have no way of |
| 13 |
>> knowing right now whether this was a disk problem that's going to come |
| 14 |
>> back, a 1 time deal due to power, or something else entirely. |
| 15 |
>> |
| 16 |
>> As these cheap machines that don't use RAID what's the right way to |
| 17 |
>> go? emerge -e @world and then wait for the next event? Do nothing and |
| 18 |
>> wait? |
| 19 |
>> |
| 20 |
>> We've got decent personal data backups as well as basic /etc data. |
| 21 |
>> |
| 22 |
>> Thanks, |
| 23 |
>> Mark |
| 24 |
>> |
| 25 |
> |
| 26 |
> I reconsidered your problem, and I actually wonder if emerging world |
| 27 |
> is a valid notion in this case, as the world file is under /var and |
| 28 |
> this is reported as corrupt. |
| 29 |
> |
| 30 |
> In this sense, it may be entirely non-trivial to regenerate (without |
| 31 |
> backup) the correct world-file for a system. |
| 32 |
> |
| 33 |
> Am I out in the deep end, or is this, in fact, the critical point that |
| 34 |
> needs consideration here? |
| 35 |
> |
| 36 |
> ~daid |
| 37 |
|
| 38 |
Hi daid, |
| 39 |
In general you are correct. If I didn't have a copy of the world |
| 40 |
file then it would be a bit hit and miss. In this case I do have it |
| 41 |
saved elsewhere so it's actually quite easy. |
| 42 |
|
| 43 |
This failure is more (it seems) a few bad blocks on one partition |
| 44 |
and not a total drive failure. |
| 45 |
|
| 46 |
I'm leaning toward a new /var partition and just ignoring the |
| 47 |
partition that has problems. It will sit on the disk but it's only |
| 48 |
10GB out of 160GB so it's not the end of the world by any means. |
| 49 |
|
| 50 |
Thanks! |
| 51 |
|
| 52 |
- Mark |
Archives