Tao Ma wrote:
In resize, we update the global_bitmap first and then the super block.
So if there is any corruption between these 2 steps, there will be a
inconsistence. In kernel we use the information in global_bitmap,
so fsck.ocfs2 should also trust it during the check.
Signed-off-by: Tao Ma <[EMAIL PROTECTED]>
---
Signed-off-by: Sunil Mushran <[EMAIL PROTECTED]>
This looks correct. However, I am still confused as to how I managed to
get clean runs when testing aborted offline resize cases.
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-devel
