Date: Wed, 13 May 2009 11:24:16 +0200 From: Maciej Milewski <milu@dat.pl> To: Pat Wendorf <dungeons@gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: File system corruption Message-ID: <200905131124.16897.milu@dat.pl> In-Reply-To: <2c2c47aa0905121110i6355930bwce3a9c6afb117d4d@mail.gmail.com> References: <2c2c47aa0905121110i6355930bwce3a9c6afb117d4d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905131124.16897.milu>