From owner-freebsd-fs@FreeBSD.ORG Tue Feb 13 20:24:02 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.ORG Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3520D16A407 for ; Tue, 13 Feb 2007 20:24:02 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 9D2B013C46B for ; Tue, 13 Feb 2007 20:24:01 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (uhktgb@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l1DKNsS2022199; Tue, 13 Feb 2007 21:24:00 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l1DKNsjM022198; Tue, 13 Feb 2007 21:23:54 +0100 (CET) (envelope-from olli) Date: Tue, 13 Feb 2007 21:23:54 +0100 (CET) Message-Id: <200702132023.l1DKNsjM022198@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG, john@kozubik.com In-Reply-To: <20070213104959.K95571@kozubik.com> X-Newsgroups: list.freebsd-fs User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 13 Feb 2007 21:24:00 +0100 (CET) Cc: Subject: Re: comments on newfs raw disk ? Safe ? (7 terabyte array) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-fs@FreeBSD.ORG, john@kozubik.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2007 20:24:02 -0000 John Kozubik wrote: > Oliver Fromme wrote: > > That's not what I wrote. I wrote that they _had_ issues, > > and that I do not know if they have been fixed. I don't > > recall any reports of problems recently (i.e. in the past > > few months), and there are no open PRs that seem to relate > > to the current code, so those issues may very well have > > been fixed. It's just my personal paranoia that lets me > > disable bg fsck on my machines (and I don't really need > > bg fsck anyway). > > Fair enough. For your information, they are still dangerous and > unstable[1][2][3]. Well, lets see ... [1] is from January 2006, applies to 6.0-RELEASE and has zero follow-ups. [2] is from July 2004 and was closed in May 2005 because it wasn't reproducible with the new compiler and no more feedback from the submitter was provided. [3] doesn't link to any PR or other information. > Your initial assessment is still valid today, > unfortunately. FWIW, [1] is open and relates to the current code. It says 6.0-RELEASE. FreeBSD 6 might have been "-current" at that time, but it's hardly current today. :-) > [1] http://lists.freebsd.org/pipermail/freebsd-bugs/2006-January/016703.html > [2] http://lists.freebsd.org/pipermail/freebsd-bugs/2004-July/007574.html > [3] [2, above] has been fixed, but large quantity inode movements keep > coming back to haunt snapshots every other release or so... In that case a new PR should be opened, I think. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "I learned Java 3 years before Python. It was my language of choice. It took me two weekends with Python before I was more productive with it than with Java." -- Anthony Roberts