From owner-freebsd-ports@FreeBSD.ORG Sun Jun 3 04:38:52 2007 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1A68816A421 for ; Sun, 3 Jun 2007 04:38:52 +0000 (UTC) (envelope-from craig@yekse.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.freebsd.org (Postfix) with ESMTP id 03AD013C45A for ; Sun, 3 Jun 2007 04:38:51 +0000 (UTC) (envelope-from craig@yekse.gank.org) Received: by ion.gank.org (Postfix, from userid 1001) id C8C33110F2; Sat, 2 Jun 2007 23:38:51 -0500 (CDT) Date: Sat, 2 Jun 2007 23:38:50 -0500 From: Craig Boston To: Thomas Hummel Message-ID: <20070603043850.GB1341@nowhere> Mail-Followup-To: Craig Boston , Thomas Hummel , Paul Schmehl , ports@freebsd.org References: <200706010521.l515LE4N074880@harmony.bsdimp.com> <20070601085750.ang0g5aqp0kg8c8k@webmail.leidinger.net> <20070601083345.GA48323@rot13.obsecurity.org> <10723ADA-FD53-45F8-BDFA-DBD98CBC212E@FreeBSD.org> <465FFE06.7010900@gmx.de> <20070601132205.GW43953@parmesan.sis.pasteur.fr> <6D9E1847C218B06AE67CB299@utd59514.utdallas.edu> <20070601154057.GY43953@parmesan.sis.pasteur.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070601154057.GY43953@parmesan.sis.pasteur.fr> User-Agent: Mutt/1.4.2.2i Cc: ports@freebsd.org, Paul Schmehl Subject: Re: Uggg! X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jun 2007 04:38:52 -0000 On Fri, Jun 01, 2007 at 05:40:57PM +0200, Thomas Hummel wrote: > Sure. But that doesn't explain why so many +CONTENT files were screwed > up and why there isn't a easy or easier way to re-generate them. Sound like pretty standard behavior of softupdates to me. Often files that were created within the last (memory fuzzy) seconds will be lost. I suspect in both cases the battery died right after an upgrade finished and portupgrade tweaked the +CONTENTS files of pretty much everything in order to update dependencies. I'd wager it's doing a create temp file/delete/rename dance. As far as I can tell, having files disappear is considered better than ending up with a corrupt filesystem, so sayeth the FS gods. It might be interesting to see how UFS+gjournal/ZFS stack up under similar circumstances. Craig (apologies if anyone has posted this already, I'm only about 1/3 down the thread)