Re: [PATCH v13 00/15] Btrfs In-band De-duplication

2016-10-18 Thread Qu Wenruo
At 10/17/2016 10:30 PM, David Sterba wrote: On Thu, Sep 08, 2016 at 03:12:49PM +0800, Qu Wenruo wrote: This patchset can be fetched from github: https://github.com/adam900710/linux.git wang_dedupe_20160907 Can you please publish the patchset in a branch that does not change name and is not b

Re: [PATCH] btrfs: pass correct args to btrfs_async_run_delayed_refs()

2016-10-18 Thread Wang Xiaoguang
hi, On 10/18/2016 06:32 PM, Holger Hoffstätte wrote: On Tue, 18 Oct 2016 15:56:13 +0800, Wang Xiaoguang wrote: In btrfs_truncate_inode_items()->btrfs_async_run_delayed_refs(), we swap the arg2 and arg3 wrongly, fix this. Signed-off-by: Wang Xiaoguang --- fs/btrfs/inode.c | 4 ++-- 1 file

[PATCH v2 1/3] btrfs-progs: send: remove unnecessary code

2016-10-18 Thread Tsutomu Itoh
Some unnecessary codes are deleted. - the setting of subvol is double. - read only check was already done by previous loop. Signed-off-by: Tsutomu Itoh --- v2: description was changed --- cmds-send.c | 11 --- 1 file changed, 11 deletions(-) diff --git a/cmds-send.c b/cmds-send.c ind

[PATCH 2/3] btrfs-progs: send: fix handling of multiple snapshots (-p option)

2016-10-18 Thread Tsutomu Itoh
We cannot send multiple snapshots at once by -p option. [before] # btrfs send -f /tmp/data0 -p Snap0 Snap[12] At subvol Snap1 At subvol Snap2 ERROR: parent determination failed for 0 # [after] # btrfs send -f /tmp/data0 -p Snap0 Snap[12] At subvol Snap1 At subvol Snap2 # Signed-off-by: Tsutomu

[PATCH 3/3] btrfs-progs: send: fix handling of -c option

2016-10-18 Thread Tsutomu Itoh
When two or more -c options are specified, cannot find a suitable parent. So, output stream is bigger than correct one. [before] # btrfs send -f /tmp/data1 -c Snap0 -c ../SnapX Snap[12] ../SnapY At subvol Snap1 At subvol Snap2 At subvol ../SnapY # ls -l /tmp/data1 -rw--- 1 root root 3153 Oct 1

[PATCH 1/3] btrfs-progs: send: remove unnecessary code

2016-10-18 Thread Tsutomu Itoh
Some unnecessary codes is deleted. Signed-off-by: Tsutomu Itoh --- cmds-send.c | 11 --- 1 file changed, 11 deletions(-) diff --git a/cmds-send.c b/cmds-send.c index 74d0128..dfdfe01 100644 --- a/cmds-send.c +++ b/cmds-send.c @@ -564,8 +564,6 @@ int cmd_send(int argc, char **argv)

Re: [PATCH v2 2/3] btrfs-progs: receive: Introduce option to exam and dump send stream

2016-10-18 Thread Qu Wenruo
At 10/18/2016 08:07 PM, David Sterba wrote: On Thu, Oct 13, 2016 at 03:32:53PM +0800, Qu Wenruo wrote: Hi David, Any updates? If you're busy on these fix, I could fix these problem and send a new version. I was about to add the series to merge but the output format needs work. At minimum,

Re: bio linked list corruption.

2016-10-18 Thread Andy Lutomirski
On 10/18/2016 05:10 PM, Linus Torvalds wrote: On Tue, Oct 18, 2016 at 4:42 PM, Chris Mason wrote: Seems to be the whole thing: Ahh. On lkml, so I do have it in my mailbox, but Dave changed the subject line when he tested on ext4 rather than btrfs.. Anyway, the corrupted address is somewhat

Re: bio linked list corruption.

