问题原文
原帖链接 · Prototype700 · CC BY-SA 4.0
I have recently looked into advanced filesystems (Btrfs, ZFS) for data redundancy and availability and got interested in the additional functionality they provide, especially their "self-healing" capabilities against data corruption.
However, I think I need to take a step back and try to understand if this benefit outweighs their disadvantages (Btrfs bugs and unresolved issues & ZFS availability and performance impact) for general home/SMB-usage, compared to a conventional mdadm-Raid1 + Ext4 solution. A mirrored backup is available either way.
Let's assume I have a couple of file servers which are used for archival purposes and have limited resources, but ECC memory and a stable power source.
- How likely am I to even encounter actual data corruption making files unreadable? How?
- Can Ext4 or the system file manager already detect data errors on copy/move operations, making me at least aware of a problem?
- What happens if one of the madam-Raid1 drives holds different data due to one drive having bad sectors? Will I still be able to retrieve the correct file or will the array be unable to decide which file is the correct one and lose it entirely?
社区高分解答
原帖链接 · Mircea Vutcovici · CC BY-SA 4.0
I had a Seagate HDD that started failing checksums each time I was running zfs scrub. It failed after a few weeks. ZFS and Btrfs have checksums for data and metadata. ext4 has only metadata chcksums.
Only CRC errors and metadata checksum errors. Data corruption can happen.
If it has bad sectors it is not a problem. The entire disk will be "failed", but you have the other disk that is "fine". The problem is when the data has correct CRC, but the data is corrupted. This can happen randomly because of large disks.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
