linux-toradex.git/fs/btrfs/delayed-inode.h, branch v3.17-rc2

Btrfs: introduce the delayed inode ref deletion for the single link inode

2014-01-28T21:20:09+00:00

The inode reference item is close to inode item, so we insert it simultaneously
with the inode item insertion when we create a file/directory.. In fact, we also
can handle the inode reference deletion by the same way. So we made this patch to
introduce the delayed inode reference deletion for the single link inode(At most
case, the file doesn't has hard link, so we don't take the hard link into account).

This function is based on the delayed inode mechanism. After applying this patch,
we can reduce the time of the file/directory deletion by ~10%.

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

Btrfs: use flags instead of the bool variants in delayed node

2014-01-28T21:20:08+00:00

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

[readdir] convert btrfs

2013-06-29T08:57:00+00:00

Signed-off-by: Al Viro

Btrfs: improve the delayed inode throttling

2013-03-07T12:52:40+00:00

The delayed inode code batches up changes to the btree in hopes of doing
them in bulk.  As the changes build up, processes kick off worker
threads and wait for them to make progress.

The current code kicks off an async work queue item for each delayed
node, which creates a lot of churn.  It also uses a fixed 1 HZ waiting
period for the throttle, which allows us to build a lot of pending
work and can slow down the commit.

This changes us to watch a sequence counter as it is bumped during the
operations.  We kick off fewer work items and have each work item do
more work.

Signed-off-by: Chris Mason

Btrfs: fix lots of orphan inodes when the space is not enough

2013-02-20T14:36:39+00:00

We're running into having 50-100 orphans left over with xfstests 83
because of ENOSPC when trying to start the transaction for the inode update.
But in fact, it makes no sense in updating the inode for the new size while
we're deleting the stupid thing. This patch fixes this problem.

Reported-by: Josef Bacik 
Signed-off-by: Miao Xie 
Signed-off-by: Josef Bacik

Btrfs: flush delayed inodes if we're short on space

2012-07-23T19:41:40+00:00

Those crazy gentoo guys have been complaining about ENOSPC errors on their
portage volumes.  This is because doing things like untar tends to create
lots of new files which will soak up all the reservation space in the
delayed inodes.  Usually this gets papered over by the fact that we will try
and commit the transaction, however if this happens in the wrong spot or we
choose not to commit the transaction you will be screwed.  So add the
ability to expclitly flush delayed inodes to free up space.  Please test
this out guys to make sure it works since as usual I cannot reproduce.
Thanks,

Signed-off-by: Josef Bacik

Btrfs: destroy the items of the delayed inodes in error handling routine

2012-06-15T15:42:28+00:00

the items of the delayed inodes were forgotten to be freed, this patch
fixes it.

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

atomic: use

2011-07-26T23:49:47+00:00

This allows us to move duplicated code in 
(atomic_inc_not_zero() for now) to 

Signed-off-by: Arun Sharma 
Reviewed-by: Eric Dumazet 
Cc: Ingo Molnar 
Cc: David Miller 
Cc: Eric Dumazet 
Acked-by: Mike Frysinger 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

btrfs: fix inconsonant inode information

2011-06-27T15:34:27+00:00

When iputting the inode, We may leave the delayed nodes if they have some
delayed items that have not been dealt with. So when the inode is read again,
we must look up the relative delayed node, and use the information in it to
initialize the inode. Or we will get inconsonant inode information, it may
cause that the same directory index number is allocated again, and hit the
following oops:

[ 5447.554187] err add delayed dir index item(name: pglog_0.965_0) into the
insertion tree of the delayed node(root id: 262, inode id: 258, errno: -17)
[ 5447.569766] ------------[ cut here ]------------
[ 5447.575361] kernel BUG at fs/btrfs/delayed-inode.c:1301!
[SNIP]
[ 5447.790721] Call Trace:
[ 5447.793191]  [] btrfs_insert_dir_item+0x189/0x1bb [btrfs]
[ 5447.800156]  [] btrfs_add_link+0x12b/0x191 [btrfs]
[ 5447.806517]  [] btrfs_add_nondir+0x31/0x58 [btrfs]
[ 5447.812876]  [] btrfs_create+0xf9/0x197 [btrfs]
[ 5447.818961]  [] vfs_create+0x72/0x92
[ 5447.824090]  [] do_last+0x22c/0x40b
[ 5447.829133]  [] path_openat+0xc0/0x2ef
[ 5447.834438]  [] ? __perf_event_task_sched_out+0x24/0x44
[ 5447.841216]  [] ? perf_event_task_sched_out+0x59/0x67
[ 5447.847846]  [] do_filp_open+0x3d/0x87
[ 5447.853156]  [] ? strncpy_from_user+0x43/0x4d
[ 5447.859072]  [] ? getname_flags+0x2e/0x80
[ 5447.864636]  [] ? do_getname+0x14b/0x173
[ 5447.870112]  [] ? audit_getname+0x16/0x26
[ 5447.875682]  [] ? spin_lock+0xe/0x10
[ 5447.880882]  [] do_sys_open+0x69/0xae
[ 5447.886153]  [] sys_open+0x20/0x22
[ 5447.891114]  [] system_call_fastpath+0x16/0x1b

Fix it by reusing the old delayed node.

Reported-by: Jim Schutt 
Signed-off-by: Miao Xie 
Tested-by: Jim Schutt 
Signed-off-by: Chris Mason

Btrfs: avoid delayed metadata items during commits

2011-06-17T20:38:47+00:00

Snapshot creation has two phases.  One is the initial snapshot setup,
and the second is done during commit, while nobody is allowed to modify
the root we are snapshotting.

The delayed metadata insertion code can break that rule, it does a
delayed inode update on the inode of the parent of the snapshot,
and delayed directory item insertion.

This makes sure to run the pending delayed operations before we
record the snapshot root, which avoids corruptions.

Signed-off-by: Chris Mason