From: Junxiao Bi <junxiao.bi@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: fix BUG due to uncleaned localalloc during mount
Date: Wed, 2 Dec 2015 09:44:11 +0800 [thread overview]
Message-ID: <565E4CEB.3080707@oracle.com> (raw)
In-Reply-To: <20151201164454.624f2294f6142b9b2fe4bd74@linux-foundation.org>
On 12/02/2015 08:44 AM, Andrew Morton wrote:
> On Tue, 1 Dec 2015 16:02:55 +0800 Junxiao Bi <junxiao.bi@oracle.com> wrote:
>
>> On 11/24/2015 09:38 PM, Joseph Qi wrote:
>>> Tariq has reported a BUG before and posted a fix at:
>>> https://oss.oracle.com/pipermail/ocfs2-devel/2015-April/010696.html
>>>
>>> This is because during umount, localalloc shutdown relies on journal
>>> shutdown. But during journal shutdown, it just stops commit thread
>>> without checking its result. So it may happen that localalloc shutdown
>>> uncleaned during I/O error and after that, journal then has been marked
>>> clean if I/O restores.
>> The above is a storage issue. In this condition, io error can even
>> happen to journal commit, some transactions may have wrong data. Let fs
>> go without a fsck may cause corruption.
>> I am thinking whether we can fail the mount and mark the journal dirty
>> again. Then we can do fsck to it withoug a fsck patch.
>
> hm, was that an ack, a nack or a quack?
nack, i think we need another way to fix this issue.
Thanks,
Junxiao.
>
next prev parent reply other threads:[~2015-12-02 1:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 13:38 [Ocfs2-devel] [PATCH] ocfs2: fix BUG due to uncleaned localalloc during mount Joseph Qi
2015-12-01 8:02 ` Junxiao Bi
2015-12-02 0:44 ` Andrew Morton
2015-12-02 1:44 ` Junxiao Bi [this message]
2015-12-02 6:52 ` Xue jiufei
2015-12-02 7:07 ` Junxiao Bi
-- strict thread matches above, loose matches on Subject: below --
2015-11-25 1:08 Shichangkuo
2015-11-25 2:01 ` Joseph Qi
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=565E4CEB.3080707@oracle.com \
--to=junxiao.bi@oracle.com \
--cc=ocfs2-devel@oss.oracle.com \
/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