Re: hang on 3.9, 3.10-rc5

Hi Chris, On Tue, 18 Jun 2013, Chris Mason wrote: > [...] > Very long way of saying I think we're one release_path short. Sage, I > haven't tested this at all yet, I was hoping to trigger it first. > > diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c > index c276ac9..c1954b3 100644 > --- a

Re: csum failed during rebalance

On Jun 19, 2013, at 5:55 PM, John Haller wrote: > > It appears that devid 1 was never balanced. Note that the drive > numbers are different because I still have the backup device connected > which had the originals of corrupted files. The filesystem started > with devid 1, was filled to the abov

Re: csum failed during rebalance

On Sun, Jun 2, 2013 at 9:05 PM, John Haller wrote: > Hi, > > I added a new drive to an existing RAID 0 array. Every > attempt to rebalance the array fails: > # btrfs filesystem balance /share/bd8 > ERROR: error during balancing '/share/bd8' - Input/output error > # dmesg | tail > btrfs: found 1 ex

Re: BUG at fs/btrfs/print-tree when trying to mount after a crash

Hi, here's an update on my situation. On Tue, 2013-06-18 at 14:11 +0200, Michael Zugelder wrote: > Anyway, I tried using btrfsck from Josef Bacik's tree (commit f392a28d, > git://github.com/josefbacik/btrfs-progs.git) and it doesn't crash. > Output is this: > > > Checking filesystem on /dev/mapp

[PATCH] Btrfs: use a percpu to keep track of possibly pinned bytes

There are all of these checks in the ENOSPC code to see if committing the transaction would free up enough space to make the allocation. This is because early on we just committed the transaction and hoped and prayed, which resulted in cases where it took _forever_ to get an ENOSPC when we really

[trivial PATCH] treewide: Add __GFP_NOWARN to k.alloc calls with v.alloc fallbacks

Don't emit OOM warnings when k.alloc calls fail when there there is a v.alloc immediately afterwards. Converted a kmalloc/vmalloc with memset to kzalloc/vzalloc. Signed-off-by: Joe Perches --- drivers/block/drbd/drbd_bitmap.c | 2 +- drivers/infiniband/hw/ehca/ipz_pt_fn.c

Re: [3.10-rc6] WARNING: at fs/btrfs/inode.c:7961 btrfs_destroy_inode+0x265/0x2e0 [btrfs]()

Quoting Dave Jones (2013-06-19 14:34:50) > On Wed, Jun 19, 2013 at 02:02:33PM -0400, Chris Mason wrote: > > Quoting Dave Jones (2013-06-17 14:58:10) > > > On Mon, Jun 17, 2013 at 02:42:27PM -0400, Chris Mason wrote: > > > > Quoting Dave Jones (2013-06-17 14:20:06) > > > > > On Mon, Jun 17, 20

Re: [3.10-rc6] WARNING: at fs/btrfs/inode.c:7961 btrfs_destroy_inode+0x265/0x2e0 [btrfs]()

On Wed, Jun 19, 2013 at 02:02:33PM -0400, Chris Mason wrote: > Quoting Dave Jones (2013-06-17 14:58:10) > > On Mon, Jun 17, 2013 at 02:42:27PM -0400, Chris Mason wrote: > > > Quoting Dave Jones (2013-06-17 14:20:06) > > > > On Mon, Jun 17, 2013 at 01:39:42PM -0400, Chris Mason wrote: > > >

Re: [3.10-rc6] WARNING: at fs/btrfs/inode.c:7961 btrfs_destroy_inode+0x265/0x2e0 [btrfs]()

Quoting Dave Jones (2013-06-17 14:58:10) > On Mon, Jun 17, 2013 at 02:42:27PM -0400, Chris Mason wrote: > > Quoting Dave Jones (2013-06-17 14:20:06) > > > On Mon, Jun 17, 2013 at 01:39:42PM -0400, Chris Mason wrote: > > > > Quoting Dave Jones (2013-06-17 09:49:55) > > > > > Hit this while run

[PATCH] Btrfs: check for actual acls rather than just xattrs when caching no acl

We have an optimization that will go ahead and cache no acls on an inode if there are no xattrs on the inode. This saves us a lookup later to check the acls for writes or any other access. The problem is I use selinux so I always have an xattr on inodes, so make this test a little smarter and che

Re: [PATCH] Btrfs-progs: do not print uuid 0 when printing root item

Hi David, >> do not print uuid 0 when printing root item > > Actually I think we should print all the UUIDs unconditionally. This is > inside the debug-tree utility and a zero uuid is an information that may > be useful, even if only as one of the results 'grep uuid'. I don't see It is useless t

Re: [PATCH] Btrfs-progs: do not print uuid 0 when printing root item

> do not print uuid 0 when printing root item Actually I think we should print all the UUIDs unconditionally. This is inside the debug-tree utility and a zero uuid is an information that may be useful, even if only as one of the results 'grep uuid'. I don't see much point in hiding information her

[PATCH] Btrfs: fix wrong mirror number tuning

Now reading the data from the target device of the replace operation is allowed, so the mirror number that is greater than the stripes number of a chunk is valid, we will tune it when we find there is no target device later. Fix it. Signed-off-by: Miao Xie --- fs/btrfs/volumes.c | 3 --- 1 file

[PATCH] Btrfs: cleanup redundant code in btrfs_submit_direct()

Signed-off-by: Miao Xie --- fs/btrfs/inode.c | 10 +- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 590c274..65ae1cb 100644 --- a/fs/btrfs/inode.c +++ b/fs/btrfs/inode.c @@ -7136,7 +7136,6 @@ static void btrfs_submit_direct(int rw,

[PATCH] xfstests: add 'check -btrfs' support

Currently we can specify the testing filesytems like 'check -xfs', but btrfs is not support in this kind of command option. Add the option 'check -btrfs' support. Signed-off-by: Wang Sheng-Hui --- check |2 ++ 1 file changed, 2 insertions(+) diff --git a/check b/check index ff8fbcf..9c4061