Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 7 Sep 2005 13:45:13 -0400
From:      Kris Kennaway <kris@obsecurity.org>
To:        Eric Anderson <anderson@centtech.com>
Cc:        questions@freebsd.org, Robert Watson <rwatson@freebsd.org>, Mikhail Teterin <mi+kde@aldan.algebra.com>, fs@freebsd.org
Subject:   Re: Strange case of filesystem corruption?
Message-ID:  <20050907174513.GA32771@xor.obsecurity.org>
In-Reply-To: <431DB382.7000904@centtech.com>
References:  <200509051953.22337@aldan> <20050906114055.R51625@fledge.watson.org> <200509060931.33977@aldan> <20050906144512.T75104@fledge.watson.org> <431DB382.7000904@centtech.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--9jxsPFA5p3P2qPhR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 06, 2005 at 10:19:30AM -0500, Eric Anderson wrote:
> Robert Watson wrote:
> >On Tue, 6 Sep 2005, Mikhail Teterin wrote:
> >
> >>On Tuesday 06 September 2005 06:51 am, Robert Watson wrote:
> >>=3D Have you recently experienced a system crash or hard reboot without=
=20
> >>proper
> >>=3D shutdown?
> >>
> >>According to dmesg.boot, this filesystem was flagged as "not properly=
=20
> >>dismounted" back then. The machine's uptime is currently 47 days and=20
> >>no background fskcs are running, of course.
> >>
> >>Yours analysis is, likely, correct then... I guess, the fix should be=
=20
> >>MFCed. (What about 6.0-release?) Thanks!
> >
> >
> >The change was made in HEAD before the 6.x branch, so it's currently in=
=20
> >RELENG_6.  I fired off an e-mail to Kirk to ask about MFC'ing it to=20
> >RELENG_5, and will do so once I hear back, assuming he thinks there is=
=20
> >no reason not to.
> >
> >Do you have back logs to when bgfsck was running, btw?  Normally it=20
> >should correct this sort of thing, suggestion that bgfsck exited without=
=20
> >correcting them, which is a little worrying.  You may want to boot to=20
> >single user and fsck manually...
>=20
> I thought that having background_fsck=3D"NO" in your rc.conf would make=
=20
> the partition get mounted even though it is unclean, and no fsck's would=
=20
> happen (I use this 'feature' right now, since doing bgfsck on a 2TB=20
> partition takes about 2 hours just to make the snapshot, which means=20
> filesystem activity is suspended for that time).

AFAIK, no, this just does a regular old fg fsck.

Kris
--9jxsPFA5p3P2qPhR
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFDHycpWry0BWjoQKURAro6AKDbtwdlhFeFMkrLC6dMmAyX7NTmmgCg/Q7w
jXqBhbOvhpqUueaoI9j7+7w=
=O1pD
-----END PGP SIGNATURE-----

--9jxsPFA5p3P2qPhR--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050907174513.GA32771>