Date: Wed, 13 May 2009 14:46:26 +0200 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-stable@freebsd.org Subject: Re: File system corruption Message-ID: <gueff2$sei$2@ger.gmane.org> In-Reply-To: <200905131124.16897.milu@dat.pl> References: <2c2c47aa0905121110i6355930bwce3a9c6afb117d4d@mail.gmail.com> <200905131124.16897.milu@dat.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8298E08ADBFA12A7A9FF1D3B Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Maciej Milewski wrote: > Tuesday 12 May 2009 20:10:57 Pat Wendorf napisa=C5=82(a): >> I have a co-lo server I've been maintaining for a few years now runnin= g IDE >> drives on a mostly terrible UPS. A few months ago, when it returned f= rom a >> power outage (running 6.2-R) I started noticing the following in my da= ily >> security email: >> >> Checking setuid files and devices: >> find: >> /var/db/portsnap/files/2dc95ddff37a8091239e83bf7e3ce5a2c285b027891ced1= 919d7 >> 6c9947c5b7db.gz: Bad file descriptor >> find: >> /var/db/portsnap/files/52abe8c91385b12272f13f4d20896067d9ba70bdec1fa25= 75025 >> 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 a= ny >> 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 ques= tion >> is, without access to the console, how would I fix this? >=20 >=20 >=20 > 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=20 > thing to do would be to stop as many daemons as possible and leaving on= ly ssh=20 > to get to this system remotely? > I really don't know how much dangerous could be unmounting /var on a li= ve=20 > system in such case. Not critically dangerous - it can be done with care. Of course, it's best to reboot afterwards :) --------------enig8298E08ADBFA12A7A9FF1D3B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoKwSIACgkQldnAQVacBchSkwCg1SBtT3r/LgrPdDUwD6oUB4jf gUYAnj+1S1/rcfVuW8XOaWink5XmDIk5 =3IrA -----END PGP SIGNATURE----- --------------enig8298E08ADBFA12A7A9FF1D3B--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?gueff2$sei$2>