lkml.org 
[lkml]   [1998]   [Nov]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.1.126: Possible bug in fschk/corrupted inode handling

Hello All,

On Mon, 2 Nov 1998, Alan Cox wrote:
> > Again running
> > e2fsck /dev/sda2
> > Produces the same read error from the same bad block and the same sound.
> > Hmmm...
> > I thought the -c option and the entry
> > of the badblock would avoid further reading?!
> e2fsck rechecks bad blocks.
> > And -- if so -- how can I avoid further reading from this defect block, possibly
> > WITHOUT reformatting the disk, cause it is my root device and therefore
> > the prrof of Murphy's law.
> Ideally you want to do a scsi verify - thats in most SCSI bios. That makes
> the drive itself do a complete check and bad block remap

Uhhh, Always remember low-level Verifies can/will/always
wipe the data off the disk. So back up first ...

Hth, JimL
+-----------------------------------------------------------------------+
| James W. Laferriere - Network Engineer - babydr@baby-dragons.com |
| System Techniques - 25416 - 22nd S. - Des-Moines, WA 98198 |
| Give me VMS -or- Give me Linux -but- only on AXP |
+-----------------------------------------------------------------------+

-
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:45    [from the cache]
©2003-2011 Jasper Spaans