From: Daeho Jeong <daeho.jeong@samsung.com>
To: "tytso@mit.edu" <tytso@mit.edu>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Cc: 정대호 <daeho.jeong@samsung.com>, 길영진 <youngjin.gil@samsung.com>
Subject: Re: [PATCH] e2fsck: update j_tail_sequence after recovery
Date: Wed, 01 Jun 2016 07:13:25 +0000 (GMT) [thread overview]
Message-ID: <159772701.338101464765204534.JavaMail.weblogic@epmlwas09b> (raw)
Hi,
Ping on this.
> When journal is released, s_sequence is set to j_tail_sequence.
> But, currently, even if the recovery process is successfully completed,
> the j_tail_sequence and, finally, s_sequence are never changed. By this,
> when we repeat doing power-off the device suddenly and executing e2fsck
> without full scan before mount, the s_sequence number will never change
> and, in a very rare case, newly generated journal logs will be
> surprisingly grafted to the old journal logs. In this case, out-of-date
> metadata log can be replayed on the filesystem area and the filesystem
> can be crashed unintentionally by journal recovery process. Therefore,
> we need to update j_tail_sequence after recovery process is successfully
> completed in e2fsck.
next reply other threads:[~2016-06-01 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 7:13 Daeho Jeong [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-04-25 4:43 [PATCH] e2fsck: update j_tail_sequence after recovery Daeho Jeong
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=159772701.338101464765204534.JavaMail.weblogic@epmlwas09b \
--to=daeho.jeong@samsung.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=youngjin.gil@samsung.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;
as well as URLs for NNTP newsgroup(s).