On Feb 27, 2007 19:02 +0000, Alan wrote: > > It would be great if the app tag was more than 16 bits. Ted mentioned > > that ideally he'd like to store the inode number in the app tag. But > > as it stands there isn't room. > > The lowest few bits are the most important with ext2/ext3 because you > normally lose a sector of inodes which means you've got dangly bits > associated with a sequence of inodes with the same upper bits. More > problematic is losing indirect blocks, and being able to keep some kind > of [inode low bits/block index] would help put stuff back together. In the ext4 extents format there is the ability (not implemented yet) to add some extra information into the extent index blocks (previously referred to as the ext3_extent_tail). This is planned to be a checksum of the index block, and a back-pointer to the inode which is using this extent block. This allows online detection of corrupt index blocks, and also detection of an index block that is written to the wrong location. There is as yet no plan that I'm aware of to have in-filesystem checksums of the extent data. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
