Bug 113781
Summary: | kernel 4.4.1-2-ARCH, 4.4.3-1-ARCH and Fake RAID array setup | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Andre Hasekamp (hasecomp) |
Component: | MD | Assignee: | fs_ext4 (fs_ext4) |
Status: | NEW --- | ||
Severity: | normal | CC: | hasecomp |
Priority: | P1 | ||
Hardware: | x86-64 | ||
OS: | Linux | ||
Kernel Version: | 4.4.1-2-ARCH, 4.4.3-1-ARCH | Subsystem: | |
Regression: | Yes | Bisected commit-id: |
Description
Andre Hasekamp
2016-03-05 13:57:05 UTC
2016-03-13 Kernel 4.4.5-1-ARCH device-mapper 2.02.145-1 thin-provisioning-tools 0.6.1-2 Unfortunately the problem remains the same. Andre Hasekamp. 2016-04-21 Archlinux is now at: Kernel 4.5.1-1 dmraid 1.0.0.rc16.3-10 device-mapper 2.02.149-1 thin-provisioning-tools 0.6.1-2 At this stage, I can run a linux system again from "Fake RAID array" disks (RAID 0) on PC 1 (decribed above). Although it is not clear what caused it, to me it is so much improvement that I will use "Fake RAID array" disks again. Neverthless, in the meantime, after having encountered the problems described, I have moved my production work to Archlinux installations on SSD. At the moment I have 2 PCs, each with a functioning linux test system on "Fake RAID array" disks. These test systems are not frequently used. So it may take a while before I consider these test systems to be reliable enough for production work. From my point of view, you may close this bug. Should the "Fake RAID array" disks present problems again in the future, then I will open a new bugreport. Since the status of the current bug report is still NEW, I trust that you have not spent any time on it yet. Kind regards, Andre Hasekamp. |