2016-10-18 Thread Linus Torvalds
On Tue, Oct 18, 2016 at 5:10 PM, Linus Torvalds wrote: > > Adding Andy to the cc, because this *might* be triggered by the > vmalloc stack code itself. Maybe the re-use of stacks showing some > problem? Maybe Chris (who can't see the problem) doesn't have > CONFIG_VMAP_STACK enabled? I bet it's t

Re: bio linked list corruption.

2016-10-18 Thread Chris Mason
On Tue, Oct 18, 2016 at 05:10:56PM -0700, Linus Torvalds wrote: On Tue, Oct 18, 2016 at 4:42 PM, Chris Mason wrote: Seems to be the whole thing: Ahh. On lkml, so I do have it in my mailbox, but Dave changed the subject line when he tested on ext4 rather than btrfs.. Anyway, the corrupted ad

Re: bio linked list corruption.

2016-10-18 Thread Linus Torvalds
On Tue, Oct 18, 2016 at 4:42 PM, Chris Mason wrote: > > Seems to be the whole thing: Ahh. On lkml, so I do have it in my mailbox, but Dave changed the subject line when he tested on ext4 rather than btrfs.. Anyway, the corrupted address is somewhat interesting. As Dave Jones said, he saw list

Re: bio linked list corruption.

2016-10-18 Thread Chris Mason
On Tue, Oct 18, 2016 at 04:39:22PM -0700, Linus Torvalds wrote: On Tue, Oct 18, 2016 at 4:31 PM, Chris Mason wrote: Jens, not sure if you saw the whole thread. This has triggered bad page state errors, and also corrupted a btrfs list. It hurts me to say, but it might not actually be your fau

Re: bio linked list corruption.

2016-10-18 Thread Linus Torvalds
On Tue, Oct 18, 2016 at 4:31 PM, Chris Mason wrote: > > Jens, not sure if you saw the whole thread. This has triggered bad page > state errors, and also corrupted a btrfs list. It hurts me to say, but it > might not actually be your fault. Where is that thread, and what is the "this" that trigg

Re: bio linked list corruption.

2016-10-18 Thread Jens Axboe
On 10/18/2016 05:31 PM, Chris Mason wrote: On Tue, Oct 18, 2016 at 05:12:41PM -0600, Jens Axboe wrote: On 10/18/2016 04:42 PM, Dave Jones wrote: So Chris had me do a run on ext4 just for giggles. It took a while, but eventually this fell out... WARNING: CPU: 3 PID: 21324 at lib/list_debug.c:3

Re: bio linked list corruption.

2016-10-18 Thread Chris Mason
On Tue, Oct 18, 2016 at 05:12:41PM -0600, Jens Axboe wrote: On 10/18/2016 04:42 PM, Dave Jones wrote: So Chris had me do a run on ext4 just for giggles. It took a while, but eventually this fell out... WARNING: CPU: 3 PID: 21324 at lib/list_debug.c:33 __list_add+0x89/0xb0 list_add corruption.

Re: bio linked list corruption.

2016-10-18 Thread Jens Axboe
On 10/18/2016 04:42 PM, Dave Jones wrote: On Tue, Oct 11, 2016 at 10:45:07AM -0400, Dave Jones wrote: > WARNING: CPU: 1 PID: 3673 at lib/list_debug.c:33 __list_add+0x89/0xb0 > list_add corruption. prev->next should be next (e8806648), but was c967fcd8. (prev=880503878b80).

Re: bio linked list corruption.

2016-10-18 Thread Dave Jones
On Tue, Oct 11, 2016 at 10:45:07AM -0400, Dave Jones wrote: > WARNING: CPU: 1 PID: 3673 at lib/list_debug.c:33 __list_add+0x89/0xb0 > list_add corruption. prev->next should be next (e8806648), but was > c967fcd8. (prev=880503878b80). > CPU: 1 PID: 3673 Comm: trinity-c0 Not

Re: Monitoring Btrfs

2016-10-18 Thread Anand Jain
I would like to monitor my btrfs-filesystem for missing drives. This is actually correct behavior, the filesystem reports that it should have 6 devices, which is how it knows a device is missing. Missing - means missing at the time of mount. So how are you planning to monitor a disk wh

Re: question re: trim in btrfs

2016-10-18 Thread Jeff Mahoney
On 10/18/16 3:06 PM, Tim Walberg wrote: > Forgot to mention - this was on a rather crusty 4.2.6 kernel. Just upgraded > to 4.8.1 > and the issue appears to have been resolved... Thanks for following up. This issue was actually fixed in v4.3. There were a bunch of fixes for discard ranging from

Re: question re: trim in btrfs

2016-10-18 Thread Tim Walberg
Forgot to mention - this was on a rather crusty 4.2.6 kernel. Just upgraded to 4.8.1 and the issue appears to have been resolved... On 10/18/2016 12:42 -0500, Walberg, Tim wrote: >> Unless I'm misinterpreting something it appears that maybe btrfs >> doesn't pass >> fstrim commands down

Re: Btrfs dev del

2016-10-18 Thread Austin S. Hemmelgarn
On 2016-10-18 11:02, Stefan Malte Schumacher wrote: Hello One of the drives which I added to my array two days ago was most likely already damaged when I bought it - 312 read errors while scrubbing and lots of SMART errors. I want to take the drive out, go to my hardware vendor and have it repla

question re: trim in btrfs

2016-10-18 Thread Tim Walberg
Unless I'm misinterpreting something it appears that maybe btrfs doesn't pass fstrim commands down to the underlying drives when being used in a RAID-1 config. I have this output from a small script I wrote to run at boot time (and also via cron.weekly), rather than using continous trim in the bo

Btrfs dev del

2016-10-18 Thread Stefan Malte Schumacher
Hello One of the drives which I added to my array two days ago was most likely already damaged when I bought it - 312 read errors while scrubbing and lots of SMART errors. I want to take the drive out, go to my hardware vendor and have it replaced. So I issued the command: "btrfs dev del /dev/sdf

Re: [GIT PULL] Send fix for 4.9

2016-10-18 Thread Chris Mason
On 10/14/2016 05:54 PM, fdman...@kernel.org wrote: From: Filipe Manana Hi Chris, please pull the following send fix for the 4.9 kernel. Thanks Filipe, I've got this queued up for this week. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a mess

Re: Monitoring Btrfs

2016-10-18 Thread Austin S. Hemmelgarn
On 2016-10-17 16:40, Chris Murphy wrote: May be better to use /sys/fs/btrfs//devices to find the device to monitor, and then monitor them with blktrace - maybe there's some courser granularity available there, I'm not sure. The thing is, as far as Btrfs alone is concerned, a drive can be "bad" an

Re: Monitoring Btrfs

2016-10-18 Thread Austin S. Hemmelgarn
On 2016-10-17 23:23, Anand Jain wrote: I would like to monitor my btrfs-filesystem for missing drives. This is actually correct behavior, the filesystem reports that it should have 6 devices, which is how it knows a device is missing. Missing - means missing at the time of mount. So how

Re: [PATCH v2 2/3] btrfs-progs: receive: Introduce option to exam and dump send stream

2016-10-18 Thread David Sterba
On Thu, Oct 13, 2016 at 03:32:53PM +0800, Qu Wenruo wrote: > Hi David, > > Any updates? > > If you're busy on these fix, I could fix these problem and send a new > version. I was about to add the series to merge but the output format needs work. At minimum, something that's parseable, so some c

Re: [PATCH] btrfs: pass correct args to btrfs_async_run_delayed_refs()

2016-10-18 Thread Holger Hoffstätte
On Tue, 18 Oct 2016 15:56:13 +0800, Wang Xiaoguang wrote: > In btrfs_truncate_inode_items()->btrfs_async_run_delayed_refs(), we > swap the arg2 and arg3 wrongly, fix this. > > Signed-off-by: Wang Xiaoguang > --- > fs/btrfs/inode.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > >

[PATCH] btrfs: pass correct args to btrfs_async_run_delayed_refs()

2016-10-18 Thread Wang Xiaoguang
In btrfs_truncate_inode_items()->btrfs_async_run_delayed_refs(), we swap the arg2 and arg3 wrongly, fix this. Signed-off-by: Wang Xiaoguang --- fs/btrfs/inode.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 2b790bd..2f1372b 1006