Problems with ext4 on large drive

GigaRoc · 07-09-2009, 04:26 PM

I have a 12.55TB raid 6 drive formated to ext4

It mounted yesterday, this morning, it doesn't.

I've tired a few things, but I can't seem to get it to mount

Code:

>mount /dev/sdb1 /mnt/raid
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
>dmesg | tail
[ 2578.977014] EXT4-fs: bad geometry: block count 3417968063 exceeds size of device (196742591 blocks

and i can't e2fsck

Code:

>e2fsck -f /dev/sda1

e2fsck 1.41.3 (12-Oct-2008)
/dev/sdb1: Invalid argument while reading block 1708687360

/dev/sdb1: Invalid argument reading journal superblock

e2fsck: Invalid argument while checking ext3 journal for /dev/sdb1

here's the tune2fs

Code:

>tune2fs -l /dev/sdb1

tune2fs 1.41.3 (12-Oct-2008)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          08ae474f-4142-4d8a-9cec-4588aba05b53
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash 
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              854499328
Block count:              3417968063
Reserved block count:     170898403
Free blocks:              2994527576
Free inodes:              854492987
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      209
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Sun Jul  5 21:52:02 2009
Last mount time:          Sun Jul  5 22:09:08 2009
Last write time:          Wed Jul  8 20:33:38 2009
Mount count:              1
Maximum mount count:      20
Last checked:             Sun Jul  5 21:52:02 2009
Check interval:           15552000 (6 months)
Next check after:         Fri Jan  1 20:52:02 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:      4a67c0b5-bd40-4061-9e25-c1aac0708a86
Journal backup:           inode blocks

We have over 3 TB's of data on the raid, I really could use some help

Thanks
Kevin

rn_ · 07-10-2009, 09:35 AM

just to be sure it uses the correct fs type, try using fsck.ext4. same result?

GigaRoc · 07-10-2009, 10:00 AM

I updated fsprogs to the newest version and was able to get e2fsck to run.

but i get this error when mounting

Code:

EXT4-fs: bad geometry: block count 3417968063 exceeds size of device (196742591 blocks)

the devices should be around 3417968063 blocks

how to i change the size of device number, resize2fs seems to think it's also 3417968063 blocks

rn_ · 07-10-2009, 02:01 PM

since you have updated e2fsprogs, probably your tune2fs will work now as well. there is a -J parameter to mess with journal options, but dude, this just went beyond my knowledge; if normal fsck doesn't fix it, i wouldn't mess with it; i'd defer it to an expert. do you have backups?