Menu ▾ ▴

#308 e2fsck Memory allocation failed

open
nobody
e2fsck (61)
5
2015-02-07
2012-04-19
martin holzer
No

i think i've hit a bug.

i already tried to download the latest stable e2fsprogs, compiled it myself.
but every time i check a 7 TB volume, it crashes.
the filesystem works fine, except i wanna open a special directory.

root@Microknoppix:/tmp/e2fsprogs-1.42.2/e2fsck# ./e2fsck -yvf -C0 /dev/md127
e2fsck 1.42.2 (27-Mar-2012)
Pass 1: Checking inodes, blocks, and sizes
Inode 25722852 has illegal block(s). Clear? yes

Illegal block #1 (4190635500) in inode 25722852. CLEARED.
Illegal block #3 (2469214953) in inode 25722852. CLEARED.
Illegal block #4 (2746471768) in inode 25722852. CLEARED.
Illegal block #5 (3265955755) in inode 25722852. CLEARED.
Illegal block #7 (2870009988) in inode 25722852. CLEARED.
Illegal block #10 (3637016504) in inode 25722852. CLEARED.
Illegal double indirect block (3204513792) in inode 25722852. CLEARED.
Illegal block #136315916 (1950436111) in inode 25722852. CLEARED.
Error storing directory block information (inode=25722852, block=0, num=110317692): Memory allocation failed
e2fsck: aborted

root@Microknoppix:/tmp/e2fsprogs-1.42.2/e2fsck# mdadm --detail /dev/md127
/dev/md127:
Version : 1.1
Creation Time : Fri Apr 9 09:23:35 2010
Raid Level : raid5
Array Size : 7795173120 (7434.06 GiB 7982.26 GB)
Used Dev Size : 1948793280 (1858.51 GiB 1995.56 GB)
Raid Devices : 5
Total Devices : 5
Persistence : Superblock is persistent

Update Time : Thu Apr 19 09:02:14 2012
State : clean
Active Devices : 5
Working Devices : 5
Failed Devices : 0
Spare Devices : 0

Layout : left-symmetric
Chunk Size : 64K

Name : LBG_DISKSTATION:2
UUID : fa71e72b:6a2f6191:b80d7b26:7430548c
Events : 720

Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
1 8 19 1 active sync /dev/sdb3
2 8 35 2 active sync /dev/sdc3
3 8 51 3 active sync /dev/sdd3
5 8 67 4 active sync /dev/sde3
root@Microknoppix:/tmp/e2fsprogs-1.42.2/e2fsck#

Discussion

  • martin holzer

    martin holzer - 2012-04-19
    • labels: --> e2fsck
     

  • martin holzer

    martin holzer - 2012-04-19

    how can i fix this filesystem to get access to the data again

     

  • martin holzer

    martin holzer - 2012-04-19

    the volume was created in a synology ds509+ nas and is a software raid5 with ext3.
    the manufactor already closed the issue with the comment, can't fix the problem, recreate the volume and restore data from backup.

    now i've put the harddisks into a ds1511+ with an intel atom cpu and 3 gb of ram.

    i'm working with knoppix 6.7 (latest) on a usb stick to boot

    root@Microknoppix:/tmp/e2fsprogs-1.42.2/e2fsck# free
    total used free shared buffers cached
    Mem: 3101816 475972 2625844 0 15092 363752
    -/+ buffers/cache: 97128 3004688
    Swap: 16382972 148 16382824

     

  • martin holzer

    martin holzer - 2012-04-19

    i've already tried the following option with no success

    root@Microknoppix:/tmp/git/e2fsprogs/e2fsck# cat /etc/e2fsck.conf
    [scratch_files]
    directory = /mnt-system/var/cache/e2fsck

     

  • Theodore Ts'o

    Theodore Ts'o - 2012-04-19

    Can you send me the output of dumpe2fs /dev/md127? Thanks!!

     

  • martin holzer

    martin holzer - 2012-04-20

    root@Microknoppix:/recover/bilder# dumpe2fs /dev/md127
    dumpe2fs 1.41.12 (17-May-2010)
    Filesystem volume name: 1.41.3-1141
    Last mounted on: <not available>
    Filesystem UUID: 4962adc7-7399-48f3-ba8d-23901f3ad071
    Filesystem magic number: 0xEF53
    Filesystem revision #: 1 (dynamic)
    Filesystem features: has_journal ext_attr resize_inode filetype sparse_super large_file
    Filesystem flags: unsigned_directory_hash
    Default mount options: (none)
    Filesystem state: clean with errors
    Errors behavior: Continue
    Filesystem OS type: Linux
    Inode count: 487202816
    Block count: 1948793280
    Reserved block count: 25600
    Free blocks: 1026652688
    Free inodes: 486981551
    First block: 0
    Block size: 4096
    Fragment size: 4096
    Reserved GDT blocks: 559
    Blocks per group: 32768
    Fragments per group: 32768
    Inodes per group: 8192
    Inode blocks per group: 512
    Filesystem created: Fri Apr 9 09:23:36 2010
    Last mount time: Thu Apr 19 08:19:44 2012
    Last write time: Thu Apr 19 08:22:17 2012
    Mount count: 117
    Maximum mount count: 22
    Last checked: Fri Apr 9 09:23:36 2010
    Check interval: 15552000 (6 months)
    Next check after: Wed Oct 6 09:23:36 2010
    Reserved blocks uid: 0 (user root)
    Reserved blocks gid: 0 (group root)
    First inode: 11
    Inode size: 256
    Required extra isize: 28
    Desired extra isize: 28
    Journal inode: 8
    Default directory hash: half_md4
    Directory Hash Seed: 5c5c4f1d-154a-2c69-3bac-f19140ebb658
    Journal backup: inode blocks
    Journal features: journal_incompat_revoke
    Journal size: 128M
    Journal length: 32768
    Journal sequence: 0x000b2772
    Journal start: 0

     

  • martin holzer

    martin holzer - 2012-04-23

    today is the last time, i can access this device.

    tomorror the volume will be deleted and recreated

     

  • Nobody/Anonymous

    Nobody/Anonymous - 2012-06-02

    Hi there.

    I'm having a very similar problem here.
    The disk I'm trying to repair is a 34GiB LVM partition formated with ext4 that has weirdly become corrupt for the second time.
    Trying to repair it with fsck.ext4 -fvy and also using the scratch dir option never manages to finish yeilding the following error message.

    Error storing directory block information (inode=2020974, block=0, num=12401097): Memory allocation failed
    e2fsck: aborted