fsck won't fix filesystem after resize2fs

Help
2004-12-07
2012-11-28
  • George Greer

    George Greer - 2004-12-07

    e2fsck -fv /dev/md0
    e2fsck 1.35 (28-Feb-2004)
    Pass 1: Checking inodes, blocks, and sizes
    Group 0's inode table at 1057 conflicts with some other fs block.
    Group 0's inode table at 1058 conflicts with some other fs block.
    Group 0's inode table at 1059 conflicts with some other fs block.
    Group 0's inode table at 1060 conflicts with some other fs block.
    Group 0's block bitmap at 1055 conflicts with some other fs block.
    Group 0's inode bitmap at 1056 conflicts with some other fs block.
    Group 1's inode table at 33825 conflicts with some other fs block.
    Group 1's inode table at 33826 conflicts with some other fs block.
    Group 1's inode table at 33827 conflicts with some other fs block.
    Group 1's inode table at 33828 conflicts with some other fs block.
    Group 1's block bitmap at 33823 conflicts with some other fs block.
    Group 1's inode bitmap at 33824 conflicts with some other fs block.
    Group 3's inode table at 99361 conflicts with some other fs block.
    Group 3's inode table at 99362 conflicts with some other fs block.
    Group 3's inode table at 99363 conflicts with some other fs block.
    Group 3's inode table at 99364 conflicts with some other fs block.
    Group 3's block bitmap at 99359 conflicts with some other fs block.
    Group 3's inode bitmap at 99360 conflicts with some other fs block.
    Group 5's inode table at 164897 conflicts with some other fs block.
    Group 5's inode table at 164898 conflicts with some other fs block.
    Group 5's inode table at 164899 conflicts with some other fs block.
    Group 5's inode table at 164900 conflicts with some other fs block.
    Group 5's block bitmap at 164895 conflicts with some other fs block.
    Group 5's inode bitmap at 164896 conflicts with some other fs block.
    Group 7's inode table at 230433 conflicts with some other fs block.
    Group 7's inode table at 230434 conflicts with some other fs block.
    Group 7's inode table at 230435 conflicts with some other fs block.
    Group 7's inode table at 230436 conflicts with some other fs block.
    Group 7's block bitmap at 230431 conflicts with some other fs block.
    Group 7's inode bitmap at 230432 conflicts with some other fs block.
    Group 125's inode table at 4097055 conflicts with some other fs block.
    Group 125's inode table at 4097056 conflicts with some other fs block.
    Group 125's inode table at 4097057 conflicts with some other fs block.
    Group 125's inode table at 4097058 conflicts with some other fs block.
    Group 243's inode table at 7963679 conflicts with some other fs block.
    Group 243's inode table at 7963680 conflicts with some other fs block.
    Group 243's inode table at 7963681 conflicts with some other fs block.
    Group 243's inode table at 7963682 conflicts with some other fs block.
    Group 343's inode table at 11240479 conflicts with some other fs block.
    Group 343's inode table at 11240480 conflicts with some other fs block.
    Group 343's inode table at 11240481 conflicts with some other fs block.
    Group 343's inode table at 11240482 conflicts with some other fs block.
    Group 2187's inode table at 71664671 conflicts with some other fs block.
    Group 2187's inode table at 71664672 conflicts with some other fs block.
    Group 2187's inode table at 71664673 conflicts with some other fs block.
    Group 2187's inode table at 71664674 conflicts with some other fs block.
    Group 2401's inode table at 78677023 conflicts with some other fs block.
    Group 2401's inode table at 78677024 conflicts with some other fs block.
    Group 2401's inode table at 78677025 conflicts with some other fs block.
    Group 2401's inode table at 78677026 conflicts with some other fs block.
    Group 3125's inode table at 102401055 conflicts with some other fs block.
    Group 3125's inode table at 102401056 conflicts with some other fs block.
    Group 3125's inode table at 102401057 conflicts with some other fs block.
    Group 3125's inode table at 102401058 conflicts with some other fs block.
    Error allocating 1 contiguous block(s) in block group 0 for block bitmap: Could not allocate block in ext2 filesystem
    Error allocating 1 contiguous block(s) in block group 0 for inode bitmap: Could not allocate block in ext2 filesystem
    Error allocating 4 contiguous block(s) in block group 0 for inode table: Could not allocate block in ext2 filesystem
    Error allocating 1 contiguous block(s) in block group 1 for block bitmap: Could not allocate block in ext2 filesystem
    Error allocating 1 contiguous block(s) in block group 1 for inode bitmap: Could not allocate block in ext2 filesystem
    Error allocating 4 contiguous block(s) in block group 1 for inode table: Could not allocate block in ext2 filesystem
    Error allocating 1 contiguous block(s) in block group 3 for block bitmap: Could not allocate block in ext2 filesystem
    Error allocating 1 contiguous block(s) in block group 3 for inode bitmap: Could not allocate block in ext2 filesystem
    Error allocating 4 contiguous block(s) in block group 3 for inode table: Could not allocate block in ext2 filesystem
    Error allocating 1 contiguous block(s) in block group 5 for block bitmap: Could not allocate block in ext2 filesystem
    Error allocating 1 contiguous block(s) in block group 5 for inode bitmap: Could not allocate block in ext2 filesystem
    Error allocating 4 contiguous block(s) in block group 5 for inode table: Could not allocate block in ext2 filesystem
    Error allocating 1 contiguous block(s) in block group 7 for block bitmap: Could not allocate block in ext2 filesystem
    Error allocating 1 contiguous block(s) in block group 7 for inode bitmap: Could not allocate block in ext2 filesystem
    Error allocating 4 contiguous block(s) in block group 7 for inode table: Could not allocate block in ext2 filesystem
    Error allocating 4 contiguous block(s) in block group 125 for inode table: Could not allocate block in ext2 filesystem
    Error allocating 4 contiguous block(s) in block group 243 for inode table: Could not allocate block in ext2 filesystem
    Error allocating 4 contiguous block(s) in block group 343 for inode table: Could not allocate block in ext2 filesystem
    Error allocating 4 contiguous block(s) in block group 2187 for inode table: Could not allocate block in ext2 filesystem
    Error allocating 4 contiguous block(s) in block group 2401 for inode table: Could not allocate block in ext2 filesystem
    Error allocating 4 contiguous block(s) in block group 3125 for inode table: Could not allocate block in ext2 filesystem
    Restarting e2fsck from the beginning...

    Repeat ad nauseum.

    The filesystem in question was expanded from ~500GB (3x 250GB RAID5) to ~1000GB (5x 250GB RAID5) without error from resize2fs (Fedora Core 3 release). The files on the filesystem are verified intact (via checksums) but I haven't written anything extra to the disk myself since then either.

        3753 inodes used (0%)
         560 non-contiguous inodes (14.9%)
             # of inodes with ind/dind/tind blocks: 3374/2732/0
    111097077 blocks used (45%)
           0 bad blocks
           1 large file

        3511 regular files
         233 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
    --------
        3744 files

    Prior to resize:

    e2fsck -f /dev/md0
    e2fsck 1.35 (28-Feb-2004)
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    /dev/md0: 3753/478848 files (14.9% non-contiguous), 111073350/122555776 blocks

    The resize itself:

    resize2fs -p /dev/md0
    resize2fs 1.35 (28-Feb-2004)
    Resizing the filesystem on /dev/md0 to 245111552 (4k) blocks.
    Begin pass 1 (max = 3740)
    Extending the inode table     XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    Begin pass 2 (max = 522)
    Relocating blocks             XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    Begin pass 3 (max = 3741)
    Scanning inode table          XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
    The filesystem on /dev/md0 is now 245111552 blocks long.

    The only thing fsck has managed to "fix", was:
    Duplicate blocks found... invoking duplicate block passes.
    Pass 1B: Rescan for duplicate/bad blocks
    Duplicate/bad block(s) in inode 2: 1061
    Duplicate/bad block(s) in inode 7: 1066
    Duplicate/bad block(s) in inode 8: 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083
    Duplicate/bad block(s) in inode 11: 1062 1063 1064 1065
    Duplicate/bad block(s) in inode 15490: 4097064 4097065 4097066 4097067 4097068 4097069 4097070 4097071 4097072 4097073 4097074 4097075 4097076 4097077 4097078 4097079 4097080 4097081 4097082 4097083
    Duplicate/bad block(s) in inode 15491: 4097059 4097060 4097061 4097062 4097063
    Duplicate/bad block(s) in inode 16839: 7963683 7963684 7963685 7963686 7963687 7963688 7963689 7963690 7963691 7963692 7963693 7963694 7963695 7963696 7963697 7963698 7963699 7963700 7963701 7963702 7963703 7963704 7963705 7963706 7963707
    Duplicate/bad block(s) in inode 16884: 11240488 11240489 11240490 11240491 11240492 11240493 11240494 11240495 11240496 11240497 11240498 11240499 11240500 11240501 11240502 11240503 11240504 11240505 11240506 11240507
    Duplicate/bad block(s) in inode 16885: 11240483 11240484 11240485 11240486 11240487
    Duplicate/bad block(s) in inode 274842: 71664680 71664681 71664682 71664683 71664684 71664685 71664686 71664687 71664688 71664689 71664690 71664691 71664692 71664693 71664694 71664695 71664696 71664697 71664698 71664699
    Duplicate/bad block(s) in inode 274843: 71664675 71664676 71664677 71664678 71664679
    Duplicate/bad block(s) in inode 300202: 78677032 78677033 78677034 78677035 78677036 78677037 78677038 78677039 78677040 78677041 78677042 78677043 78677044 78677045 78677046 78677047 78677048 78677049 78677050 78677051
    Duplicate/bad block(s) in inode 300203: 78677027 78677028 78677029 78677030 78677031
    Duplicate/bad block(s) in inode 358734: 102401064 102401065 102401066 102401067 102401068 102401069 102401070 102401071 102401072 102401073 102401074 102401075 102401076 102401077 102401078 102401079 102401080 102401081 102401082 102401083
    Duplicate/bad block(s) in inode 358735: 102401059 102401060 102401061 102401062 102401063
    Duplicate/bad block(s) in inode 476810: 33829 33830 33831 33832 33833 33834 33835 33836 33837 33838 33839 33840 33841 33842 33843 33844 33845 33846 33847 33848 33849 33850 33851
    Duplicate/bad block(s) in inode 476811: 99368 99369 99370 99371 99372 99373 99374 99375 99376 99377 99378 99379 99380 99381 99382 99383 99384 99385 99386 99387
    Duplicate/bad block(s) in inode 476812: 99365 99366 99367 164904 164905 164906 164907 164908 164909 164910 164911 164912 164913 164914 164915 164916 164917 164918 164919 164920 164921 164922 164923
    Duplicate/bad block(s) in inode 476813: 164901 164902 164903 230440 230441 230442 230443 230444 230445 230446 230447 230448 230449 230450 230451 230452 230453 230454 230455 230456 230457 230458 230459
    Duplicate/bad block(s) in inode 476814: 230437 230438 230439
    Pass 1C: Scan directories for inodes with dup blocks.
    Pass 1D: Reconciling duplicate blocks
    (There are 18 inodes containing duplicate/bad blocks.)

    File / (inode #2, mod time Sun Dec  5 11:08:14 2004)
      has 1 duplicate block(s), shared with 0 file(s):
    Duplicated blocks already reassigned or cloned.

    File <The group descriptor inode> (inode #7, mod time Sun Nov 21 12:48:00 2004)
      has 1 duplicate block(s), shared with 0 file(s):
    Duplicated blocks already reassigned or cloned.

    File <The journal inode> (inode #8, mod time Sun Nov 21 12:48:00 2004)
      has 17 duplicate block(s), shared with 0 file(s):
    Duplicated blocks already reassigned or cloned.

    File /lost+found (inode #11, mod time Sun Nov 21 12:48:00 2004)
      has 4 duplicate block(s), shared with 0 file(s):
    Duplicated blocks already reassigned or cloned.

    (...etc..., all having "duplicates" already reassigned.)

    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    Block bitmap differences:  -(276360--276881) +(295973--296001) +(820259--820287) +(885795--885823) +(1606691--1606719) +(2655267--2655295) +(20481059--20481087) +(23888931--23888959) +(214990914--214991937)
    Fix<y>? yes

    Free blocks count wrong for group #8 (18030, counted=18552).
    Fix<y>? yes

    Free blocks count wrong for group #9 (31707, counted=31678).
    Fix<y>? yes

    Free blocks count wrong for group #25 (31707, counted=31678).
    Fix<y>? yes

    Free blocks count wrong for group #27 (31707, counted=31678).
    Fix<y>? yes

    Free blocks count wrong for group #49 (31707, counted=31678).
    Fix<y>? yes

    Free blocks count wrong for group #81 (31707, counted=31678).
    Fix<y>? yes

    Free blocks count wrong for group #625 (31707, counted=31678).
    Fix<y>? yes

    Free blocks count wrong for group #729 (31707, counted=31678).
    Fix<y>? yes

    Free blocks count wrong for group #6561 (32702, counted=31678).
    Fix<y>? yes

    Free blocks count wrong (134015180, counted=134014475).
    Fix<y>? yes

    Then it prints out the file system summary I pasted above.

    Unfortunately, I don't have sufficient space elsewhere to copy everything and re-run mke2fs.

    (Maybe I should be asking the mailing list instead of this forum?)

    -George Greer

     
    • Theodore Ts'o

      Theodore Ts'o - 2005-01-19

      You're using the Fedora version of e2fsprogs, which was buggy.  Please try e2fsprogs 1.36-rc3; that should fix your problems.  (Sorry if I've replied to you already)

       

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks