Minor Description
When specifying the mmp_update_interval option, mke2fs command does not take it into account and initialize the filesystem with the default value (5 seconds).
mke2fs -j -b 4096 -L fsperf-OST0000 -j -J device=/dev/ldn.sfa10kt.jp22 -m 0 -I 256 -i 524288 -O extents,uninit_bg,mmp,dir_nlink,huge_file,flex_bg -G 256 -E lazy_itable_init=0,lazy_journal_init=0,mmp_update_interval=10,resize=4290772992 -F /dev/ldn.sfa10kt.dp22 1891631104
^^^^^^^^^^^^^^^^^^^^^^
mke2fs 1.42.3.wc3 (15-Aug-2012)
Filesystem label=fsperf-OST0000
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
14778368 inodes, 1891631104 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4290772992
57728 block groups
32768 blocks per group, 32768 fragments per group
256 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544
Allocating group tables: done
Writing inode tables: done
Adding journal to device /dev/ldn.sfa10kt.jp22: done
Multiple mount protection is enabled with update interval 5 seconds. <================
Writing superblocks and filesystem accounting information: done
Looking at the code, the command parameters are correctly parsed by the value stored in fs_param->s_mmp_update_interval is not transmitted to the filesystem superblock descriptor: fs->super->s_mmp_update_interval.
I will provide a patch.