From owner-freebsd-stable@FreeBSD.ORG Thu Oct 10 18:09:42 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 2D03A857 for ; Thu, 10 Oct 2013 18:09:42 +0000 (UTC) (envelope-from to.my.trociny@gmail.com) Received: from mail-ee0-x22d.google.com (mail-ee0-x22d.google.com [IPv6:2a00:1450:4013:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B9A0F2094 for ; Thu, 10 Oct 2013 18:09:41 +0000 (UTC) Received: by mail-ee0-f45.google.com with SMTP id c50so1356275eek.32 for ; Thu, 10 Oct 2013 11:09:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=MV/O/5Vb24sfdig3t5Hhjk13AYq+w3c4kGRGrRR+RuQ=; b=nFIhCBeOOAhRSViAmYYn3nqNeqK/wvzQl3A1JA8cUriqIBqFdUMPr9EOFAgoazmNbT ijo2xtRHUr+UttL2FTnw+DXQXzOmcMf9V03Q5SBn3Mm7Oz6rxIw3Lmkl1Ifwp2wp8KaJ co/v1gAgaXzCFawuZ9m4TpAw+H6Ys/+AVl+hLYNn01CmMmF2kIa/0o/JKXgVUS4aAy9m d+i18Dy3Wb32Hgnu5vixi3frZOa68C53MhGjDYdAZ0Xd2f/P8MN84TXExrxNIrlzmn8+ EjW4gz/FG0IFFHvikFRYcNNaOiUpXtMetblLGsC2tWFvVH0GkwICAtI//uxYSK8IOwu2 ftDg== X-Received: by 10.14.29.67 with SMTP id h43mr22506898eea.7.1381428580145; Thu, 10 Oct 2013 11:09:40 -0700 (PDT) Received: from localhost ([178.150.115.244]) by mx.google.com with ESMTPSA id m54sm104360168eex.2.1969.12.31.16.00.00 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Oct 2013 11:09:39 -0700 (PDT) Sender: Mikolaj Golub Date: Thu, 10 Oct 2013 21:09:37 +0300 From: Mikolaj Golub To: Steven Hartland Subject: Re: hast and zfs trim possibly causing some problems in 9.2 Message-ID: <20131010180936.GP44942@gmail.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org, Pete French X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 18:09:42 -0000 On Wed, Oct 09, 2013 at 03:47:29PM +0100, Steven Hartland wrote: > ZFS will try to send DELETE requests to the underlying storage to > support TRIM. If that fails then it will disable TRIM support for > that vdev. > > My guess would be you're just seeing hast being a bit verbose > when these initial batch failures happen. If the device on the secondary node does not supports DELETE, but the device on the primary does, HAST will report to ZFS that DELETE succeeded (although it failed on the secondary), and ZFS will not disable TRIM. Pete, isn't this your case? > From: "Pete French" > > >I just had a machine fall over on my for the first time in ages - one > > of a pair of machine we have running hast with zfs on top. I havent > > got any concrete evidence of what made it die as yet, but I > > did notice the logifles filling up with thoursands of lines like this > > just prior to the crash: > > > > serpentine-active hastd[1522]: [serp1] (primary) Remote request failed (Operation not supported): DELETE(26847744000, 1536). > > > > so I am guessing taht is ZFS trying to send a trim command to hast, and hast > > does not support it. Have disabled zfs trim now, but thought it was > > worth mentioning - I would have not expected zfs to be trying to issue > > a trim command to an underlying device which doesnt support it. These > > machines were rock solid under 8, and the only chnage I can see with 9 is > > the trim support being added. Another important change that comes to mind is the default replication mode, changed from fullsync to memsync. Do you have the replication mode explicitly set in your config? -- Mikolaj Golub