Pretty sure my Seagate usb disks I use for backup are SMR and sustained writes are awfully slow. Luckily I've discovered restic for backing up which lowered a 1.5tb weekly incremental backup from 9hrs to 1 min.
blackstrat
joined 1 year ago
I highly recommend watching this guys videos on his analysis of the backblaze data https://www.youtube.com/watch?v=IgJ6YolLxYE&t=1
And a comparison of the difference WD drive colours, which might not be what you expect https://www.youtube.com/watch?v=QDyqNry_mDo&t=2
"It's never lost data for me. Yet" is what they mean.
I totally agree, the only file system I've lost data with as a result of a file system corruption not caused by hardware errors or power problems in 35 years has been btrfs. FAT even served me better.
But pulling the power on a btrfs drive at the wrong time results in you not even being able to mount it as read only. No snapshotting can help you there.
And yet here we are 16 years later with btrfs only just in a position to be usable (perhaps. My experience is that I'll never use it again)
It cares so much that when it goes wrong you can't even mount the partitions as readonly to try get your data back. It will stubbornly hold on to it and refuse any access at all. Boy I am so glad it didn't let me access a potentially corrupted byte somewhere!
And why I no longer run NC. Every time it would fuck itself to death and I'd have to start from scratch again.
Sue's-uh
Ahh yes, the first time it is defined is in the conclusion after being used 25 times previously in the article.
Thank you! I hate unexplained acronyms
I skimmed through it and have no idea what BBR stands for.
Just because a DE looks sparse doesn't means it also uses less resources. In imagine KDE would actually run well as it doesn't need all the bells it offers and is actually a well written performant DE.