Marc - On 31 Jan 2003, Lowell Gilbert wrote:
> Marc Schneiders <[EMAIL PROTECTED]> writes: > > > I have searched Google to find a solution to mark off these two > > blocks/inodes (or however I should call them), so that they will not > > be used anymore. All I found is that this is not possible on > > IDE. It is possible with some types of Linux filesystems (ext2 for one), and 'e2fsck' can be told to run a block-by-block read-write test across the disk (optionally preserving original data where possible), then add any bad blocks to a suitably named file which exists just to keep bad blocks out of circulation. 'apropos badblocks' and 'man fsck' failed to suggest such a function in fBSD, but it might be worth more looking. Such an operation would cost you only those files which are now corrupted - when it happened to me I lost a block in a text file, 'fsck' moved the fragments to 'lost+found', and I was able to reconstruct the file. That was pure luck, naturally. > Why is it radical? After all, IDE disks already do bad-block > remapping internally, so you've built up a *lot* of bad sectors > already if they're starting to become visible to the operating > system... Does fBSD's file system creation make sure that all blocks of a newly created file system are in fact usable? I would be surprised if there were no cross checks in the formatting/partitioning/fs-creation path. If the bad blocks weren't linked in the new filesystem, they would have become invisible for practical purposes. Bad side: This approach wipes the rest of your disk's contents. Maybe there are some starting points in there. - John Mills To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
