upvote
I've got a few USB drives that are always attached that I do stuff with.

To pick a not-RAID example, I've got an old (2012-vintage) 180GB SATA SSD, from Intel, on my desk. It gets used as scratch space for big-ish file operations, where it gets hammered hard periodically, usually in bursts. It's plugged into a cheap SATA <> USB 3 adapter, and is otherwise-unadorned. It is bus-powered.

It's usually connected to the back of the PC, but it's been plugged into different USB ports (with different controller types) and also external hubs.

I don't recall what its exact status was when I starting doing that with it after pulling it out of a gently-used Thinkpad T530 about 5 years ago, but I do recall thinking that it had lots of life left.

Here's where it is today:

  - 10.6 years powered on
  - 81TB written (of 36.5TB promised); ~222% over spec
  - Zero reallocated sectors
  - One singular hardware-reported error (corrected)
  - Zero sector reallocations
And the pièce de résistance:

  - Zero reported errors according to ZFS checksums
That last one is important because in this application, ZFS automatically and continuously provides end-to-end verification, and it's been doing...perfectly fine.

The other USB storage devices here that are used 24/7 are similar in this way. It's not hellish at all. It's quite lovely.

I'm inclined to further extrapolate that it would not have better data integrity when connected directly to a SATA port on the motherboard, or in a disk shelf attached via iSCSI or SAS or some other more-stodgy thing. It's hard get results that exceed beyond perfection.

(But in this example, I'm not chasing down minute bus timing issues with multi-gig networks. That's a very different kind of discussion.)

reply
You really must hate yourself to attempt that.
reply