linux-toradex.git/fs/btrfs/inode-map.c, branch v3.6.5

Btrfs: show useful info in space reservation tracepoint

2012-03-29T13:57:44+00:00

o For space info, the type of space info is useful for debug.
o For transaction handle, its transid is useful.

Signed-off-by: Liu Bo 
Signed-off-by: Chris Mason

btrfs: replace many BUG_ONs with proper error handling

2012-03-22T10:52:54+00:00

 btrfs currently handles most errors with BUG_ON. This patch is a work-in-
 progress but aims to handle most errors other than internal logic
 errors and ENOMEM more gracefully.

 This iteration prevents most crashes but can run into lockups with
 the page lock on occasion when the timing "works out."

Signed-off-by: Jeff Mahoney

Btrfs: fix compiler warnings on 32 bit systems

2012-02-24T15:39:05+00:00

The enospc tracing code added some interesting uses of
u64 pointer casts.

Signed-off-by: Chris Mason

Btrfs: space leak tracepoints

2012-01-16T20:29:43+00:00

This in addition to a script in my btrfs-tracing tree will help track down space
leaks when we're getting space left over in block groups on umount.  Thanks,

Signed-off-by: Josef Bacik

Btrfs: fix no reserved space for writing out inode cache

2011-11-11T01:45:04+00:00

I-node cache forgets to reserve the space when writing out it. And when
we do some stress test, such as synctest, it will trigger WARN_ON() in
use_block_rsv().

WARNING: at fs/btrfs/extent-tree.c:5718 btrfs_alloc_free_block+0xbf/0x281 [btrfs]()
...
Call Trace:
 [] warn_slowpath_common+0x80/0x98
 [] warn_slowpath_null+0x15/0x17
 [] btrfs_alloc_free_block+0xbf/0x281 [btrfs]
 [] ? __set_page_dirty_nobuffers+0xfe/0x108
 [] __btrfs_cow_block+0x118/0x3b5 [btrfs]
 [] btrfs_cow_block+0x103/0x14e [btrfs]
 [] btrfs_search_slot+0x249/0x6a4 [btrfs]
 [] btrfs_lookup_inode+0x2a/0x8a [btrfs]
 [] btrfs_update_inode+0xaa/0x141 [btrfs]
 [] btrfs_save_ino_cache+0xea/0x202 [btrfs]
 [] ? btrfs_update_reloc_root+0x17e/0x197 [btrfs]
 [] commit_fs_roots+0xaa/0x158 [btrfs]
 [] btrfs_commit_transaction+0x405/0x731 [btrfs]
 [] ? wake_up_bit+0x25/0x25
 [] ? btrfs_log_dentry_safe+0x43/0x51 [btrfs]
 [] btrfs_sync_file+0x16a/0x198 [btrfs]
 [] ? mntput+0x21/0x23
 [] vfs_fsync_range+0x18/0x21
 [] vfs_fsync+0x17/0x19
 [] do_fsync+0x29/0x3e
 [] sys_fsync+0xb/0xf
 [] system_call_fastpath+0x16/0x1b

Sometimes it causes BUG_ON() in the reservation code of the delayed inode
is triggered.

So we must reserve enough space for inode cache.

Note: If we can not reserve the enough space for inode cache, we will
give up writing out it.

Signed-off-by: Miao Xie 
Signed-off-by: Chris Mason

Btrfs: handle enospc accounting for free space inodes

2011-10-19T19:12:42+00:00

Since free space inodes now use normal checksumming we need to make sure to
account for their metadata use.  So reserve metadata space, and then if we fail
to write out the metadata we can just release it, otherwise it will be freed up
when the io completes.  Thanks,

Signed-off-by: Josef Bacik

btrfs: add helper for fs_info->closing

2011-06-04T12:11:22+00:00

wrap checking of filesystem 'closing' flag and fix a few missing memory
barriers.

Signed-off-by: David Sterba

Btrfs: add mount -o inode_cache

2011-06-04T12:03:47+00:00

This makes the inode map cache default to off until we
fix the overflow problem when the free space crcs don't fit
inside a single page.

Signed-off-by: Chris Mason

Btrfs: don't save the inode cache if we are deleting this root

2011-06-04T12:03:45+00:00

With xfstest 254 I can panic the box every time with the inode number caching
stuff on.  This is because we clean the inodes out when we delete the subvolume,
but then we write out the inode cache which adds an inode to the subvolume inode
tree, and then when it gets evicted again the root gets added back on the dead
roots list and is deleted again, so we have a double free.  To stop this from
happening just return 0 if refs is 0 (and we're not the tree root since tree
root always has refs of 0).  With this fix 254 no longer panics.  Thanks,

Signed-off-by: Josef Bacik 
Tested-by: David Sterba 
Signed-off-by: Chris Mason

Btrfs: don't save the inode cache in non-FS roots

2011-06-04T12:03:44+00:00

This adds extra checks to make sure the inode map we are caching really
belongs to a FS root instead of a special relocation tree.  It
prevents crashes during balancing operations.

Signed-off-by: Liu Bo 
Signed-off-by: Chris Mason