ext3 lvm disk Journal has aborted

Hi,

I know it is a bit long, mostly are printout. Thanks for your patient in
advance.
The lvm file system looks corrupt. Then, I try to use fcsk -t ext3
/dev/sdb1,
and I got the error message "Couldn't find ext2 superblock, trying backup
blocks..."
How can I fix it?
I define the file system by mkfs -j. How come the system will see it as
ext2?

Thanks a lot.

From /var/log/messages
faz2 kernel: EXT3-fs error (device dm-2) in start_transaction: Journal has
aborted

pvdisplay
--- Physical volume ---
PV Name /dev/sdb1
VG Name VolGroupFAZ
PV Size 1.99 TB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 521214
Free PE 2168
Allocated PE 519046
PV UUID FHwuBh-mo30-DIAp-8NhA-sHec-0XgI-U39kuL

lvdisplay
--- Logical volume ---
LV Name /dev/VolGroupFAZ/lvol0
VG Name VolGroupFAZ
LV UUID hZGWe6-6l0q-IpDF-iX4x-tS67-ZQJw-4T0jGU
LV Write Access read/write
LV Status available
# open 1
LV Size 1.98 TB
Current LE 519046
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:2

pvdisplay
--- Physical volume ---
PV Name /dev/sdb1
VG Name VolGroupFAZ
PV Size 1.99 TB / not usable 0
Allocatable yes
PE Size (KByte) 4096
Total PE 521214
Free PE 2168
Allocated PE 519046
PV UUID FHwuBh-mo30-DIAp-8NhA-sHec-0XgI-U39kuL

--- Physical volume ---
PV Name /dev/sda2
VG Name VolGroup00
PV Size 67.62 GB / not usable 0
Allocatable yes
PE Size (KByte) 32768
Total PE 2164
Free PE 2
Allocated PE 2162
PV UUID arVsSq-OXkT-ZV4k-PD3h-1dFe-LCYF-vC1Woy

vgdisplay
--- Volume group ---
VG Name VolGroupFAZ
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 2
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 1
Act PV 1
VG Size 1.99 TB
PE Size 4.00 MB
Total PE 521214
Alloc PE / Size 519046 / 1.98 TB
Free PE / Size 2168 / 8.47 GB
VG UUID 7dLMCt-hvvA-v402-JeCK-r8u2-Ev0d-vM21M6

The fs of the lv is built by,
mkfs -j /dev/VolGroupFAZ/lvol0

fsck -t ext3 /dev/sdb1
fsck 1.35 (28-Feb-2004)
e2fsck 1.35 (28-Feb-2004)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to open /dev/sdb1

The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>


.

Relevant Pages

  • Re: Not impressed.
    ... > On ext2 it's relatively easy to corrupt the file system. ... > shut it down ungracefully and there would be corrupt flash files. ... > circumstances should anyone ever run ext2 though, ... I doubt she was running ext2 since Redhat uses ext3 by default. ...
    (alt.os.linux.redhat)
  • Re: Not impressed.
    ... > On ext2 it's relatively easy to corrupt the file system. ... > shut it down ungracefully and there would be corrupt flash files. ... > circumstances should anyone ever run ext2 though, ... I doubt she was running ext2 since Redhat uses ext3 by default. ...
    (linux.redhat)
  • Re: cant mount my root partition (rescue mode)
    ... > in this case it might be a "bad superblock" like it says. ... The file system is appalently too high for this version of e2fsck (or the ... filesystem superblock is corrupt). ...
    (Debian-User)
  • Re: newfs and mount vs. half-baked disks
    ... > clean we just newfs and mount the clean new filesystem. ... > performance hit in updating all superblock copies at the end is small ... since the superblock for the previous file system may ... Newfs should also set the unclean flags and any related flags until it ...
    (freebsd-arch)
  • [PATCH 6/9] exofs: super_operations and file_system_type
    ... This patch ties all operation vectors into a file system superblock ... The next inode number to be allocated ... * struct to hold what we get from mount options ...
    (Linux-Kernel)