Hi Reinoud, On Tue, 2013-06-04 at 21:47 +0200, Reinoud Zandijk wrote: > Hi folks, > > would the Linux implementation grock multiple finfo's about one file even with > overlapping blocks ? say a finfo of ino 12345, followed by some finfo's of say > ino 123400, followed by some more of ino 12345? Or does it implicitly assume a > kind of ordering in the blocks? > I suspect that I don't exactly follow your thoughts. But I don't understand about what overlapping blocks you are talking. I have such understanding. Segment summary begins from segment summary header (struct nilfs_segment_summary). This structure has many fields. One of fields is the number of finfo structures in segment summary block. Then, it follows array of file description items after segment summary header. Every file description item begins from struct nilfs_finfo. It defines number of blocks (including intermediate blocks) and number of file data blocks. It follows array of block information items (union nilfs_binfo) after each file information item. So, file describes on block basis. And every file is described by continuous array of union nilfs_binfo items. What do you mean by blocks overlapping? With the best regards, Vyacheslav Dubeyko. -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
