On Fri, Feb 23, 2007 at 09:32:29PM -0500, Theodore Tso wrote: > And having a way of making this list available to both the > filesystem and to a userspace utility, so they can more easily deal > with doing a forced rewrite of the bad sector, after determining > which file is involved and perhaps doing something intelligent (up > to and including automatically requesting a backup system to fetch a > backup version of the file, and if it can be determined that the > file shouldn't have been changed since the last backup, > automatically fixing up the corrupted data block :-). i had a small c program + perl script that would take a badblocks list and figure out which files on an xfs filesystem were trashed, though in the case of xfs it's somewhat easier because you can dump the extents for a file something more generic wouldn't be hard to make work, it also wouldn't be hard to extend this to inodes in some cases though im not sure that there is much you can do there beyond fsck - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
