From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 61631] kernel BUG at fs/ext4/super.c:818 umounting md raid6 volume
Date: Sat, 21 Sep 2013 02:11:27 +0000 [thread overview]
Message-ID: <bug-61631-13602-PIfVQgW0vZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-61631-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=61631
--- Comment #8 from Jim Faulkner <jfaulkne@ccs.neu.edu> ---
I suspect commit bf7bd3e98be5c74813bee6ad496139fb0a011b3b will indeed fix this
issue since it sounds exactly like my issue.
However, before applying any patch, I'll do the debug tests that Ted suggests
so we can be sure. I need some uptime to be sure I can reproduce this bug, so
I'll report back a few days from now.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-09-21 2:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 22:05 [Bug 61631] New: kernel BUG at fs/ext4/super.c:818 umounting md raid6 volume bugzilla-daemon
2013-09-18 22:06 ` [Bug 61631] " bugzilla-daemon
2013-09-18 22:07 ` bugzilla-daemon
2013-09-18 22:10 ` bugzilla-daemon
2013-09-18 22:27 ` bugzilla-daemon
2013-09-19 18:58 ` Theodore Ts'o
2013-09-19 0:58 ` bugzilla-daemon
2013-09-19 19:20 ` bugzilla-daemon
2013-09-20 22:41 ` bugzilla-daemon
2013-09-21 2:08 ` bugzilla-daemon
2013-09-21 2:11 ` bugzilla-daemon [this message]
2013-10-12 0:14 ` bugzilla-daemon
2013-10-12 0:17 ` bugzilla-daemon
2013-10-12 0:17 ` bugzilla-daemon
2013-10-12 0:19 ` bugzilla-daemon
2013-10-12 0:21 ` bugzilla-daemon
2013-10-15 7:58 ` bugzilla-daemon
2013-10-15 7:58 ` bugzilla-daemon
2013-10-15 7:58 ` bugzilla-daemon
2013-10-15 7:59 ` bugzilla-daemon
2013-10-15 8:04 ` bugzilla-daemon
2013-10-20 2:10 ` bugzilla-daemon
2013-10-20 22:32 ` bugzilla-daemon
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-61631-13602-PIfVQgW0vZ@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).