From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 113781] kernel 4.4.1-2-ARCH, 4.4.3-1-ARCH and Fake RAID array setup
Date: Thu, 21 Apr 2016 20:06:57 +0000 [thread overview]
Message-ID: <bug-113781-13602-D3dGZ3uIkh@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-113781-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=113781
--- Comment #2 from Andre Hasekamp <hasecomp@aim.com> ---
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.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2016-04-21 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 13:57 [Bug 113781] New: kernel 4.4.1-2-ARCH, 4.4.3-1-ARCH and Fake RAID array setup bugzilla-daemon
2016-03-05 15:40 ` [Bug 113781] " bugzilla-daemon
2016-03-05 15:41 ` bugzilla-daemon
2016-03-13 11:01 ` bugzilla-daemon
2016-04-21 20:06 ` bugzilla-daemon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-113781-13602-D3dGZ3uIkh@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).