[PATCH] btrfs: Handle unaligned length in extent_same

2015-06-08 Thread Mark Fasheh
The extent-same code rejects requests with an unaligned length. This poses a problem when we want to dedupe the tail extent of files as we skip cloning the portion between i_size and the extent boundary. If we don't clone the entire extent, it won't be deleted. So the combination of these

rw-mount-problem after raid1-failure

2015-06-08 Thread Martin
Hello! I have a raid1-btrfs-system (Kernel 3.19.0-18-generic, Ubuntu Vivid Vervet, btrfs-tools 3.17-1.1). One disk failed some days ago. I could remount the remaining one with -o degraded. After one day and some write-operations (with no errrors) I had to reboot the system. And now I can not

Re: [PATCH] btrfs: Handle unaligned length in extent_same

2015-06-08 Thread Mark Fasheh
On Mon, Jun 08, 2015 at 11:36:25PM +, Holger Hoffstätte wrote: On Mon, 08 Jun 2015 15:05:25 -0700, Mark Fasheh wrote: The extent-same code rejects requests with an unaligned length. This poses a problem when we want to dedupe the tail extent of files as we skip cloning the portion

Re: [PATCH] btrfs: Handle unaligned length in extent_same

2015-06-08 Thread Darrick J. Wong
On Mon, Jun 08, 2015 at 03:05:25PM -0700, Mark Fasheh wrote: The extent-same code rejects requests with an unaligned length. This poses a problem when we want to dedupe the tail extent of files as we skip cloning the portion between i_size and the extent boundary. If we don't clone the

Re: [PATCH] btrfs: Handle unaligned length in extent_same

2015-06-08 Thread Holger Hoffstätte
On Mon, 08 Jun 2015 15:05:25 -0700, Mark Fasheh wrote: The extent-same code rejects requests with an unaligned length. This poses a problem when we want to dedupe the tail extent of files as we skip cloning the portion between i_size and the extent boundary. This sounds familiar:

Re: [PATCH 3/3] btrfs: add missing discards when unpinning extents with -o discard

2015-06-08 Thread Filipe David Manana
On Wed, Jun 3, 2015 at 3:47 PM, je...@suse.com wrote: From: Jeff Mahoney je...@suse.com When we clear the dirty bits in btrfs_delete_unused_bgs for extents in the empty block group, it results in btrfs_finish_extent_commit being unable to discard the freed extents. The block group removal

Re: [PATCH 5/5] Btrfs: incremental send, fix rmdir not send utimes

2015-06-08 Thread Filipe David Manana
On Mon, Jun 8, 2015 at 4:44 AM, Robbie Ko robbi...@synology.com wrote: Hi Filipe, Hi Robbie, I've fixed don't send utimes for non-existing directory with another solution. In apply_dir_move(), the old parent dir. and new parent dir. will be updated after the current dir. has moved.

[PATCH] btrfs: cleanup noused initialization of dev in btrfs_end_bio()

2015-06-08 Thread Zhaolei
From: Zhao Lei zhao...@cn.fujitsu.com It is introduced by: c404e0dc2c843b154f9a36c3aec10d0a715d88eb Btrfs: fix use-after-free in the finishing procedure of the device replace But seems no relationship with that bug, this patch revirt these code block for cleanup. Signed-off-by: Zhao Lei

btrfs-progs: btrfs replace status show 139,3% done

2015-06-08 Thread Patrick Schmid
Hi I started a disk replacement around 11:00 with following command: btrfs replace start /dev/iscsi/diskA /dev/diskB /export/backup The disks has a size of 10TiB. Now (15:00)i`ve checked the status and get btrfs replace status -1 /export/backup/ 143.7% done, 0 write

Re: 4.1-rc6 - kernel crash after doing chattr +C

2015-06-08 Thread Chris Mason
On 06/06/2015 02:07 AM, Tomasz Chmielewski wrote: 4.1-rc6, busy filesystem. I was running mongo import which made quite a lot of IO. During the import, I did chattr +C /var/lib/mongodb - shortly after I saw this in dmesg and server died: [57860.149839] BUG: unable to handle kernel NULL