From owner-freebsd-current Sat Jun 2 17:59:18 2001 Delivered-To: freebsd-current@freebsd.org Received: from superconductor.rush.net (superconductor.rush.net [208.9.155.8]) by hub.freebsd.org (Postfix) with ESMTP id E95C937B422 for ; Sat, 2 Jun 2001 17:59:15 -0700 (PDT) (envelope-from bright@superconductor.rush.net) Received: (from bright@localhost) by superconductor.rush.net (8.11.2/8.11.2) id f530xDd00570; Sat, 2 Jun 2001 20:59:13 -0400 (EDT) Date: Sat, 2 Jun 2001 20:59:13 -0400 From: Alfred Perlstein To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: dirpref and RELENG_4 fsck Message-ID: <20010602205912.F1832@superconductor.rush.net> References: <20010602154633.A25944@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <20010602154633.A25944@xor.obsecurity.org>; from kris@obsecurity.org on Sat, Jun 02, 2001 at 03:46:33PM -0700 X-all-your-base: are belong to us. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Kris Kennaway [010602 18:46] wrote: > Was it determined that the fsck corruption problems which were seen > with fsck after the introduction of the dirpref changes do not affect > RELENG_4? I haven't seen any MFC of changes to the RELENG_4 fsck > code, and I'm kind of worried now that I've reverted my current system > back to RELENG_4 :-) Afaik the problem was that fsck would wipe certain stats info that dirpref would use, however I think the kernel detects absurd values and will reinit them. I could be way off about this though. :) -- -Alfred Perlstein [alfred@freebsd.org] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message