Btrfs: Update the highest objectid in a root after log replay is done

[linux-2.6-omap-h63xx.git] / fs / btrfs / btrfs_inode.h

diff --git a/fs/btrfs/btrfs_inode.h b/fs/btrfs/btrfs_inode.h
index 534ac4153ddd08f45bb207510d8be65871fc80b7..fcc8cf27e906c8d865ecb08f8e353ae181656207 100644 (file)
--- a/fs/btrfs/btrfs_inode.h
+++ b/fs/btrfs/btrfs_inode.h
@@ -33,6 +33,7 @@ struct btrfs_inode {
        struct extent_io_tree io_failure_tree;
        struct mutex csum_mutex;
        struct mutex extent_mutex;
+       struct mutex log_mutex;
        struct inode vfs_inode;
        struct btrfs_ordered_inode_tree ordered_tree;
 
@@ -44,10 +45,17 @@ struct btrfs_inode {
 
        struct list_head delalloc_inodes;
 
+       /* full 64 bit generation number */
+       u64 generation;
+
        /*
         * transid of the trans_handle that last modified this inode
         */
        u64 last_trans;
+       /*
+        * transid that last logged this inode
+        */
+       u64 logged_trans;
        u64 delalloc_bytes;
        u64 disk_i_size;
        u32 flags;
@@ -57,15 +65,6 @@ struct btrfs_inode {
         * number for new files that are created
         */
        u64 index_cnt;
-
-       /*
-        * index holds the directory index for this inode on creation, so
-        * add_link can do what its supposed to.  This isn't populated when the
-        * inode is read because there isn't really a reason to know this unless
-        * we are creating the directory index or deleting it, and deletion
-        * reads the index off of the inode reference at unlink time.
-        */
-       u64 index;
 };
 
 static inline struct btrfs_inode *BTRFS_I(struct inode *inode)