[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201105311929.p4VJThFo023179@demeter2.kernel.org>
Date: Tue, 31 May 2011 19:29:43 GMT
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 36172] "kernel BUG at fs/ext4/super.c" triggered after
tune2fs/remount
https://bugzilla.kernel.org/show_bug.cgi?id=36172
Manish Katiyar <mkatiyar@...il.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mkatiyar@...il.com
--- Comment #3 from Manish Katiyar <mkatiyar@...il.com> 2011-05-31 19:29:40 ---
Yes, either tune2fs should be fixed to not change the mounted fs state, or the
code should be prepared to deal with it silently. Since the next mount isn't
going
to see the journal, it doesn't matter whether we clear the errors or not.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists