• Korhaka@sopuli.xyz
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    1
    ·
    2 days ago

    Does it really matter that much if the first copy takes a while though? Only doing it once and you don’t even have to do it all in 1 go. Just let it run over the weekend would do though.

      • Korhaka@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        1
        ·
        16 hours ago

        It’s only the first copy that takes such a long time. After that you only copy the changes.

          • Korhaka@sopuli.xyz
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            11 hours ago

            Sure, if you have many TBs of data changes per day you probably want a different solution. But that would also suggest you don’t need to keep it for very long.

            • DefederateLemmyMl@feddit.nl
              link
              fedilink
              English
              arrow-up
              1
              ·
              4 hours ago

              Write speeds on SMR drives start to stagnate after mere gigabytes written, not after terabytes. As soon as the CMR cache is full, you’re fucked, and it stagnates to utterly unusable speeds as it’s desperately trying to balance writing out blocks to the persistent area of the disk and accepting new incoming writes. I have 25 year old consumer level IDE drives that perform better than an SMR drive in this thrashing state.

              Also, I often use hard drives as a temporary holding area for stuff that I’m transferring around for one reason or another and that absolutely sucks if an operation that normally takes an hour or two is suddenly becoming a multi-day endeavour tying up my computing resources. I was burned once when Seagate submarined SMR drives into the Barracuda line, and I got a drive that was absolutely unfit for purpose. Never again.