4 ms·
All this QUIC talk makes me think of tape backups. Wonder if a tape backup could be devised which was inspired by network congestion algorithms - i.e. if a sect
by actionfromafar 3y ago
All this QUIC talk makes me think of tape backups. Wonder if a tape backup could be devised which was inspired by network congestion algorithms - i.e. if a section of bad tape was discovered, the same data would get "resent" - to tape! Until it read back correctly (by a read head just behind the write head).
This way, the overall tape data density could be increased even if it would mean occasional dropouts.
Maybe this is already how modern tape drives work?
- Veserv 3y agoTransparently remapping good storage over bad storage to deal with faulty sectors is standard practice in hard disk drives and solid state drives. It was historically done in software, though these days it is largely done in the drive microcontrollers directly. Tape drives almost certainly use similar techniques.
- HankB99 3y agoWikipedia confirms that IBM introduced this in 1958. > Separate read/write heads providing transparent read-after-write verification.
- actionfromafar 3y agoThere's a general IBM theme of "whatever tech we come up with", IBM did it first, a very long time ago, they have their own name for it, and everyone else "discovers" it years or decades later.
- Karellen 3y ago> It was historically done in software, though these days it is largely done in the drive microcontrollers directly. It's still software on the drive microcontrollers, though. The only difference is it's software you can't see, reason about, upgrade, improve, or fix.
- RiverCrochet 3y agoIf a modern "one-shot" tape drive encounters an error during write, it will write the data again as the tape is moving. You lose a little bit of total capacity, but the data will still get written. This is why you always plan to write a little less than the full capacity of your tape. Newer LTOs may behave a little differently, I haven't kept up with newer stuff here.