search for: ext3_check_descriptor

I've got a 3.3TB ext3 on a FC3 64-bit system, running kernel 2.6.10-1.766FC3smp. I create the partition with parted 1.6.21, and I make the fs via: mkfs.ext3 -m1 -b 4096 -T largefile4 /dev/sda1 Works fine. bonnie++ running on it multiple times for days on end, no problems. However, I do the exact same setup on a RHEL4-AS i686 system, 32-bit, and the fs is totally hosed, get all kinds of

Hi! I'm new to the list. I have a problem with mounting my home directory since my PC crashed. I hope that I can get some help on this list as I don't know much of ext3 myself. The mount command for my /home gives me the following output: # mount /dev/sda6 /mnt/tmp/ mount: wrong fs type, bad option, bad superblock on /dev/sda6, missing codepage or other error In some cases useful info

...ready answered before. I'm having this problem; i've got an ext3 8GB partition and it doesn't mount, the cause of this: a user (yes me!) running fsck.ext3 with the filesystem mounted, ups! (snif, forgive me!!, totally newbie and mad) errors while booting: EXT3_fs error (device hda4): ext3_check_descriptors: Blockbitmap for group 0 not in group (block 41471)! EXT3_fs: group descriptors corrupted mount: error 22 mounting ext3flags defaults well, retrying without the options flags and repeats this again twice; then: pivotroot:pivot_root (/sysroot, /sysroot/initrd) failed:2 umont /initrd/sys failed:...

...o 500mb - 1gb still. I don't think it is relevant, but the device itself is /dev/loop0, because there is a cryptoloop layer between the device and the actual /dev/hda3, but i can initiate that layer properly anyway, so it shouldn't matter (should it?). When i try to mount: EXT3-fs error: ext3_check_descriptors: block bitmap for group 0 not in group (block (block 152615462) EXT3-fs: group descriptors corrupted. of course i tried e2fsck (v 1.27), but it said it could not see an ext3 on the partiiton and suggested to try another superblock (here: 8193). hopes surging, but bad luck, because block 8193 is...

...re chances that someone in here might comment on it as well. TIA. * Neil Brown <neilb@cse.unsw.edu.au> [2003-03-20 10:58]: > On Thursday March 20, lists@schlich.org wrote: > > > > And when I try to mount the array: > > --8<-- > > EXT3-fs error (device md(9,1)): ext3_check_descriptors: Block bitmap for group 509 not in group (block 4294967295)! > > EXT3-fs: group descriptors corrupted ! > > --8<-- > > > > What should I do now? Raidhotadd the 4th device? Run e2fsck prior to > > that or afterwards? > > I would > fsck -n /dev/md1 &gt...

Hello all, I just installed a new beta kernel from Dzickus over at redhat. Rebooting causes this, no matter what kernel I boot from: EXT3-fs error: device dm-0: ext3_check_descriptors: Block bitmap for group 5008 not in group (block 167772160)! EXT3-fs: group dexcriptors corrupted! Mount: error mounting /dev/root on /sysroot as ext3: Invalid argument Setuproot: /moving /dev failed: no such file or directory And a bunch of other mounting errors. OK, so, I have a Centos 5.2 in...

...g e2fsck -b 294912 -vvfy /dev/sdj1 (providing backup superblock location ..which I tried several of) I get the following error: Segmentation fault In dmesg, after trying to mount the filesystem, I get the following error: EXT3-fs: group descriptors corrupted ! EXT3-fs error (device sd(8,145)): ext3_check_descriptors: Block bitmap for group 128 not in group (block 523)! Any ideas? Thanks, Barry

...o 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 whil...