e2fsck: Error allocating 1 contiguous block

Help
Bob Kĺre
2005-12-13
2012-11-28
  • Bob Kĺre
    Bob Kĺre
    2005-12-13

    This filesystem is on a LVM, and has been resized at least once with resize2fs without anything seeming to go wrong.

    Recently I plugged the disks into another computer via a SATA-USB adapter, which caused a couple of filesystems to crash for some reason. I was able to save one, but on the other e2fsck says the following:

    e2fsck -v /dev/mapper/vg-datalv
    e2fsck 1.38 (30-Jun-2005)
    /dev/mapper/vg-datalv contains a file system with errors, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Group 4's inode table at 131074 conflicts with some other fs block.
    Relocate<y>? yes

    Group 4's block bitmap at 131072 conflicts with some other fs block.
    Relocate<y>? yes

    Group 4's inode bitmap at 131073 conflicts with some other fs block.
    Relocate<y>? yes

    Group 8's inode table at 262146 conflicts with some other fs block.
    Relocate<y>? yes

    Group 8's block bitmap at 262144 conflicts with some other fs block.
    Relocate<y>? yes

    Group 8's inode bitmap at 262145 conflicts with some other fs block.
    Relocate<y>? yes

    <snip>

    Group 1568's inode table at 51380226 conflicts with some other fs block.
    Relocate<y>? yes

    Group 1568's block bitmap at 51380224 conflicts with some other fs block.
    Relocate<y>? yes

    Group 1568's inode bitmap at 51380225 conflicts with some other fs block.
    Relocate<y>? yes

    Root inode is not a directory.  Clear<y>? yes

    Error allocating 1 contiguous block(s) in block group 4 for block bitmap: Could n
    ot allocate block in ext2 filesystem
    Error allocating 1 contiguous block(s) in block group 4 for inode bitmap: Could n
    ot allocate block in ext2 filesystem
    Error allocating 1 contiguous block(s) in block group 4 for inode table: Could no
    t allocate block in ext2 filesystem
    Error allocating 1 contiguous block(s) in block group 8 for block bitmap: Could n
    ot allocate block in ext2 filesystem

    <snip>

    Error allocating 1 contiguous block(s) in block group 1568 for block bitmap: Could not allocate block in ext2 filesystem
    Error allocating 1 contiguous block(s) in block group 1568 for inode bitmap: Could not allocate block in ext2 filesystem
    Error allocating 1 contiguous block(s) in block group 1568 for inode table: Could not allocate block in ext2 filesystem
    Restarting e2fsck from the beginning...
    /dev/mapper/vg-datalv contains a file system with errors, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Group 4's inode table at 131074 conflicts with some other fs block.
    Relocate<y>?

    This just loops infinitely

     
    • masta
      masta
      2006-01-06

      I have the same problem. Resized an ext3-lv and getting those errors.

      When using the FS, the kernel reports

      EXT3-fs error (device dm-0): ext3_free_blocks_sb: bit already cleared for block 78678357
      Aborting journal on device dm-0.
      EXT3-fs error (device dm-0): ext3_free_blocks_sb: bit already cleared for block 78678359
      EXT3-fs error (device dm-0): ext3_free_blocks_sb: bit already cleared for block 78678362
      EXT3-fs error (device dm-0): ext3_free_blocks_sb: bit already cleared for block 78678364
      .....

      And running fsck.ext2 stucks in a endless loop, always with these errors:

      /dev/vg_data/lvol1 contains a file system with errors, check forced.
      Pass 1: Checking inodes, blocks, and sizes
      Group 2187's inode table at 71663664 conflicts with some other fs block.
      Relocate? yes
      Group 2187's inode table at 71663665 conflicts with some other fs block.
      Relocate? yes
      Group 2187's inode table at 71663666 conflicts with some other fs block.
      Relocate? yes
      Group 2187's inode table at 71663667 conflicts with some other fs block.
      Relocate? yes
      Group 2187's inode table at 71663668 conflicts with some other fs block.
      Relocate? yes
      Group 2187's inode table at 71663669 conflicts with some other fs block.
      Relocate? yes
      Group 2187's inode table at 71663670 conflicts with some other fs block.
      Relocate? yes
      Group 2187's inode table at 71663671 conflicts with some other fs block.
      Relocate? yes
      Group 2187's inode table at 71663672 conflicts with some other fs block.
      Relocate? yes
      Group 2187's inode table at 71663673 conflicts with some other fs block.
      Relocate? yes
      Group 2187's inode table at 71663674 conflicts with some other fs block.
      Relocate? yes
      Group 2187's inode table at 71663675 conflicts with some other fs block.
      Error allocating 512 contiguous block(s) in block group 2187 for inode table: Could not allocate block in ext2 filesystem
      Error allocating 512 contiguous block(s) in block group 3125 for inode table: Could not allocate block in ext2 filesystem
      Restarting e2fsck from the beginning...
      /dev/vg_data/lvol1 contains a file system with errors, check forced.
      Pass 1: Checking inodes, blocks, and sizes

      Is there ANY way to fix this?

      Other people seem to have the same problem:
      http://sourceforge.net/forum/forum.php?thread_id=1280519&forum_id=7053
      http://sourceforge.net/forum/forum.php?thread_id=1234287&forum_id=7053
      http://sourceforge.net/forum/forum.php?thread_id=1191397&forum_id=7053