| commit | 3f6fae9559225741c91f1320090b285da1413290 | |
| author | Shaohua Li <shaohua.li@intel.com> | |
| Thu, 11 Feb 2010 07:43:00 +0000 (11 07:43 +0000) | ||
| committer | Chris Mason <chris.mason@oracle.com> | |
| Fri, 12 Feb 2010 21:47:19 +0000 (12 16:47 -0500) | ||
| tree | 94c1a90aaed740d80cfa701b8c4abad5bbb699df | treesnapshot (tar.gz zip) |
| parent | 23b5c50945f2294add0137799400329c0ebba290 | commitdiff |
Btrfs: btrfs_mark_extent_written uses the wrong slot
My test do: fallocate a big file and do write. The file is 512M, but
after file write is done btrfs-debug-tree shows:
item 6 key (257 EXTENT_DATA 0) itemoff 3516 itemsize 53
extent data disk byte 1103101952 nr 536870912
extent data offset 0 nr 399634432 ram 536870912
extent compression 0
Looks like a regression introducted by
6c7d54ac87f338c479d9729e8392eca3f76e11e1, where we set wrong slot.
Signed-off-by: Shaohua Li <shaohua.li@intel.com>
Acked-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
My test do: fallocate a big file and do write. The file is 512M, but
after file write is done btrfs-debug-tree shows:
item 6 key (257 EXTENT_DATA 0) itemoff 3516 itemsize 53
extent data disk byte 1103101952 nr 536870912
extent data offset 0 nr 399634432 ram 536870912
extent compression 0
Looks like a regression introducted by
6c7d54ac87f338c479d9729e8392eca3f76e11e1, where we set wrong slot.
Signed-off-by: Shaohua Li <shaohua.li@intel.com>
Acked-by: Yan Zheng <zheng.yan@oracle.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>
| fs/btrfs/file.c | diffblobblamehistory |