Messages in this thread | | | Date | Tue, 21 Oct 2003 16:31:30 -0400 (EDT) | From | "Richard B. Johnson" <> | Subject | Re: Blockbusting news, results are in |
| |
On Tue, 21 Oct 2003 Valdis.Kletnieks@vt.edu wrote:
> 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? > >
You repair file-systems when they are not mounted. Also, the source of an old version of e2fsprogs has a "defrag" utility that could be used as a sample of how to create a file that owns the bad blocks you find.
Cheers, Dick Johnson Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips). Note 96.31% of all statistics are fiction.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |