From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 95875C3A5A9 for ; Tue, 5 May 2020 02:22:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 729E2206B9 for ; Tue, 5 May 2020 02:22:43 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=colorremedies-com.20150623.gappssmtp.com header.i=@colorremedies-com.20150623.gappssmtp.com header.b="S9VUkrfW" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726885AbgEECWm (ORCPT ); Mon, 4 May 2020 22:22:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50712 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726531AbgEECWm (ORCPT ); Mon, 4 May 2020 22:22:42 -0400 Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DD9B0C061A0F for ; Mon, 4 May 2020 19:22:41 -0700 (PDT) Received: by mail-wm1-x336.google.com with SMTP id h4so455285wmb.4 for ; Mon, 04 May 2020 19:22:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=colorremedies-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YvtOJ6OnXxi8N+V9ajSGW4uUb5yRuZ82sqRrCAUJenk=; b=S9VUkrfWpxd7kYdBGdxcu6aklJg6qHTU0aK2LlH5X70MYbjJ/qKdbG4Be+wG/Upr0p q14NH00LEmBP3pWrlTOuNFeh3bxPtz+Pz5QNq5b8+U6cqp1xFVL1Rq9yaSBJOc3GWVqF aG6AO5lEUBa2Ws/22QI6R6+cqSGK/GlZt+XwxhpSLVDZ4IHNyUEu0hmxPtfjw9yZ3gxt Hp2SdouqXpZ3w12N7KzzDBazzvlJNvdRL3TQdhT3q8Vc0YhvSPzuyXz2Xw6d5SsDhE5F clILsNQ5QwlAEl6Iy4SohKWvEmLEH+nfpy96RV6Ifc/5Zu9i7Gyaaso5y/npoWqZdgw4 i5zQ== 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=YvtOJ6OnXxi8N+V9ajSGW4uUb5yRuZ82sqRrCAUJenk=; b=akwf1myUnjReusg2sl3O+X0ng/BKSCZefnTvKnFTqeV5neJhpbG2s9dmIL+JFFKY7r 5wm2Oey/TLMTSgDqGVMLxaxxdcgZkZtbmnEXw//bvnpwfr1hzItCpilSRA03oP/8yEiX PfaWQcVyt0OmZHuF522qIT3ElEkX8qn2yc09RrT+ihVnSMTcq7SFwCKAZp5Cv737rCyv ihqXiS6eWSZO01t5Da63VyUb7ICpZgO7yZKiDZQGUqVqzQ9VhSWdC35v4IDliskThrtF WnP23lzwGHjItC+XlwtSVgz9EL8b6srk14UNflXNs5iRquI+B6sv5zGXLVvMQ36yxZpt H5QQ== X-Gm-Message-State: AGi0PuZwkGkxcA88DPzV/fqM31FsGlp6gPypD15hV29izV7XkLrmzSJ2 02vLcpLT/TuFuQqA9FNpq+rI8Oqv8RS15CjhgttEAQ== X-Google-Smtp-Source: APiQypI2MOJ0fCG3YDJ2tlDNzfFeQJqQnKpj+p4QVWEc2W+3cLh3kb0XD/lmB6yK4zRrOUM9F/THWxd6QmfJmU7MJ54= X-Received: by 2002:a1c:6455:: with SMTP id y82mr553393wmb.128.1588645360605; Mon, 04 May 2020 19:22:40 -0700 (PDT) MIME-Version: 1.0 References: <20200504230857.GQ10769@hungrycats.org> <20200505020021.GR10769@hungrycats.org> In-Reply-To: <20200505020021.GR10769@hungrycats.org> From: Chris Murphy Date: Mon, 4 May 2020 20:22:24 -0600 Message-ID: Subject: Re: Western Digital Red's SMR and btrfs? To: Zygo Blaxell Cc: Chris Murphy , Rich Rauenzahn , Btrfs BTRFS Content-Type: text/plain; charset="UTF-8" Sender: linux-btrfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-btrfs@vger.kernel.org On Mon, May 4, 2020 at 8:00 PM Zygo Blaxell wrote: > > On Mon, May 04, 2020 at 05:24:11PM -0600, Chris Murphy wrote: > > On Mon, May 4, 2020 at 5:09 PM Zygo Blaxell > > wrote: > > > > > Some kinds of RAID rebuild don't provide sufficient idle time to complete > > > the CMR-to-SMR writeback, so the host gets throttled. If the drive slows > > > down too much, the kernel times out on IO, and reports that the drive > > > has failed. The RAID system running on top thinks the drive is faulty > > > (a false positive failure) and the fun begins (hope you don't have two > > > of these drives in the same array!). > > > > This came up on linux-raid@ list today also, and someone posted this > > smartmontools bug. > > https://www.smartmontools.org/ticket/1313 > > > > It notes in part this error, which is not a time out. > > Uhhh...wow. If that's not an individual broken disk, but the programmed > behavior of the firmware, that would mean the drive model is not usable > at all. I haven't gone looking for a spec, but "sector ID not found" makes me think of a trim/remap related failure, which, yeah it's gotta be a firmware bug. This can't be "works as designed". -- Chris Murphy