SoylentNews is people
SoylentNews
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.
[Editor's Comment: Original Submission]
This discussion has been archived.
No new comments can be posted.
Running an ext4 RAID0 with a Linux 4.x Kernel? Better Spray for Bugs
|
Log In/Create an Account
| Top
| 45 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
"History is a tool used by politicians to justify their intentions."
-- Ted Koppel
(Score: 3, Insightful) by mr_mischief on Wednesday May 27 2015, @05:16PM
The simplicity of shell scripts controlling the system has pros and cons. The concept is simple. The scripts themselves often aren't very simple. There's definitely room to argue for scripts over unit files, but also vice versa.
The bit about Microsoft is a false association, though. Unit files are plaintext and simple. There's a separate one for each service. They aren't some binary blob locked in some poorly documented binary file together along with all the other information about all the other part of the system.
One thing Microsoft always has had right, though, despite their crap security record, huge code bloat, and illegal business practices, is that developers matter. On most Linux distros, package maintainers matter, too. Having a simple way for maintainers to package all that third-party open source code means faster turnaround. That means faster security fixes. It means quicker access to new features. It potentially more packages available. Making it easier for third parties to build packages makes it easier to deploy things not already packaged, especially via configuration management.
There's still a lot about systemd that sucks. Pragmatically, though, rather than ripping out all the stuff out there running on Linux and getting it working on FreeBSD, NetBSD, or OpenBSD in production and rather than forking one's own non-systemd Linux distro, most people are going to deal with what RedHat, Debian, and Ubuntu have given them. They'll try to find the best parts of that and take advantage of those even as they curse the rest of the changes as unnecessary fluff. People getting real work done five or six days a week don't have much choice.