What does the first inode do? On Oct 3, 2011 3:37 PM, "Theodore Ts'o" <[email protected]> wrote: > The bad block inode was corrupted in such a way that e2fsck got > confused. I have implemented a partial protection against which is in > the latest 1.42 pre-release version of e2fsprogs. > > The short-term workaround is to use debugfs -w /dev/sdXXX and then use > the command "clri <1>". That will clear out the bad block inode. > > Note that with this kind of corruption, it's likely that the first part > of the inode table has been corrupted, so it's likely the root inode, > and possibly other files, will have been damaged/lost as well. When > crap gets written into the inode table, there's not much e2fsck can > do.... > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/861281 > > Title: > FSCK on fs with claimed blocks yields Programming Error in > process_bad_block > > Status in “e2fsprogs” package in Ubuntu: > New > > Bug description: > Pass 1: Checking inodes, blocks, and sizes > Programming error? block #2013802232 claimed for no reason in process_bad_block. > Programming error? block #1648606690 claimed for no reason in process_bad_block. > Programming error? block #3170630438 claimed for no reason in process_bad_block. > Programming error? block #2013802232 claimed for no reason in process_bad_block. > Programming error? block #1648606690 claimed for no reason in process_bad_block. > Programming error? block #3170630438 claimed for no reason in process_bad_block. > Programming error? block #2013802232 claimed for no reason in process_bad_block. > Programming error? block #1648606690 claimed for no reason in process_bad_block. > Programming error? block #3170630438 claimed for no reason in process_bad_block. > Programming error? block #2013802232 claimed for no reason in process_bad_block. > Programming error? block #1648606690 claimed for no reason in process_bad_block. > Programming error? block #3170630438 claimed for no reason in process_bad_block. > Programming error? block #2013802232 claimed for no reason in process_bad_block. > Programming error? block #1648606690 claimed for no reason in process_bad_block. > Programming error? block #3170630438 claimed for no reason in process_bad_block. > Programming error? block #2013802232 claimed for no reason in process_bad_block. > Programming error? block #1648606690 claimed for no reason in process_bad_block. > Programming error? block #3170630438 claimed for no reason in process_bad_block. > Programming error? block #2013802232 claimed for no reason in process_bad_block. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/861281/+subscriptions
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/861281 Title: FSCK on fs with claimed blocks yields Programming Error in process_bad_block To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/861281/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
