EXT4 and fsck problem

[cloneu2]

Power blinked and my battery bakup didn't hold. It messed up a drive that is formated with ext4dev. fsck will not run and i need to fix it. What is out there? I have searched and found nothing..

Tks

[stevea]

READ THE RELEASE NOTES !
"The e2fsprogs userspace tools shipping with Fedora 9 are not yet fully ext4-capable. In particular, fsck ability is limited". So you *may* do better by loading the latestr tools from the ext4 developers.

I assume you didn't put anything important on an ext4 fs yet. Ted T'So the developer of ext4 (and others stuff) has said it is NOT ready for production use - (only experimental). I posted the same on this forum half a dozen times.
http://fedoraproject.org/wiki/FedoraExt4

If not, then realize that lessons learned the hard way are usually learned well.

[SlowJet]

Originally Posted by cloneu2

Power blinked and my battery bakup didn't hold. It messed up a drive that is formated with ext4dev. fsck will not run and i need to fix it. What is out there? I have searched and found nothing..

Tks

I've run EXT4 for months now and have had 3 dramatic power outages from blow transformers to lightening stricks.
Had at least 20 system freezes, reboots for gui hang ups.
But the journal (now checksummed for ext4) has always recovered the file system.

What messages or information are you getting that tells you the file system is messed up?
That would be good to know.

SJ

[leigh123linux]

Here's a srpm you can build ( e2fsprogs-1.41 )


http://www.4shared.com/file/50503814...1-1fc9src.html

[cloneu2]

Thanks for the help. I used Leigh123's program and was able to do some more damage. I booted with the rawhide drive and tried to fix the f9 drive. since it is ext4 it would not mount. So after playing for a while I just said "Oh what the Hell and formatted the thing with ext4dev again. Hate to have to re setup everything BUT I had trashed the lovely KDE with an upgrade to the rawhide version. SO now 1 drive with F9 left STABLE and 1 drive with rawhide to play with.....
enjoy

[mpelletier]

I have had a similar problem after rebuilding initrd. I had to do this to get my ATI HD3650 installed properly. Upon reboot, mount was complaining:

"mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup00-LogVol01,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so"

I did fsck to get the system to boot. Other volumes in the VolGroup00 (also ext4) are working fine now, but LogVol01 will not mount. dmesg | tail reports: "ext4: No journal on filesystem on dm-1"

Is there a way to rebuild the journal? It appears that the data on the drive is still okay.

Any Ideas? All the other forums that I checked did not give much help for this particular problem.