From owner-freebsd-fs@freebsd.org Fri Feb 19 14:29:14 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A5A9AAEB3B for ; Fri, 19 Feb 2016 14:29:14 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (mail.sorbs.net [67.231.146.200]) by mx1.freebsd.org (Postfix) with ESMTP id 8E43E1C87 for ; Fri, 19 Feb 2016 14:29:13 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 8BIT Content-type: text/plain; charset=windows-1252 Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0O2S00F4STWF9Q00@hades.sorbs.net> for freebsd-fs@freebsd.org; Fri, 19 Feb 2016 06:36:17 -0800 (PST) Message-id: <56C726B6.5050108@sorbs.net> Date: Fri, 19 Feb 2016 15:29:10 +0100 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Steven Hartland Cc: freebsd-fs@freebsd.org Subject: Re: Zfs heavy io writing | zfskern txg_thread_enter References: <56C70365.1050800@sorbs.net> <56C70AB0.6050400@multiplay.co.uk> <56C71350.3020602@sorbs.net> <56C71DD8.3040505@multiplay.co.uk> <56C72155.10500@sorbs.net> <56C7222F.2090009@sorbs.net> In-reply-to: <56C7222F.2090009@sorbs.net> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Feb 2016 14:29:14 -0000 Michelle Sullivan wrote: > Links to the grabs inline because the list seems to have converted > html->plaintext > > Michelle Sullivan wrote: > >> Steven Hartland wrote: >> >> >>> On 19/02/2016 13:06, Michelle Sullivan wrote: >>> >>> >>>> Steven Hartland wrote: >>>> >>>> >>>>> On 19/02/2016 11:58, Michelle Sullivan wrote: >>>>> >>>>> >>>>>> Niccolò Corvini wrote: >>>>>> >>>>>> >>>>>>> Hi, first time here! >>>>>>> We are having a problem with a server running FreeBsd 9.1 with ZFS >>>>>>> on a >>>>>>> >>>>>>> >>>>>>> >>>>>> You should upgrade to a supported version first... 9.3 would probably >>>>>> be the best (rather than 10.x) as it's still supported and uses the >>>>>> same >>>>>> ABI (ie you should need to reinstall all your ports/packages - though >>>>>> you should because it sometimes breaks things - at least check for >>>>>> broken things :) .) >>>>>> >>>>>> If you're not familiar "freebsd-update -r 9.3-RELEASE upgrade" will >>>>>> help >>>>>> you do it without too many problems. >>>>>> >>>>>> >>>>> 9.3 is still ancient, and while "supported" its not in active >>>>> development, and to be blunt no one will be interested in helping to >>>>> diagnose any actual issue on something so old. >>>>> >>>>> >>>> So supported is not really supported... Is that an official position? >>>> >>>> >>> Supported for 9.x, which is a "Legacy Release", I would say is >>> supported for security and other critical issues only, which is the >>> same for pretty much every project / product out there. >>> >>> >> Oh, it's legacy is it? Funny you should say that ... "Production = >> Legacy" then...? >> >> >> > ----> http://flashback.sorbs.net/packages/freebsd-page.jpg > And yes to reply to my own message before you do... I know what it says on the releases page ... but that's not what it says to anyone looking for information about what to download and install, or what is supported or not... I mean seriously if there is no support for 9.x why are you telling people it is an option for a new installation because its a current production version...? Why is it even listed on the support page as a 'currently supported' version? I mean it became obvious to some of us even though I never saw an official announcement that 9.x is being retired as quickly as possible therefore there will be no x.4 release unlike other releases... but at least update the documentation to say 9.x is no longer a production version and nothing except critical security issues will be fixed on the support page... because *that* is what you just indicated... Put it in the release documentation, announce it, so at least everyone will know for certain there is no point in asking for help.... Michelle -- Michelle Sullivan http://www.mhix.org/