From: evansmp@uhura.aston.ac.uk (Mark Evans) Subject: Re: Badblocks revisited (**sigh**) Date: 14 Jul 1992 07:25:37 GMT
hedrick@dartagnan.rutgers.edu (Charles Hedrick) writes:
: duperval@ERE.UMontreal.CA (Duperval Laurent) complains about badblock
: handling.
:
: When I was still using an MFM disk, Linux handled bad blocks on it
: just fine. Maybe the features have gone away?? At that time, there
: was an option to mkfs that would cause it to scan the disk, and put
: any badblocks into a file, which I believe was /.badblocks. That
: a low-tech solution to bad blocks, but it seems reasonable. Ideally
: the bad blocks would be put somewhere that doesn't appear in the
: file system at all, but this would require modifications to both
: the kernel and fsck.
Or rather just to fsck.
Solution make a file unreferenced by any directory, as we are building
a file system from scratch with mkfs, this file can be a know inode.
Then simply have fsck NOT complain about this file having the wrong link
count.
Why modify the kernel?
-- ========================================================================= Mark Evans |evansmp@uhura.aston.ac.uk +(44) 21 565 1979 (Home) |evansmp@cs.aston.ac.uk +(44) 21 359 6531 x4039 (Office) |