[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: ext3 fs errors 3T fs



This is a 64 bit system running a 64 bit kernel.

After reading through the manpage for e2fsck a bit I noticed that mke2fs
can be used to determine additional superblock backups with the -n flag.
Not knowing how the fs was created I assumed that the default blocksize
was used.

terrorbytes:~ # mke2fs -n /dev/md0
mke2fs 1.34 (25-Jul-2003)
warning: 160 blocks unused.

Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
403685856 inodes, 805797888 blocks
40289902 blocks (5.00%) reserved for the super user
First data block=0
24591 block groups
32768 blocks per group, 32768 fragments per group
16416 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208,
        4096000, 7962624, 11239424, 20480000, 23887872, 71663616,
78675968,
        102400000, 214990848, 512000000, 550731776, 644972544


terrorbytes:~ # e2fsck -yb 229376 /dev/md0

The system has now been corecting errors for the past 12 hours.  I hope
when it finishes, it will mount without complaints.

Sincerely,
Dennis Williams

"And for all the good or evil, creation or destruction
your living might have of accomplished, you might have
just never have lived at all"
-From: The Sleeping Beauty

On Wed, 18 Jan 2006, Dennis Williams wrote:

> Hello,
> I looked through the archives a bit and could not find anything relevant,
> if you know otherwise please point me in the right direction.
>
> I have a ~3T ext3 filesystem on linux software raid that had been behaving
> corectly for sometime.  Not to long ago it gave the following error after
> trying to mount it:
>
> mount: wrong fs type, bad option, bad superblock on /dev/md0,
>        or too many mounted file systems
>
> after a long fsck which I had to do manually I noticed the following in
> /var/log/messages after trying to mount again:
>
> Jan 19 09:13:11 terrorbytes kernel: EXT3-fs error (device md0):
> ext3_check_descriptors: Block bitmap for group 3584 not in group (block
> 0)!
> Jan 19 09:13:11 terrorbytes kernel: EXT3-fs: group descriptors corrupted !
>
> when trying to correct again with e2fsck I get this error:
>
> e2fsck 1.34 (25-Jul-2003)
> Group descriptors look bad... trying backup blocks...
> e2fsck: Invalid argument while checking ext3 journal for /dev/md0
>
> some more information on the system:
> os flavor: Suse 9.1
> kernel version: 2.6.5-7.202.7-default (various suse patches applied to
>    2.6.5 kernel)
>
> I am not sure where to go from here, any help, experience, or references
> to documentation that would help me better understand the problem would be
> apreciated.
>
> Sincerely,
> Dennison Williams
>
> "And for all the good or evil, creation or destruction
> your living might have of accomplished, you might have
> just never have lived at all"
> -The Sleeping Beauty
>
> _______________________________________________
> Ext3-users mailing list
> Ext3-users redhat com
> https://www.redhat.com/mailman/listinfo/ext3-users
>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]