ext3 crash

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

 



>On Apr 02, 2002  22:52 +0900, Andy Paul wrote:
> > One of my shared volumes crashed the other day on a RH-7.2, 2.4.9-31 
>system.
> >
> > These are the first errors in the log:
> >
> > kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in
> > directory #2424833: rec_len is smaller than minimal - offset=0,
> > inode=2553887680, rec_len=0, name_len=0
> >
> > kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in
> > directory #2424833: rec_len is smaller than minimal - offset=0,
> > inode=2553887680, rec_len=0, name_len=0
>
>These errors indicate a read error on the device, I think.
>
> > kernel: attempt to access beyond end of device
> > kernel: 03:09: rw=0, want=558629008, limit=53600841
> >
> >
> > e2fsck complains :
> >
> > e2fsck 1.26 (3-Feb-2002)
> > Group descriptors look bad... trying backup blocks...
> > e2fsck: Attempt to read block from filesystem resulted in short read 
>while
> > checking ext3 journal for /share6
> > e2fsck: io manager magic bad!
>
>Try running "e2fsck -b 32768" or "e2fsck -b 98304".  It may be that
>e2fsck 1.26 already checks all of the possible backup block groups for
>you, but I don't know what version that was added in.

I have tried them with the same result.


>
>You should also try whether "dd if=/dev/hda9" works at all, since it
>seems you have some pretty major problems.

dd, hexdump work properly with the partition. Forgot to mention, the 
partition is (was ?) rather big (40G), used 87%. Is there any ("hard") way 
to recover anything?

Many thanks,
Adrian




_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx





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

  Powered by Linux