similar to: inode cache slows down startup of system

We can just return an error and we''ll bail out properly. We still want to catch this case to make sure we don''t have a bug somewhere, so just warn if this pops up. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> --- fs/btrfs/inode.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 961ae6f..db6e11f

Right now inode cache inode is treated as the same as space cache inode, ie. keep inode in memory till putting super. But this leads to an awkward situation. If we''re going to delete a snapshot/subvolume, btrfs will not actually delete it and return free space, but will add it to dead roots list until the last inode on this snap/subvol being destroyed. Then we''ll fetch deleted

I''ve noticed that: - with x86-64 Fedora 15 DVD install images: - du -sh <ROOT VOLUME> was 36 GB - btrfs df | grep -i data have shown over 40 GB used - without - du -sh <ROOT VOLUME> is 34 GB - btrfs df | grep -i data have shown less then 34 GB used It seems that iso files are considered compressable while they may not be (and penalty is severe - 3x). Regards

Hello, I wanted to make sure that my boot slowdown was related to space_cache so I rebooted the PC several times and it did become slower again. What is more, it doesn''t seem like I even need to generate any actual IO traffic to trigger this. I thought I might give clear_cache a shot again and to test the boot speed with nospace_cache as well. After first booting with

If we get any error while doing a dir index/item lookup in the log tree, we were always unlinking the corresponding inode in the subvolume. It makes sense to unlink only if the lookup failed to find the dir index/item, which corresponds to NULL or -ENOENT, and not when other errors happen (like a transient -ENOMEM or -EIO). Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com> ---

If we fsync, seek and write, rename and then fsync again we will lose the modified hole extent because the rename will drop all of the modified extents since we didn''t do the fast search. We need to only drop the modified extents if we didn''t do the fast search and we were logging the entire inode as we don''t need them anymore, otherwise this is being premature.

Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org> --- fs/btrfs/inode.c | 11 +---------- 1 files changed, 1 insertions(+), 10 deletions(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 4deb280..ae4f64c 100644 --- a/fs/btrfs/inode.c +++ b/fs/btrfs/inode.c @@ -4145,16 +4145,7 @@ static struct inode *btrfs_new_inode(struct btrfs_trans_handle *trans, if (ret != 0) goto

In tree-log.c:replay_one_name(), if memory allocation for the name fails, ensure we iput the dir inode we got before before we return. Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com> --- fs/btrfs/tree-log.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c index ff60d89..6797a93 100644 ---

Hi, I noticed that `df -i` on btrfs returns zero values, much like it does for vfat and - I think I remember - reiser3. It would be nice if btrfs could count the number of inodes on a volume, to get an overview of just how much dust I am collecting. Is it doable? Filesystem Inodes IUsed IFree IUse% Mounted on /dev/loop0 0 0 0 - /lo/kernel2 Jan

Add an option ''s'' to set bufsize in logical to inode transition, then we are able to read all the refs to the logical address. Meanwhile, set a max value 64k for the bufsize. Signed-off-by: Liu Bo <bo.li.liu@oracle.com> --- v2->v3: - use 64k as the upper limit - document command''s options cmds-inspect.c | 23 +++++++++++++++++------ man/btrfs.8.in |

Quiet the following sparse noise: warning: symbol ''btrfs_first_delayed_node'' was not declared. Should it be static? warning: symbol ''btrfs_next_delayed_node'' was not declared. Should it be static? warning: symbol ''btrfs_first_prepared_delayed_node'' was not declared. Should it be static? warning: symbol

When a directory has a default ACL and a subdirectory is created under that directory, btrfs_init_acl() is called when the subdirectory''s inode is created to initialize the inode''s ACL (inherited from the parent directory) but it was clearing the ACL from the inode after setting it if posix_acl_create() returned success, instead of clearing it only if it returned an error. To

Hello insiders is there low level support to change inode ctimes somehow? (on ext[234] it can be done using debugfs) It would be nice to make received snapshots as similar as possible to their send source. (I am not talking about uuids and such, just ls -lc output) creative ideas are welcome, Karl -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body

Even though we allocate more, we should be updating inode i_size as per the arguments passed Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> --- Changes from V1: We should update i_size only if actual_len and cur_offset are both larger than i_size. Otherwise if actual_len is < i_size and cur_offset > i_size we may end up setting wrong i_size value

Hi list, I don''t trust theoretical benchmarks that much and prefer "real-life benchs" on the occasion, so here''s mine: Given 4 laptops, the most powerful of which was running BTRFS and the others ext3 or ext4, all machines running Ubuntu 11.04 Natty 32-bit with a stock Ubuntu 2.6.38-11 kernel, all machines were given the following FS-intensive task : - Upgrade

A user reported getting spammed when moving to 3.0 by this message. Since we switched to the normal checksumming infrastructure all old free space caches will be wrong and need to be regenerated so people are likely to see this message a lot, so ratelimit it so it doesn''t fill up their logs and freak them out. Thanks, Reported-by: Andrew Lutomirski <luto@mit.edu> Signed-off-by:

the tree log recover code expects no free space cached before it executes. Signed-off-by: Yan Zheng <zheng.yan@oracle.com> --- diff -urp 4/fs/btrfs/extent-tree.c 8/fs/btrfs/extent-tree.c --- 4/fs/btrfs/extent-tree.c 2010-05-11 14:15:29.174108554 +0800 +++ 8/fs/btrfs/extent-tree.c 2010-05-11 13:26:38.036107000 +0800 @@ -316,11 +329,6 @@ static int caching_kthread(void *data) if (!path)

This patch makes us cache the extent state we find in find_delalloc_range since we''ll have to lock the extent later on in the function. This will keep us from re-searching for the rang when we try to lock the extent. Signed-off-by: Josef Bacik <josef@redhat.com> --- fs/btrfs/extent_io.c | 11 ++++++++--- 1 files changed, 8 insertions(+), 3 deletions(-) diff --git

Two files in the different subvolumes may have the same inode id, so The rb-tree which is used to manage the defragment object must take it into account. This patch fix this problem. Signed-off-by: Miao Xie <miaox@cn.fujitsu.com> --- fs/btrfs/file.c | 45 +++++++++++++++++++++++++++++++++++---------- 1 files changed, 35 insertions(+), 10 deletions(-) diff --git a/fs/btrfs/file.c

Hi all, I had been clearing the space cache on my btrfs vol (Debian 3.10.11-1 btrfs-tools 2013-7-5) by changing the fstab to "nospace_cache, clear_cache". I ran btrfsck --repair and it said: "cache and super generation don''t match, space cache will be invalidated." Can one of the dev''s please tell me whether that message means that the space cache