Re: bad extent [5993525264384, 5993525280768), type mismatch with chunk

2015-11-21 Thread Christoph Anton Mitterer
Hey Qu. On Sun, 2015-11-22 at 10:04 +0800, Qu Wenruo wrote: > If any of you can recompile btrfs-progs and use gdb to debug it, > would > anyone please to investigate where did the wrong_chunk_type is set? > It is in the function check_extent_type(): Not 100% what you want... AFAIU, you just wan

Re: free space is missing after dist upgrade on lzo compressed vol

2015-11-21 Thread Duncan
Brenton Chapin posted on Sat, 21 Nov 2015 12:32:12 -0600 as excerpted: > Thanks, snapshots, or subvolumes, was it. (I'm not clear on the > distinction between a snapshot and a subvolume.) As Hugo says much more briefly, snapshots are a special kind of subvolume. These are normally (copy-on-wri

Re: bad extent [5993525264384, 5993525280768), type mismatch with chunk

2015-11-21 Thread Qu Wenruo
Hi Lukas, Laurent and Christoph, If any of you can recompile btrfs-progs and use gdb to debug it, would anyone please to investigate where did the wrong_chunk_type is set? It is in the function check_extent_type(): -- /* Check if the type of extent matches with its chunk */ static void che

Re: free space is missing after dist upgrade on lzo compressed vol

2015-11-21 Thread Hugo Mills
On Sat, Nov 21, 2015 at 12:32:12PM -0600, Brenton Chapin wrote: > Thanks, snapshots, or subvolumes, was it. (I'm not clear on the > distinction between a snapshot and a subvolume.) A snapshot is just a subvolume that's initialised (via CoW copies) with the contents of some other subvolume, rat

Re: free space is missing after dist upgrade on lzo compressed vol

2015-11-21 Thread Brenton Chapin
Thanks, snapshots, or subvolumes, was it. (I'm not clear on the distinction between a snapshot and a subvolume.) The 8G amount and that I did 2 distribution upgrades was a clue. When I searched for info on btrfs and snapshots, I eventually found this command, with these results: btrfs subvolume

Re: [PATCH 2/2] generic/15[78]: fix error messages in the golden output

2015-11-21 Thread Christoph Hellwig
> Shouldn't these be Invalid argument just like the > to a device case above or the clone case? E.g. something like this on top of your patch: diff --git a/tests/generic/158.out b/tests/generic/158.out index 1210429..dff3692 100644 --- a/tests/generic/158.out +++ b/tests/generic/158.out @@ -16,9

Re: [PATCH 2/2] generic/15[78]: fix error messages in the golden output

2015-11-21 Thread Christoph Hellwig
> --- a/tests/generic/158.out > +++ b/tests/generic/158.out > Try to dedupe a device > -XFS_IOC_FILE_EXTENT_SAME: Permission denied > +XFS_IOC_FILE_EXTENT_SAME: Invalid argument > Try to dedupe to a dir > -/mnt/test-158/dir1: Is a directory > +TEST_DIR/test-158/dir1: Is a directory > Try to dedu

Re: 4.2.6: livelock in recovery (free_reloc_roots)?

2015-11-21 Thread Lukas Pirl
On 11/21/2015 08:16 PM, Duncan wrote as excerpted: > Lukas Pirl posted on Sat, 21 Nov 2015 13:37:37 +1300 as excerpted: > >> > Can "btrfs_recover_relocation" prevented from being run? I would not >> > mind losing a few recent writes (what was a balance) but instead going >> > rw again, so I can re

Re: 4.2.6: livelock in recovery (free_reloc_roots)?

2015-11-21 Thread Alexander Fougner
Den 2015-11-21 kl. 08:16, skrev Duncan: > Lukas Pirl posted on Sat, 21 Nov 2015 13:37:37 +1300 as excerpted: > >> Can "btrfs_recover_relocation" prevented from being run? I would not >> mind losing a few recent writes (what was a balance) but instead going >> rw again, so I can restart a balance