Whamcloud - gitweb
tune2fs: do not change j_tail_sequence in journal superblock
authorzhanchengbin <zhanchengbin1@huawei.com>
Thu, 4 Aug 2022 10:33:39 +0000 (18:33 +0800)
committerTheodore Ts'o <tytso@mit.edu>
Thu, 11 Aug 2022 16:57:21 +0000 (12:57 -0400)
commit003125b2f00aed8f0a1d8b5bd80fcbb1e8e2f13e
tree4553bc0a2c91aaba6e32977a2779d0b16a0dc836
parent3a3f3f153372ae5daafad5fb68d84847e9f17e9c
tune2fs: do not change j_tail_sequence in journal superblock

The function recover_ext3_journal() in debugfs/journal.c, if the log
replay is over, the j_tail_sequence in journal superblock is not
changed to the value of the last transaction sequence.  This will
cause subsequent log commitids to count from the commitid in last
time.  After tune2fs -e, the log commitid is counted from the commitid
in last time, if the log ID of the current operation overlaps with
that of the last operation, this will cause logs that were previously
replayed by tune2fs to be replayed here.

Signed-off-by: zhanchengbin <zhanchengbin1@huawei.com>
Signed-off-by: Zhiqiang Liu <liuzhiqiang26@huawei.com>
Signed-off-by: liangyun <liangyun2@huawei.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
debugfs/journal.c