similar to: patchwork

Hello Josef, Could you please pull these patches: https://patchwork.kernel.org/patch/2192901/ https://patchwork.kernel.org/patch/2192911/ https://patchwork.kernel.org/patch/2192921/ The first one is definitely a bug that needs to be fixed, the second one is to remove unnecessary BUG_ON, the last one is a clean up.. Is there any problems with these patches? Please let me know.. Thanks,

Hi. petrb@bots-bnr1:/mnt$ btrfs subvolume delete ext2_saved/ Delete subvolume ''/mnt/ext2_saved'' ERROR: cannot delete ''/mnt/ext2_saved'' this is not really very descriptive. It would be really cool if it told me why it can''t delete it. For example: Permission denied. Cannot delete ... Disk write error. Cannot delete Descriptive error messages

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

Hi, Will btrfs/oracle mentor students for this year''s "Google Summer of Code 2011"? I would like to work on a Windows-IFS driver which uses coLinux as a "backend" - and therefor support all Filesystems the Linux kernel has drivers for. Although not as cool as a native btrfs driver for windows, in the long term this could be even more profitable for btrfs - without

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

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

I''ve enabled "extended inode refs" and "skinny metadata extent refs" with btrfstune. Then, I''ve tried running "btrfs filesystem balance" - unfortunately it segfaulted. (not sure if I should run balance operation after using btrfstune with -r and -x)? This is with 3.10 kernel with "Btrfs: make backref walking code handle skinny metadata"

Hello, Per David''s comments upon v6, I missed a check up against the return value of btrfs_end_transaction for btrfs_ioctl_fs_setlabel(), it was fixed in this version. v7->v6: - take care of btrfs_end_transaction() in btrfs_ioctl_fs_setlabel() rather than keeping silence. The old versions can be found at: v6: http://www.spinics.net/lists/linux-btrfs/msg20922.html v5:

It seems that the BTRFS_IOC_CLONE ioctl fails when trying to do a cross-subvolume clone of a file. Chris Mason suggested in the past ([1]) that this should be possible. Am I missing something? [1] http://kerneltrap.org/mailarchive/linux-btrfs/2010/6/10/6884911 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to

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

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

Hi Everyone, I am very new to this mailing list and very much interested in getting into the internals of BTRFS file system I was looking for mkfs.btrfs source code so that I can start getting how the disk is formatted with btrfs system. Can anyone of you redirect me to that place to download the btrfsprogs source code. Thanks in advance. Debasish -- To unsubscribe from this list: send the

HI all, >----Messaggio originale---- >Da: chris.mason@fusionio.com >Data: 20/06/2012 1.49 >A: "H. Peter Anvin"<hpa@zytor.com> >Cc: "linux-btrfs@vger.kernel.org"<linux-btrfs@vger.kernel.org> >Ogg: Re: Subvolumes and /proc/self/mountinfo > >> b. Are there better ways (walking the tree using BTRFS_IOC_TREE_SEARCH?) >> to accomplish

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:

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

Hi, I scrubbed a BTRFS volume (mounted as a VFS root) and got several errors. However I am not able to make btrfs print the path of the corrupted files... E.g. kernel log gives : [51078.682876] btrfs: unable to fixup (regular) error at logical 51241746432 on dev /dev/root [51078.683013] btrfs: checksum error at logical 51242385408 on dev /dev/root, sector 102196320, root 684, inode 60676040,

Hello everyone, As Linus discovered, the new btrfs disk format in 2.6.31-git can be problematic if your FS gets forward rolled to the new format and you end up bisecting back to the old code. It would also be nice to have a way to run btrfsck on a root filesystem and do other assorted tasks. So, I''m making live boot usb images for both x86 and x86-64. They should have enough to get

A couple of weeks ago it was mentioned that btrfs in the stand alone tree would be patched to support 2.6.27 with older versions coming after. Has anyone actually done these patches? I''d like to get btrfs running on 2.6.26(Debian Lenny kernel) and if no one has done any code towards it I''d be happy to do it. Lee -- To unsubscribe from this list: send the line "unsubscribe

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

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> ---