From owner-freebsd-stable@FreeBSD.ORG Wed May 13 20:37:12 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CDD7106564A for ; Wed, 13 May 2009 20:37:12 +0000 (UTC) (envelope-from dungeons@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id 373298FC08 for ; Wed, 13 May 2009 20:37:11 +0000 (UTC) (envelope-from dungeons@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so491647yxb.13 for ; Wed, 13 May 2009 13:37:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=V7SxtfuFV7JEglK+F/qL2sUyO+YZBE9UUG66E5ZFFj0=; b=GAkw4XXQXqdZ08qATdpavibUJQV3TaDkAJVASueh10F4a1HKuHhpIbF3IV4r6c6K5i Z6Q3m3yT7OFPEViiVJupoQChs5HsNoWNguVMB+Y0RkAPZT3QwRMz6G7tW6RgbTXOYSoa 3HUERflVuqMy6DmyWDDhm9z2AKviyhlzCFMgs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=YqsZlzyCBQN8mCJTY6VxFw3fnUSUcytnsoqB6uWqqr2fIHJ/++0MVG7Z7668wm6FP7 hLawmQvpUnU0i459dp0GjyLGi9YXiSuBJYXw/HbI5/7pOKrTubxF27Rh1drDXvXv6Few hgSxwGwARLka34doBB9gwI1IUPujzH0Y+EfBY= MIME-Version: 1.0 Received: by 10.100.46.12 with SMTP id t12mr1827297ant.55.1242247031087; Wed, 13 May 2009 13:37:11 -0700 (PDT) In-Reply-To: <200905131124.16897.milu@dat.pl> References: <2c2c47aa0905121110i6355930bwce3a9c6afb117d4d@mail.gmail.com> <200905131124.16897.milu@dat.pl> Date: Wed, 13 May 2009 16:37:09 -0400 Message-ID: <2c2c47aa0905131337w4a338386t2407f7df7a398cf7@mail.gmail.com> From: Pat Wendorf To: Maciej Milewski Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: File system corruption X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 May 2009 20:37:12 -0000 I spoke too soon I guess: A buddy of mine at the hosting provider took down the box and did a fsck -y on the var partition, this seems to have cleaned it up. It looks like the regular fsck -p could not repair it. 2009/5/13 Maciej Milewski > Tuesday 12 May 2009 20:10:57 Pat Wendorf napisa=B3(a): > > > I have a co-lo server I've been maintaining for a few years now running > IDE > > drives on a mostly terrible UPS. A few months ago, when it returned fro= m > a > > power outage (running 6.2-R) I started noticing the following in my dai= ly > > security email: > > > > Checking setuid files and devices: > > find: > > > /var/db/portsnap/files/2dc95ddff37a8091239e83bf7e3ce5a2c285b027891ced1919= d7 > >6c9947c5b7db.gz: Bad file descriptor > > find: > > > /var/db/portsnap/files/52abe8c91385b12272f13f4d20896067d9ba70bdec1fa25750= 25 > >858bd3e93718.gz: Bad file descriptor > > find: /var/lost+found/#238237: Bad file descriptor > > > > I verified that these files return the same result when trying to do an= y > > operation on them (including ls in the directory). > > > > I've managed to ignore the problem for a while now, and even upgraded t= o > > 7.2, but I'm not sure if it will cause problems later on. So the questi= on > > is, without access to the console, how would I fix this? > > > I think tere is a need for fsck on this partition. > /var is used by many daemons for logging, mailqueue etc., so maybe the > first thing to do would be to stop as many daemons as possible and leavin= g > only ssh to get to this system remotely? > I really don't know how much dangerous could be unmounting /var on a live > system in such case. > > > > > -- > Pozdrawiam, > Maciej Milewski >