The combination of RAID0 redundancy, an ext4 filesystem, a Linux 4.x kernel, and either Debian Linux or Arch Linux has been associated with data corruption.
El Reg reports EXT4 filesystem can EAT ALL YOUR DATA
Fixes are available, one explained by Lukas Czerner on the Linux Kernel Mailing List. That post suggests the bug is long-standing, possibly as far back as the 3.12-stable kernel. Others suggest the bug has only manifested in Linux 4.x.
[...] This patch for version 4.x and the patched Linux kernel 3.12.43 LTS both seem like sensible code to contemplate.
(Score: 2, Insightful) by Placenta on Tuesday May 26 2015, @10:21PM
How does any of that apply when the system in question refuses to boot because of a failure of systemd?
(Score: 2) by kaszz on Tuesday May 26 2015, @10:37PM
§1 Systemd is flawless and the solution to everything(tm)
§2 If rule (1) should for any reason be wrong. Just ask Poettering about it's validity.
;-)
(Score: 2) by mr_mischief on Wednesday May 27 2015, @05:04PM
It doesn't apply if the init system fails to initialize the system. How often does that happen, though? We run plenty of CentOS 7 and I don't remember having any failures to boot.
(Score: 1) by Placenta on Wednesday May 27 2015, @09:50PM
I had it happen to me numerous times while running Debian systems that used systemd. I finally got fed up, and moved these Debian systems to other OSes.