similar to: New #btrfs registered on freenode

V2 -> V3: set ''err'' to -ENOMEM when kmalloc() fails. Thanks to Tao. V1 -> V2: Move kmalloc() before mutex_lock(), suggested by Arjan. file_remove_suid() should be called with i_mutex held, file_update_time() too. So move them after mutex_lock(). Plus, check the return value of kmalloc(). Signed-off-by: WANG Cong <amwang@redhat.com> Cc: Arjan

V1 -> V2: Move kmalloc() before mutex_lock(), suggested by Arjan. file_remove_suid() should be called with i_mutex held, file_update_time() too. So move them after mutex_lock(). Plus, check the return value of kmalloc(). Signed-off-by: WANG Cong <amwang@redhat.com> Cc: Arjan <arjan@infradead.org> Cc: Chris Mason <chris.mason@oracle.com> Cc: Yan Zheng

Hello. Sorry for writing to btrfs mailing list, but personal mail reject my message. Saying " <chris.mason@fusionio.com>: host 10.101.1.19[10.101.1.19] said: 554 5.4.6 Hop count exceeded - possible mail loop (in reply to end of DATA command) Final-Recipient: rfc822; chris.mason@fusionio.com Action: failed Status: 5.0.0 Diagnostic-Code: X-Spam-&-Virus-Firewall; host

merge list_for_each and list_entry to list_for_each_entry. Signed-off-by: Qinghuang Feng <qhfeng.kernel@gmail.com> --- diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c index b187b53..70f0248 100644 --- a/fs/btrfs/volumes.c +++ b/fs/btrfs/volumes.c @@ -104,10 +104,8 @@ static noinline struct btrfs_device *__find_device(struct list_head *head, u64 devid, u8 *uuid) { struct

Hello everyone, Btrfs v0.10 is now available for download from: http://oss.oracle.com/projects/btrfs/ Btrfs is still in an early alpha state, and the disk format is not finalized. v0.10 introduces a new disk format, and is not compatible with v0.9. The core of this release is explicit back references for all metadata blocks, data extents, and directory items. These are a crucial building

Hello everyone, Btrfs v0.10 is now available for download from: http://oss.oracle.com/projects/btrfs/ Btrfs is still in an early alpha state, and the disk format is not finalized. v0.10 introduces a new disk format, and is not compatible with v0.9. The core of this release is explicit back references for all metadata blocks, data extents, and directory items. These are a crucial building

Hi all, are there any plans that future versions of mkfs.btrfs will do an initial pre-discard for SSDs? (AFAIK mkfs.btrfs does not do this currently) For Ext4, mke2fs does this with the -E discard option. From the mke2fs manpage: -E discard Attempt to discard blocks at mkfs time (discarding blocks initially is useful on solid state devices and sparse / thin-provisioned storage). When

I''m trying to compile the btrfs source code but I''m getting an error. Any suggestions? Thanks Joe [root@ol6 btrfs-progs]# uname -a Linux ol6.localdomain 2.6.39-400.17.2.el6uek.x86_64 #1 SMP Wed Mar 13 12:31:05 PDT 2013 x86_64 x86_64 x86_64 GNU/Linux [root@ol6 src]# git clone git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-progs.git Initialized empty Git repository in

I found userspace tool, btrfsctl, uses BTRFS_VOL_NAME_MAX, and it also looks that this one is more proper. Kill BTRFS_PATH_NAME_MAX since no one will use it. Signed-off-by: WANG Cong <wangcong@zeuux.org> Cc: Chris Mason <chris.mason@oracle.com> --- diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c index c2aa33e..f229950 100644 --- a/fs/btrfs/ioctl.c +++ b/fs/btrfs/ioctl.c @@ -472,7

These are all the cases where a variable is set, but not read which are really bugs. - Couple of incorrect error handling fixed. - One incorrect use of a allocation policy - Some other things Still needs more review. Found by gcc 4.6''s new warnings Cc: chris.mason@oracle.com cc: linux-btrfs@vger.kernel.org Signed-off-by: Andi Kleen <ak@linux.intel.com> ---

I''m using btrfs on two devices here, /usr on sda3 and /home on sdb (dm-crypt device on the whole disk). With btrfs-master the whole system hangs when accessing /home. The system hangs when I''m logging in into my account with KDE and is easily reproducible with dbench. On /usr the hangs appeared also but not as often as on the /home-device. I''ve tested on a third

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

I was playing around with btrfs, and did a mkfs.btrfs on one of my partition. Mistakes, it was my data partition (ext3 based). I have not yet mounted the device, but the mkfs.btrfs continued to completion. Is it possible to salvage my ext3 filesystem? Anyway to reverse the effect of mkfs.btrfs? Thank you for your help/answer. -- Regards, Peter Teoh

There''s no need to preserve this abstraction; it used to let us use hardware crc32c support directly, but libcrc32c now does that for us through the crypto API -- so we''re already using the Intel crc32c acceleration where appropriate, without having to do anything special. As is right and proper. Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> ---

tree: git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git master head: 0cb8658e96f1ba2ff2d730224cb31e231edd318d commit: 7017ac470ed5b029bc683883714a7f4a4ed34c33 Btrfs: move some common code into a subfunction date: 2 days ago config: make ARCH=x86_64 allyesconfig All warnings: fs/btrfs/volumes.c: In function ''btrfs_rm_device'': fs/btrfs/volumes.c:1505:1:

Hello, I''m using kernel 3.1.0 and I have both / and /home as btrfs. I used suspend to ram quite often and never had a problem, but yesterday I''ve suspended to get into a plane and when I resumed my /home was all about input/output errors. Reboot did not help either. My root (/) did not suffer any problems. Today I''ve upgraded btrfs-progs to latest GIT and tried scrub

Hi everyone, The master branch of the btrfs unstable tree: git://git.kernel.org/pub/scm/linux/kernel/git/mason/btrfs-unstable.git master Has a collection of btrfs bug fixes. The three most important fixes here address crashes in the btrfs O_DIRECT code, add a migrate_page operation to avoid metadata corruption as btree pages go through migration, and fix up our NFS support. Otherwise we have

Hi, I try to format a USB memory with a Btrfs. I can format it with mkfs.btrfs without problems. But; when I try to mount it, it fails to mount with the below error messages. But the USB memory works fine with other filesystems (ext4, XFS etc.). So, the hardware is not faulty. tarkane@tarkane:~$ sudo mkfs.btrfs -d single -n 4096 /dev/sdb1 WARNING! - Btrfs v0.18-26-g0030f1d IS EXPERIMENTAL

From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> The pdflush thread is long gone, so this patch removes references to pdflush from btrfs comments. Cc: Chris Mason <chris.mason@fusionio.com> Cc: linux-btrfs@vger.kernel.org Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> --- I expect this patch to be merged via Al Viro''s VFS tree.

This reverts commit 5500cdbe14d7435e04f66ff3cfb8ecd8b8e44ebf. We had numerous reports of premature ENOSPC that were bisected to this patch. Reverting will not break things but a warning in ''use_block_rsv'' may show up in the syslog. There''s no alternative fix in sight and the ENOSPC problem affects all 3.3 btrfs users during normal filesystem use. CC: