help with 2.4.18 oops - sorry was 2.4.16

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

 



Martial Herbaut wrote:
> 
> >
> > Very strange.  Sounds like the metadata for the journal file
> > itself is wrecked.
> >
> > It's the root filesystem - the kernel mounts that itself,
> > so /etc/fstab has no effect.  Look in /proc/mounts and you'll
> > see that it's really mounted by ext3.
> >
> > Try removing the journal altogether:
> >
> >       tune2fs -O ^has_journal /dev/sda2
> >       e2fsck -f /dev/sda2
> >
> > this should convert the filesystem to ext2.  You can then boot
> > with it as ext2, then run `tune2fs -J /dev/sda2' to turn it
> > back to ext3.
> >
> 
> Ok thanks for that, did that and system is back all on ext3.
> we'll see if this permanentely  fixes it or not.
> We had a scsi controller failure so I would say that's when the journal
> got corrupted.
> 

It's a bit odd.  I'm wondering if e2fsck actually checks the
journal file correctly.  Andreas and Ted will know...

-





[Index of Archives]         [Linux RAID]     [Kernel Development]     [Red Hat Install]     [Video 4 Linux]     [Postgresql]     [Fedora]     [Gimp]     [Yosemite News]

  Powered by Linux