Messages in this thread | | | Subject | Re: Blockbusting news, results are in | From | Valdis.Kletnieks@vt ... | Date | Tue, 21 Oct 2003 16:21:26 -0400 |
| |
On Tue, 21 Oct 2003 16:05:15 EDT, "Richard B. Johnson" said:
> If the respondent wants them isolated into a "BADBLOCKS" file, > he can make a utility to do that. It's really quite easy because > you can raw-read disks under Linux, plus there is already > the `badblocks` program that will locate them.
Yes, it's trivially easy to figure out that block 193453 on /dev/hdb is bad. It's even not too bad to map that to an offset on /dev/hdb4. Even if you're using LVM or DM to map stuff, it's still attackable. But how do you guarantee that block 193453 gets allocated to your badblocks file and not to some other file that just tried to extend itself by 32K?
[unhandled content-type:application/pgp-signature] | |