From nobody Mon Jul 5 14:51:14 2021 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id C596A11D4637 for ; Mon, 5 Jul 2021 14:51:26 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-oi1-f170.google.com (mail-oi1-f170.google.com [209.85.167.170]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4GJTCf54Svz3vN5; Mon, 5 Jul 2021 14:51:26 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-oi1-f170.google.com with SMTP id s24so5941851oiw.2; Mon, 05 Jul 2021 07:51:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BSAzkRd4GVbQURAXfzf+DvLDUD9dTpRUkR6i2VAG6f0=; b=DLIpc0f8zNw1qB6qbMtPnsMpGH+s7Yd/j0hx8iS5jfXkgeGtNRE7Kq4T8Aif4wvQlN ne4/b+Y3Fp9ZSGRziUW2Q7FDQ9mMTwQJw8D4Mz2l2Wle6irRl2lD27o6bCN1W+fKy4pU wkieAk1quHTSfI6evBm/WV9K22br9twIUb+P1VZtkHVpNRsG0stqMd+SmcP1Fnv5gHnH Xg/ELhLyqongFWNCPiTFxu2EmEMeJxC34IuaDYFOmrIDTbojhNWtGqTVJmEx3dbEtVuZ lOKmi3v1ULMvFsTfffv4YoJQB2hSWXdpimLfifMk4SVDqihpmk/mbr6j9JrdxIk8IXw/ /GuA== X-Gm-Message-State: AOAM5338LmPJffI0/9fK0L8FitwB/my3taOYuUCl3M4HkF4+nLBRdIbW Q+4PAQXUVOJDMu/BVkdqoTwvPcu2KY0ov0lFB2l7wqi/Ul0= X-Google-Smtp-Source: ABdhPJzeX8U0aZz5f2NkEwtncTrfvR2PdXPTs5IFPAjWuHnHtQOEd5NB9V5bgC8MNAFGVKRGkL2r2A8INKXGdAW0eSs= X-Received: by 2002:a05:6808:bc1:: with SMTP id o1mr10880362oik.55.1625496685629; Mon, 05 Jul 2021 07:51:25 -0700 (PDT) List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 References: <89c37c3e-22e8-006e-5826-33bd7db7739e@ingresso.co.uk> <2fd9b7e4-dc75-fedc-28d7-b98191167e6b@freebsd.org> <9c71d627-55b8-2464-6cc9-489e4ce98049@ingresso.co.uk> In-Reply-To: <9c71d627-55b8-2464-6cc9-489e4ce98049@ingresso.co.uk> From: Alan Somers Date: Mon, 5 Jul 2021 08:51:14 -0600 Message-ID: Subject: Re: ZFS + mysql appears to be killing my SSD's To: Pete French Cc: Stefan Esser , FreeBSD Stable Mailing List Content-Type: multipart/alternative; boundary="00000000000087d45205c661707a" X-Rspamd-Queue-Id: 4GJTCf54Svz3vN5 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: Y --00000000000087d45205c661707a Content-Type: text/plain; charset="UTF-8" On Mon, Jul 5, 2021 at 8:31 AM Pete French wrote: > > > On 05/07/2021 14:37, Stefan Esser wrote: > > Hi Pete, > > > > have you checked the drive state and statistics with smartctl? > > Hi, thanks for the reply - yes, I did check the statistics, and they > dont make a lot of sense. I was just looking at them again in fact. > > So, one of the machines that we chnaged a drive on when this first > started, which was 4 weeks ago. > > root@telehouse04:/home/webadmin # smartctl -a /dev/ada0 | grep Perc > 169 Remaining_Lifetime_Perc 0x0000 082 082 000 Old_age > Offline - 82 > root@telehouse04:/home/webadmin # smartctl -a /dev/ada1 | grep Perc > 202 Percent_Lifetime_Remain 0x0030 100 100 001 Old_age > Offline - 0 > > Now, from that you might think the 2nd drive was the one changes, but > no. Its the first one, which is now at 82% lifetime remaining! The other > druve, still at 100%, has been in there a year. The drives are different > manufacturers, which makes comparing most of the numbers tricky > unfortunately. > > > Am now even more worried than when I sent the first email - if that 18% > is accurate then I am going to be doing this again in another 4 months, > and thats not sustainable. It also looks as if this problem has got a > lot worse recently. Though I wasnt looking at the numbers before, only > noticing tyhe failurses. If I look at 'Percentage Used Endurance > Indicator' isntead of the 'Percent_Lifetime_Remain' value then I see > some of those well over 200%. That value is, on the newer drives, 100 > minus the 'Percent_Lifetime_Remain' value, so I guess they ahve the same > underlying metric. > > I didnt mention in my original email, but I am encrypting these with > geli. Does geli do any write amplification at all ? That might explain > the high write volumes... > > -pete. > If you're using 4K sectors anyway, then GELI does not create any extra write amplification. But if you're extra paranoid and you use the "-T" option to "geli attach", then GELI will block TRIM commands. That could hurt SSD lifetime. But I don't think "-T" is the default. You are using 4K sectors, right? ZFS's ashift is set to 12? -Alan --00000000000087d45205c661707a--