Theodore Tso <tytso@xxxxxxx> writes: > > If you are going to store all of the cached objects then you will need > to effectively store *all* of the filesystem metatdata in memory at > the same time. Are you sure about all data? I think he would just need some lookup table from metadata block numbers to inode numbers and then when a hit occurs on a block in the table somehow invalidate all data related to that inode and restart that part. And the same thing for bitmap blocks. That lookup table should be much smaller than the full metadata. Anyways my favourite fsck wish list feature would be a way to record the changes a read-only fsck would want to do and then some quick way to apply them to a writable version of the file system without doing a full rescan. Then you could regularly do a background check and if it finds something wrong just remount and apply the changes quickly. Or perhaps just tell the kernel which objects is suspicious and should be EIOed. -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
