From owner-freebsd-ports@FreeBSD.ORG Thu Aug 18 01:14:01 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C0D81065673; Thu, 18 Aug 2011 01:14:01 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id 7AC2E8FC0A; Thu, 18 Aug 2011 01:14:01 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p7I1DuPM042347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Aug 2011 18:13:56 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p7I1DuBN042346; Wed, 17 Aug 2011 18:13:56 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA08405; Wed, 17 Aug 11 18:03:47 PDT Date: Thu, 18 Aug 2011 01:03:28 -0700 From: perryh@pluto.rain.com To: utisoft@gmail.com, linimon@lonesome.com Message-Id: <4e4cc750.GqJImeHzdv6k8zld%perryh@pluto.rain.com> References: <201108171436.p7HEaNYQ071778@fire.js.berklix.net> <20110817161554.GA2496@lonesome.com> In-Reply-To: <20110817161554.GA2496@lonesome.com> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, ben@freebsd.org, phk@phk.freebsd.dk, jhs@berklix.com Subject: Re: sysutils/diskcheckd needs fixing and a maintainer 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: Thu, 18 Aug 2011 01:14:01 -0000 Chris Rees wrote: > We don't want to provide broken software. Mark Linimon wrote: > ... it's obsolete, broken, junk ... Unless there is more to this than is reported in those two PRs, I'd call it a considerable exaggeration to describe diskcheckd as "broken". * http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/115853 is shown as "closed", so presumably is no longer a problem. * http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/143566 says "... diskcheckd runs fine when gmirror is not involved ..." and then goes on to describe a problem _when diskcheckd is run on a component of a gmirror_. How anyone got from "in some way incompatible with gmirror" to "broken" escapes me. One could as well claim that gmirror is "broken" because it is incompatible with diskcheckd >:-> I'm currently running diskcheckd on an 8.1 gmirrored system with config file /dev/ad0 * * 8192 -- which should be using about 1/6 of that disk's bandwidth -- and will see what happens when it reaches the end of the disk (sometime tomorrow). So far I have not seen any issues.