lkml.org 
[lkml]   [1999]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: Massive e2fs corruption with 2.2.9/10?
On Thu, Jun 17, 1999 at 02:30:51PM +0200, Harald Koenig wrote:
> two times I got strange ext2fs errors -- there was a duplicate block
> both times. for the 2nd error I kept the fsck log:
>
> Duplicate blocks found... invoking duplicate block passes.
> Pass 1B: Rescan for duplicate/bad blocks
> Duplicate/bad block(s) in inode 196693: 787271

I have seen different messages when trying to recover. all data was lost
(converted to inode numbers in lost+found). Next time, I'll also try to save
the logs.

> did you change your hardware [settings?] recently ?

at least, I did not. I also have found that a few dir entries in the at that
time mounted msdos filesystems on the same disk was affected as well. It
contained invalid filenames that was not shown when 'DIR' was entered but
the subdirectory wasn't empty. Could not be cleared with del, or linux rm or
whatever.

I finally fixed it by editing the entries in the FAT.

anyways, 2.2.10 to date is still OK <knock on wood> but it does give me a
bad feeling.


Roeland

--
Grobbebol's Home | Don't give in to spammers.
http://www.xs4all.nl/~bengel | Use your real e-mail address
Linux 2.0.34 on an i586/64 MB | on Usenet.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:52    [W:0.124 / U:0.108 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site