On Fri, 18 Feb 2011, bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote: > > These panics can be suppressed by using -E lazy_itable_init at mkfs time. The > test system survived two series of 10 ffsb tests beginning with a single mkfs > each. Subsequently, the system survived a run of about 16 hours in which a > complete scalability measurement pass was made > Hi Eric, Are you saying that it works fine (without panic) with lazy_itable_init feature enabled ? I am confused now, because in the first trace "spinlock bad magic: ext4lazyinit" the ext4lazyinit thread is obviously running. When the ext4lazyinit thread is running, it means that inode table was not zeroed, hence kernel thread (ext4lazyinit) is trying to do the job. Am I missing something ? Note that on the kernel which supports lazy itable initialization (/sys/fs/ext4/features/lazy_itable_init exists) the mke2fs (since v1.41.12-50-g210fd2c) will skip inode table initialization automatically (it is the same as you would specify -E lazy_itable_init). Thanks! -Lukas -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
