From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 75881] lazyinit failure on new mdadm raid5 & encrypted array
Date: Mon, 12 May 2014 05:09:13 +0000 [thread overview]
Message-ID: <bug-75881-13602-l9Jq6meC7r@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-75881-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=75881
--- Comment #2 from TR Reardon <thomas_reardon@hotmail.com> ---
I cannot reproduce. A quick glance at the stack made me fear that this was not
an obvious ext4 problem but an interaction bug between block layers. Still
thought I should submit in case it proved useful...hard to easily repro errors
building 16TB arrays on production servers
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2014-05-12 5:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 18:47 [Bug 75881] New: lazyinit failure on new mdadm raid5 & encrypted array bugzilla-daemon
2014-05-11 19:05 ` [Bug 75881] " bugzilla-daemon
2014-05-12 5:09 ` 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-75881-13602-l9Jq6meC7r@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).