-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2016-12-23 23:49, sdm wrote:
On 12/23/2016 02:04 PM, Paul Neuwirth wrote:
maybe another reason to switch back to ext4. btrfsck failed IIRC with exit code 234. ran btrfsck --repair /dev/md2 . now I started btrfsck --repair -p /dev/md2 and waiting for result (tons of lines).
The chances of btrfs failing in RAID 1 are very slim, like near 0, unless a controller issue or problems with the drive(s) themselves.
Not true.
mdadm is software RAID and it's not surprising people have issues with it as software RAID is not production-level RAID.
That's not true, either.
It's easy to point the finger at the filesystem when in actuality it's shoddy hardware or just because the parity bits get all messed up because of software RAID. The more recent problems with btrfs and RAID had to do with RAID 5/6, and supposedly the issues have been mostly fixed.
Those are problems with btrfs own version of raid, which has nothing to do with traditional Linux software raid, which is what the OP is using. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlhdv4IACgkQja8UbcUWM1wLUgD/b/WkgI9vo78cfWilvWcn5HUL Vy7yQbNPxSfaCZMpRyQA/ioDovAcKFj3niqcHW8m2xDK8K/Yq2WyGpRBtgZw5Jri =dU9K -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org