public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Seagate hard drives with dual actuators.
Date: Sun, 17 Nov 2024 18:04:34 -0500	[thread overview]
Message-ID: <VL43KSZM.WX4TAYHL.UQDT6CU2@3A7PDRNJ.4JWAS2OM.UYQRY47Q> (raw)
In-Reply-To: <CAGfcS_kKM24kbw-f8QGkmLYgDm1Zc5jkkcnyNNr2dEbtyR8YbA@mail.gmail.com>

On 2024.11.17 16:26, Rich Freeman wrote:
> On Sun, Nov 17, 2024 at 6:22 AM Michael <confabulate@kintzios.com>  
> wrote:
> > On Saturday 16 November 2024 20:13:30 GMT Rich Freeman wrote:
[snip ....]
> > It would be interesting to see how different fs types perform on  
> DM-SMRs.
> 
> Not that interesting, for me personally.  That's like asking how well  
> different filesystems would perform on tape.  If I'm storing data on  
> tape, I'll use an algorithm designed to work on tape, and a tape  
> drive that actually has a command set that doesn't try to pretend  
> that it is useful for random writes.
What about DEC-Tape?  :-)  (https://en.wikipedia.org/wiki/DECtape)  (I  
may even have a few left in a closet somewhere, if only I could find  
someone to read them.)

> SMR is pretty analogous to tape, with the benefit of being as fast as  
> CMR for random reads.

[snip ....]


  reply	other threads:[~2024-11-17 23:04 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13 23:10 [gentoo-user] Seagate hard drives with dual actuators Dale
2024-11-14  0:46 ` Matt Jolly
2024-11-14 13:05   ` Dale
2024-11-14  7:55 ` Wols Lists
2024-11-14 16:48   ` Dale
2024-11-15  0:18     ` [OT] " Peter Humphrey
2024-11-15  8:41       ` [gentoo-user] Hollerith (was: Seagate hard drives with dual actuators) karl
2024-11-15  9:51       ` [OT] Re: [gentoo-user] Seagate hard drives with dual actuators Wols Lists
2024-11-14 11:21 ` Michael
2024-11-14 17:00   ` Dale
2024-11-14 19:12     ` Michael
2024-11-14 19:51       ` Frank Steinmetzger
2024-11-14 19:55         ` Frank Steinmetzger
2024-11-14 23:14           ` Peter Humphrey
2024-11-14 20:33       ` Dale
2024-11-14 20:57         ` Rich Freeman
2024-11-14 23:10           ` Dale
2024-11-15  0:59             ` Rich Freeman
2024-11-15  5:53               ` Dale
2024-11-15 10:09                 ` Michael
2024-11-15 11:59                   ` Dale
2024-11-15 15:35                     ` Michael
2024-11-15 16:36                       ` Dale
2024-11-15 22:13                       ` Rich Freeman
2024-11-16 11:02                         ` Michael
2024-11-16 14:36                           ` Rich Freeman
2024-11-16 19:47                             ` Michael
2024-11-16 20:13                               ` Rich Freeman
2024-11-16 23:21                                 ` Wol
2024-11-17 11:22                                 ` Michael
2024-11-17 21:26                                   ` Rich Freeman
2024-11-17 23:04                                     ` Jack [this message]
2024-11-18  0:23                                       ` Rich Freeman
2024-11-18  2:32                                         ` Matt Jolly
2024-11-15 10:38                 ` Frank Steinmetzger
2024-11-15 12:19                   ` Dale
2024-11-14 22:38         ` Wols Lists
2024-11-15  9:35           ` Michael

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=VL43KSZM.WX4TAYHL.UQDT6CU2@3A7PDRNJ.4JWAS2OM.UYQRY47Q \
    --to=ostroffjh@users.sourceforge.net \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox