From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RLvxm-0008RM-Ms for garchives@archives.gentoo.org; Thu, 03 Nov 2011 12:00:10 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D103321C043; Thu, 3 Nov 2011 11:59:55 +0000 (UTC) Received: from mail-bw0-f53.google.com (mail-bw0-f53.google.com [209.85.214.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 7FC9021C025 for ; Thu, 3 Nov 2011 11:59:19 +0000 (UTC) Received: by bkbzs8 with SMTP id zs8so1294059bkb.40 for ; Thu, 03 Nov 2011 04:59:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=rn5Rr3XxbVmfhogF7LaxVKjrAA0XH0YMNfxaSKMXg28=; b=kaWqkpSg7BFhirFiKbVq9Z98bdc0QkVwu/oMYB1gAimrKPXuPVCs9qnRYNh6/moSQk FbWbWHue4aRrbML0832oQwLGtXGsEVDgM7JPXdQ+i4CvkCEHo4s7hqgPw8J0VLeY55H9 Ii+aDKWxLV+6iSt8F2z4Qv8+4cSNRgJL3n8bQ= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Received: by 10.204.131.66 with SMTP id w2mr7665111bks.49.1320321558445; Thu, 03 Nov 2011 04:59:18 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.204.65.195 with HTTP; Thu, 3 Nov 2011 04:59:18 -0700 (PDT) In-Reply-To: <4EB277D9.3070302@gentoo.org> References: <4EB277D9.3070302@gentoo.org> Date: Thu, 3 Nov 2011 07:59:18 -0400 X-Google-Sender-Auth: x1sJ59fdg94HCMvASjsmcCxjoLM Message-ID: Subject: Re: [gentoo-dev] recovering from corrupted vdb From: Rich Freeman To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 704578d6-81db-4a85-bdfb-3910870a9b3e X-Archives-Hash: 7c3f71e21ff8afdbdf4e791e0b4aab1f On Thu, Nov 3, 2011 at 7:15 AM, "Pawe=C5=82 Hajdan, Jr." wrote: > I think we can't salvage much from a corrupted db (anything can happen, > and the reporter mentions some code being present in the files), but at > least "emerge -e world" or equivalent should be possible. I'm not sure how portage handles not having ANYTHING in the vdb, but wouldn't it at least be possible to just wipe out the entire directory tree and then do an emerge -e world? As long as the packages themselves are working I would think that this should work. The only thing I'm not sure about is that if portage thinks that nothing is installed it might run into circular dependency issues. Maybe we need an option to include dependencies in the list of packages to install but not bail out on circular dependency issues since the reality is that the packages are there. Or, we need to give the user a script to follow (maybe try to follow whatever the logic is in catalyst since obviously that works). If the packages themselves are corrupted then installing from binary packages for @system would make sense. That thread really sounds like some kind of filesystem corruption issue, even if fsck doesn't report any problems. Something like that happened to me ages ago with some kind of mdadm+lvm+ext3 bug (an fsck on one lvm partition destroyed data on a different partition). A more intelligent solution would be to actually check the system for consistency (file hashes, etc), and then just re-emerge the stuff that is broken. Rich