> snaphot was taken. Even if it has been remounted read-only at this > point, this gets really dicey. Consider that with certain types of > corruption, if the filesystem continues to get modified, the > corruption can get worse. I see, but perhaps you could do that on at least some common type of corruptions and only give up in the extreme cases? Mind you I don't have a good feeling what common and uncommon types are. > > > Or perhaps just tell the kernel which objects is suspicious and > > should be EIOed. > > Yeah; you could do that, as long as it's not a guarantee that all of > the objects which were suspicious were found. It would also be Ok to do the 100% job you probably need metadata checksums and always validate on initial read. -Andi -- 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
