From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 2E4A11382C5 for ; Tue, 16 Jun 2020 12:26:09 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1CD17E0D98; Tue, 16 Jun 2020 12:26:01 +0000 (UTC) Received: from mail-ed1-f45.google.com (mail-ed1-f45.google.com [209.85.208.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C2DECE0D82 for ; Tue, 16 Jun 2020 12:26:00 +0000 (UTC) Received: by mail-ed1-f45.google.com with SMTP id e12so14108668eds.2 for ; Tue, 16 Jun 2020 05:26:00 -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; bh=4KO0mLxHKAtQ+xrpZOPCpAd6bj6w4DZ5ZyAGNCPurjo=; b=JCLzunEz3fPPam0SLKxFC2kXrL9LNMWHN8dAG7eNH/IPwD9Oq4IfDbsynV8dHJ6iBM UGVuE4WEdw7VFMH73NchqwSL5pT3xN1oK4Zj48WCYNuCvQkF5YPOVSZbVObjXhoAkkMB pZNsoWNx12CXyM1nif6RWHvWeXctgeYvBAZ9SCeeBFvqLJj9eunSnEScVmmY4J4LV9DG T0WtTB7p37wp2FB5gqp4UFnJQpuAIxGyHSVe6kq+H10K/yn1b8iCdGfzos5FBKfm++Tk mcWdAg3uLAfYl/NT0qEriqpelbpqwmNheDnnt6AKVf6PVXnxRTtK1C51DkuPIUP66v16 +PAA== X-Gm-Message-State: AOAM531/8ks9222OhM8URmNIdgHDZ+5cpLsJswlcF0vgTS8T//Jcsjvb vvX+SLY+iSk2mMCMVoG22gnsU+CwaIR/GNy7BNMafQFm X-Google-Smtp-Source: ABdhPJzBZNi/rPUaA/UfhvEoZhBkP4ms2R1tfIOU7aCrnCAvlQGRUppUyc57WpDeUMRwwJ4FPjS4TkJfOI3w24iOij4= X-Received: by 2002:a50:f052:: with SMTP id u18mr2279688edl.16.1592310359108; Tue, 16 Jun 2020 05:25:59 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <6d77acb3-5754-06cb-b8ef-2f1a5d7d8084@gmail.com> <5EE8A6C9.9020900@youngman.org.uk> <5611481.lOV4Wx5bFT@lenovo.localdomain> In-Reply-To: <5611481.lOV4Wx5bFT@lenovo.localdomain> From: Rich Freeman Date: Tue, 16 Jun 2020 08:25:48 -0400 Message-ID: Subject: Re: [gentoo-user] Testing a used hard drive to make SURE it is good. To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset="UTF-8" X-Archives-Salt: 880ac74c-378d-49c1-89c8-e61cda703f04 X-Archives-Hash: ca19bb9b3116bd5bb354d92d159d6106 On Tue, Jun 16, 2020 at 7:36 AM Michael wrote: > > Just to add my 2c's before you throw that SMR away, the use case for these > drives is to act as disk archives, rather than regular backups. You write > data you want to keep, once. If your write pattern is more like a tape SMR should be ok in theory. For example, if you wrote to a raw partition using tar (without a filesystem) I suspect most SMR implementations (including drive-managed) would work tolerably (a host-managed implementation would perform identically to CMR). Once you toss in a filesystem then there is no guarantee that the writes will end up being sequential. And of course the problem with these latest hidden SMR drives is that they generally don't support TRIM, so even repeated sequential writes can be a problem because the drive doesn't realize that after you send block 1 you're going to send blocks 2-100k all sequentially. If it knew that then it would just start overwriting in place obliterating later tracks, since they're just going to be written next anyway. Instead this drive is going to cache every write until it can consolidate them, which isn't terrible but it still turns every seek into three (write buffer, read buffer, write permanent - plus updating metadata). If they weren't being sneaky they could have made it drive-managed WITH TRIM so that it worked more like an SSD where you get the best performance if the OS uses TRIM, but it can fall back if you don't. Sequential writes on trimmed areas for SMR should perform identically to writes on CMR drives. -- Rich