From owner-freebsd-stable@FreeBSD.ORG Wed May 13 09:42:58 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 04FB0106566B for ; Wed, 13 May 2009 09:42:58 +0000 (UTC) (envelope-from milu@dat.pl) Received: from jab.dat.pl (dat.pl [80.51.155.34]) by mx1.freebsd.org (Postfix) with ESMTP id 9C4F88FC1D for ; Wed, 13 May 2009 09:42:57 +0000 (UTC) (envelope-from milu@dat.pl) Received: from localhost (jsrv.dat.pl [127.0.0.1]) by jab.dat.pl (Postfix) with ESMTP id C3516A8; Wed, 13 May 2009 11:24:31 +0200 (CEST) X-Virus-Scanned: amavisd-new at dat.pl Received: from jab.dat.pl ([127.0.0.1]) by localhost (jab.dat.pl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1fbsOWqn3Hgn; Wed, 13 May 2009 11:24:28 +0200 (CEST) Received: from snifi.localnet (87-204-241-35.ip.netia.com.pl [87.204.241.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by jab.dat.pl (Postfix) with ESMTPSA id 8242C99; Wed, 13 May 2009 11:24:28 +0200 (CEST) From: Maciej Milewski To: Pat Wendorf Date: Wed, 13 May 2009 11:24:16 +0200 User-Agent: KMail/1.11.2 (Linux/2.6.29-ARCH; KDE/4.2.2; x86_64; ; ) References: <2c2c47aa0905121110i6355930bwce3a9c6afb117d4d@mail.gmail.com> In-Reply-To: <2c2c47aa0905121110i6355930bwce3a9c6afb117d4d@mail.gmail.com> MIME-Version: 1.0 Message-Id: <200905131124.16897.milu@dat.pl> 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 09:42:58 -0000 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 I= DE > drives on a mostly terrible UPS. A few months ago, when it returned from= a > power outage (running 6.2-R) I started noticing the following in my daily > 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 any > operation on them (including ls in the directory). > > I've managed to ignore the problem for a while now, and even upgraded to > 7.2, but I'm not sure if it will cause problems later on. So the question > 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 firs= t=20 thing to do would be to stop as many daemons as possible and leaving only s= sh=20 to get to this system remotely? I really don't know how much dangerous could be unmounting /var on a live=20 system in such case. =2D-=20 Pozdrawiam, Maciej Milewski