On 4/8/2010 9:17 AM, Theodore Ts'o wrote: > If there are invalid block group checksums and a previous file system > is reformatted using lazy_itable_init, e2fsck can get confused with a > inodes from previous file systems. This is why the default is zero > out the entire inode table.
Isn't that why there are multiple copies of the block group descriptor table? If one got corrupted, wouldn't the backup then be consulted which would have the uninitialized flag set correctly so fsck would know to ignore the inode table? -- lazy_itable_init not on by default https://bugs.launchpad.net/bugs/556621 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
