Tux3: the other next-generation filesystem

Posted Dec 11, 2008 6:42 UTC (Thu) by daniel (guest, #3181)
In reply to: Tux3: the other next-generation filesystem by joern
Parent article: Tux3: the other next-generation filesystem

How do you deal with inode->i_size and inode->i_blocks changing on behalf of the "promise"?

These are updated with the inode table block and not affected by promises. Note that we can sometimes infer the i_size and i_blocks changes from the logical positions of the written data blocks and could defer inode table block udpates until rollup time. And in the cases where we can't infer it, write the i_size into the log commit block. More optimization fun.