Re: [PATCH] generic/311: Disable dmesg check

2015-07-17 Thread Chandan Rajendra
On Friday 17 Jul 2015 06:16:02 Brian Foster wrote: On Fri, Jul 17, 2015 at 12:56:43AM -0400, Chandan Rajendra wrote: When running generic/311 on Btrfs' subpagesize-blocksize patchset (on ppc64 with 4k sectorsize and 16k node/leaf size) I noticed the following call trace, BTRFS

Re: [PATCH] Btrfs: incremental send, fix clone operations for compressed extents

2015-07-17 Thread Filipe David Manana
On Fri, Jul 17, 2015 at 4:49 AM, Jan Alexander Steffens jan.steff...@gmail.com wrote: On Sun, May 3, 2015 at 2:56 AM, Filipe Manana fdman...@suse.com wrote: Marc reported a problem where the receiving end of an incremental send was performing clone operations that failed with -EINVAL. This

Re: [PATCH 1/2] Btrfs: move kobj stuff out of dev_replace lock range

2015-07-17 Thread Liu Bo
On Fri, Jul 17, 2015 at 06:23:13PM +0800, Anand Jain wrote: On 07/17/2015 04:49 PM, Liu Bo wrote: To avoid deadlock described in commit 084b6e7c7607 (btrfs: Fix a lockdep warning when running xfstest.), we should move kobj stuff out of dev_replace lock range. Is this just a lock

[PATCH 2/2] Btrfs: fix lockdep deadlock warning due to dev_replace

2015-07-17 Thread Liu Bo
Xfstests btrfs/011 complains about a deadlock warning, [ 1226.649039] = [ 1226.649039] [ INFO: possible irq lock inversion dependency detected ] [ 1226.649039] 4.1.0+ #270 Not tainted [ 1226.649039]

[PATCH 1/2] Btrfs: move kobj stuff out of dev_replace lock range

2015-07-17 Thread Liu Bo
To avoid deadlock described in commit 084b6e7c7607 (btrfs: Fix a lockdep warning when running xfstest.), we should move kobj stuff out of dev_replace lock range. Signed-off-by: Liu Bo bo.li@oracle.com --- fs/btrfs/dev-replace.c | 8 1 file changed, 4 insertions(+), 4 deletions(-)

Re: [PATCH] btrfs: Add raid56 support for updating num_tolerated_disk_barrier_failures in btrfs_balance()

2015-07-17 Thread Anand Jain
nice clean up thanks. but... more below. On 07/16/2015 08:15 PM, Zhaolei wrote: From: Zhao Lei zhao...@cn.fujitsu.com Code for updating fs_info-num_tolerated_disk_barrier_failures in btrfs_balance() lacks raid56 support. Reason: Above code was wroten in 2012-08-01, together with

[PATCH] btrfs: its btrfs_err() instead of btrfs_error()

2015-07-17 Thread Anand Jain
sorry I indented to use btrfs_err() and I have no idea how btrfs_error() got there. infact I was thinking about these kind of oversights since these two func are too closely named. Signed-off-by: Anand Jain anand.j...@oracle.com --- fs/btrfs/dev-replace.c | 2 +- 1 file changed, 1 insertion(+),

RE: [PATCH] btrfs: Add raid56 support for updating num_tolerated_disk_barrier_failures in btrfs_balance()

2015-07-17 Thread Zhao Lei
Hi, Anand Jain Thanks for review it. -Original Message- From: Anand Jain [mailto:anand.j...@oracle.com] Sent: Friday, July 17, 2015 5:12 PM To: Zhaolei; linux-btrfs@vger.kernel.org Subject: Re: [PATCH] btrfs: Add raid56 support for updating num_tolerated_disk_barrier_failures in

[PATCH v3] Btrfs-progs: add feature to get mininum size for resizing a fs/device

2015-07-17 Thread fdmanana
From: Filipe Manana fdman...@suse.com Currently there is not way for a user to know what is the minimum size a device of a btrfs filesystem can be resized to. Sometimes the value of total allocated space (sum of all allocated chunks/device extents), which can be parsed from 'btrfs filesystem

[PATCH] [RFC] btrfs: Avoid using single-type chunk on degree mode

2015-07-17 Thread Zhaolei
From: Zhao Lei zhao...@cn.fujitsu.com We can get mount-fail in following operation: # mkfs a raid1 filesystem mkfs.btrfs -f -d raid1 -m raid1 /dev/vdd /dev/vde # destroy a disk dd if=/dev/zero of=/dev/vde bs=1M count=1 # do some fs operation on degraded mode mount -o degraded

Re: [PATCH] generic/311: Disable dmesg check

2015-07-17 Thread Brian Foster
On Fri, Jul 17, 2015 at 12:56:43AM -0400, Chandan Rajendra wrote: When running generic/311 on Btrfs' subpagesize-blocksize patchset (on ppc64 with 4k sectorsize and 16k node/leaf size) I noticed the following call trace, BTRFS (device dm-0): parent transid verify failed on 29720576 wanted 160

Re: [PATCH 1/2] Btrfs: move kobj stuff out of dev_replace lock range

2015-07-17 Thread Anand Jain
On 07/17/2015 04:49 PM, Liu Bo wrote: To avoid deadlock described in commit 084b6e7c7607 (btrfs: Fix a lockdep warning when running xfstest.), we should move kobj stuff out of dev_replace lock range. Is this just a lock optimizing patch or fixing _a_ cause for the deadlock. ? Am I

Re: [PATCH] btrfs: Show detail information when mount failed on missing devices

2015-07-17 Thread Anand Jain
On 07/16/2015 04:44 PM, Zhaolei wrote: From: Zhao Lei zhao...@cn.fujitsu.com When mount failed because missing device, we can see following dmesg: [ 1060.267743] BTRFS: too many missing devices, writeable mount is not allowed [ 1060.273158] BTRFS: open_ctree failed This patch add

Re: Concurrent write access

2015-07-17 Thread Calvin Walton
On Fri, 2015-07-10 at 00:13 +0200, Wolfgang Mader wrote: On Thursday 09 July 2015 22:06:09 Hugo Mills wrote: On Thu, Jul 09, 2015 at 11:34:40PM +0200, Wolfgang Mader wrote: Hi, I have a btrfs raid10 which is connected to a server hosting multiple virtual machine. Does btrfs support

btrfs_create_pending_block_groups:9460: errno=-27 unknown

2015-07-17 Thread Omar Sandoval
Hey, Filipe, I've been seeing errors of this sort: [ 658.221300] [ cut here ] [ 658.221948] WARNING: CPU: 0 PID: 1636 at fs/btrfs/extent-tree.c:9460 btrfs_create_pending_block_groups+0x16b/0x210() [ 658.223274] CPU: 0 PID: 1636 Comm: btrfs-transacti Not tainted

[GIT PULL] Btrfs

2015-07-17 Thread Chris Mason
Hi Linus, We have some fixes in my for-linus-4.2 branch: git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus-4.2 These are all from Filipe, and cover a few problems we've had reported on the list recently (along with ones he found on his own). Filipe Manana (5)

Re: btrfs_create_pending_block_groups:9460: errno=-27 unknown

2015-07-17 Thread Filipe David Manana
On Fri, Jul 17, 2015 at 7:36 PM, Omar Sandoval osan...@fb.com wrote: Hey, Filipe, I've been seeing errors of this sort: [ 658.221300] [ cut here ] [ 658.221948] WARNING: CPU: 0 PID: 1636 at fs/btrfs/extent-tree.c:9460