public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mark Knecht <markknecht@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] recovery from /var corruption?
Date: Fri, 26 Feb 2010 10:57:13 -0800	[thread overview]
Message-ID: <5bdc1c8b1002261057v3bfca72cic3081013f07c2249@mail.gmail.com> (raw)
In-Reply-To: <3ac129341002260938h71168de3gd1fb22537798712a@mail.gmail.com>

On Fri, Feb 26, 2010 at 9:38 AM, daid kahl <daidxor@gmail.com> wrote:
> On 26 February 2010 12:33, Mark Knecht <markknecht@gmail.com> wrote:
>> So I got my wife's machine booted today using a install disk and
>> played a bit with e2fsck. The machine stopped being happy last night
>> due to some sort of corruption on the /var partition. e2fsck
>> complained about 3 or 4 files and then repaired the partition. The
>> machine booted cleanly as far as I can tell.
>>
>> So, something went bad and I managed to sneak around it for a while
>> and now I'm sort of living with the machine wondering what to do.
>>
>> Do I just watch the logs looking for problems? I have no way of
>> knowing right now whether this was a disk problem that's going to come
>> back, a 1 time deal due to power, or something else entirely.
>>
>> As these cheap machines that don't use RAID what's the right way to
>> go? emerge -e @world and then wait for the next event? Do nothing and
>> wait?
>>
>> We've got decent personal data backups as well as basic /etc data.
>>
>> Thanks,
>> Mark
>>
>
> I reconsidered your problem, and I actually wonder if emerging world
> is a valid notion in this case, as the world file is under /var and
> this is reported as corrupt.
>
> In this sense, it may be entirely non-trivial to regenerate (without
> backup) the correct world-file for a system.
>
> Am I out in the deep end, or is this, in fact, the critical point that
> needs consideration here?
>
> ~daid

Hi daid,
   In general you are correct. If I didn't have a copy of the world
file then it would be a bit hit and miss. In this case I do have it
saved elsewhere so it's actually quite easy.

   This failure is more (it seems) a few bad blocks on one partition
and not a total drive failure.

   I'm leaning toward a new /var partition and just ignoring the
partition that has problems. It will sit on the disk but it's only
10GB out of 160GB so it's not the end of the world by any means.

   Thanks!

- Mark



      reply	other threads:[~2010-02-26 18:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26  3:33 [gentoo-user] recovery from /var corruption? Mark Knecht
2010-02-26  9:09 ` Neil Bothwick
2010-02-26  9:46 ` Alex Schuster
2010-02-26 15:17   ` Mark Knecht
2010-02-26 16:01     ` Alex Schuster
2010-02-26 16:53       ` Mark Knecht
2010-02-26 17:27         ` Alex Schuster
2010-02-26 17:51           ` Mark Knecht
2010-02-26 17:59             ` Volker Armin Hemmann
2010-02-26 18:19               ` Paul Hartman
2010-02-26 18:26               ` Mark Knecht
2010-02-26 18:37                 ` Volker Armin Hemmann
2010-02-26 18:48                 ` Mark Knecht
2010-02-26 11:47 ` daid kahl
2010-02-26 17:38 ` daid kahl
2010-02-26 18:57   ` Mark Knecht [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5bdc1c8b1002261057v3bfca72cic3081013f07c2249@mail.gmail.com \
    --to=markknecht@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox