At 2004-08-08T16:28:16+1200, Volker Kuhlmann wrote:
> You misunderstood. I want to leave the faulty part in the file, but
> remove the space around so I can use that elsewhere. Obviously copying
> is not an option. Data recovery is a non-issue (the whole file was an
> on-disk copy of a DVD). Yes there is badblock handling.
You already know the LBA of the bad block(s). Add them to the
filesystem's bad block list. Given you're a SuSE user, you're probably
using reiserfs, so read the man page for reiserfstune and look for the
'-b' option--there's also a bunch of information about this in the
ReiserFS FAQ at the Namesys website. Alternatively, use dd to write to
the bad block(s) and that will probably force the drive to perform a
sector reallocation.
> Incidentally, I don't think that much of the badblocks program. They all
> can't really work properly. I ran it with -w and it didn't find
> anything. Yet, if I deliberately read certain blocks, the kernel keeps
> on reporting
Are you sure you're initiating badblocks with the correct parameters?
It seems strange that it would not find the same errors given that your
test and badblocks will be doing effectively the same thing at the
system call level... it could also be a bug, I guess.
> If badblocks reports failures you know you have a problem - if it
> reports nothing, it doesn't mean a hell of a lot.
Yes, this is worth noting, and it's true of every piece of software that
tries to perform a similar task, e.g. memtest86.
-mjg
--
Matthew Gregan |/
/| [EMAIL PROTECTED]
