You can try mounting the OST with "-o noinit_itable". This doesn't fix the formatting (not sure why that isn't being recognized), but it prevents the kernel thread from zeroing the inode table.
This could cause problems for e2fsck in the distant future if certain types of corruption are hit, but does not affect testing in any way Cheers, Andreas On 2013-10-14, at 7:35, "Lambert, Cedric" <[email protected]<mailto:[email protected]>> wrote: Hello, Sorry for this trivial question, but I did not find the solution myself : Everyone in the ldiskfs/ext4 community is happy since the OST formatting is quicker with the uninit_bg and lazy_itable_init features. And I appreciate a lot this feature too ! However, today for a particular test, When I format my OSTs, I would like this task to be completely finished in order to be sure to have the maximum OSTs bandwidth when I run my benchmarks. So, I tried the following : --mkfsoptions="-E lazy_itable_init=0,lazy_journal_init=0" but no success : formatting is still really quick and as soon as I mount my OST, iostats show me the formatting activity on it. Is it still possible to format like in the old ext3 age ? Thanks for your help Cédric _______________________________________________ Lustre-discuss mailing list [email protected]<mailto:[email protected]> http://lists.lustre.org/mailman/listinfo/lustre-discuss _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
