All of lore.kernel.org
 help / color / mirror / Atom feed
* question about jbd2 checksum v2 and v3 flag
@ 2019-08-16 23:55 Shehbaz Jaffer
  2019-08-26  3:05 ` Andreas Dilger
  0 siblings, 1 reply; 6+ messages in thread
From: Shehbaz Jaffer @ 2019-08-16 23:55 UTC (permalink / raw)
  To: linux-ext4

Hello,

I am trying to understand jbd2 checksumming procedure. I reboot ext4
in the middle of a metadata intensive operation using echo b>
/proc/sysrq-trigger. I see that the journal gets replayed on next
mount using prinks in jbd2/recovery.c: do_one_pass() function.

I then corrupt intermediate metadata logged on jbd2 and I still see
the journal being replayed without multiple error messages which
should ideally get printed when one of the two following flags -
JBD2_FEATURE_INCOMPAT_CSUM_V2 or JBD2_FEATURE_INCOMPAT_CSUM_V3 are
set.

I have 2 questions:

1. Are the two flags: JBD2_FEATURE_INCOMPAT_CSUM_V2 and
JBD2_FEATURE_INCOMPAT_CSUM_V3 set by default? If not, how do we set
them so that the journal will detect and respond to injected
corruptions?

2. this is very naive question, but what do compat and incompat
options mean? If flag X in incompat is set, does this mean the feature
does not exist?

Thank you,

-- 
Shehbaz Jaffer

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2019-08-27 20:06 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-08-16 23:55 question about jbd2 checksum v2 and v3 flag Shehbaz Jaffer
2019-08-26  3:05 ` Andreas Dilger
2019-08-26 16:51   ` Theodore Y. Ts'o
2019-08-26 18:31     ` Darrick J. Wong
2019-08-26 18:56       ` Theodore Y. Ts'o
2019-08-27 20:06       ` Andreas Dilger

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.