All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 20 Oct 2013 02:10:45 +0000	[thread overview]
Message-ID: <bug-61631-13602-gQNhUe70L5@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 #15 from Jim Faulkner <jfaulkne@ccs.neu.edu> ---
Looks like bf7bd3e98be5c74813bee6ad496139fb0a011b3b indeed fixed it.  I ran
3.11.5 (which I believe includes that patch) for a few days, doing normal
activities such as nfs i/o and rdiff-backups.  I was able to umount without
problems.  Thanks for fixing this!

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2013-10-20  2:10 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
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 [this message]
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-gQNhUe70L5@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.