blackstrat

joined 1 year ago
[–] blackstrat@lemmy.fwgx.uk 1 points 5 months ago (1 children)

Same as any OS, yes

[–] blackstrat@lemmy.fwgx.uk 2 points 5 months ago (3 children)

It doesn't tell you up front that it's going to break

[–] blackstrat@lemmy.fwgx.uk 5 points 6 months ago (1 children)

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

[–] blackstrat@lemmy.fwgx.uk 2 points 6 months ago

"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.

[–] blackstrat@lemmy.fwgx.uk 3 points 6 months ago (1 children)

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.

[–] blackstrat@lemmy.fwgx.uk 1 points 6 months ago (1 children)

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)

[–] blackstrat@lemmy.fwgx.uk 1 points 6 months ago

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!

[–] blackstrat@lemmy.fwgx.uk 2 points 6 months ago

And why I no longer run NC. Every time it would fuck itself to death and I'd have to start from scratch again.

[–] blackstrat@lemmy.fwgx.uk 6 points 7 months ago

Ahh yes, the first time it is defined is in the conclusion after being used 25 times previously in the article.

view more: ‹ prev next ›