Re: "bad metadata" not fixed by btrfs repair

On Thu, Mar 31, 2016 at 08:42:46PM +0200, Henk Slager wrote: > So also false alerts. btrfs-tools 4.5.1 with Qu's patch from patchwork doesnt show those warnings any more. Greetings Marc -- - Marc Haber | "I

Re: "bad metadata" not fixed by btrfs repair

On Mon, Mar 28, 2016 at 4:37 PM, Marc Haber wrote: > Hi, > > I have a btrfs which btrfs check --repair doesn't fix: > > # btrfs check --repair /dev/mapper/fanbtr > bad metadata [4425377054720, 4425377071104) crossing stripe boundary > bad metadata [4425380134912,

Re: "bad metadata" not fixed by btrfs repair

On Thu, Mar 31, 2016 at 4:23 AM, Qu Wenruo wrote: > > > Henk Slager wrote on 2016/03/30 16:03 +0200: >> >> On Wed, Mar 30, 2016 at 9:00 AM, Qu Wenruo >> wrote: >>> >>> First of all. >>> >>> The "crossing stripe boundary" error message itself is

Re: "bad metadata" not fixed by btrfs repair

On Thu, Mar 31, 2016 at 2:28 AM, Qu Wenruo wrote: > > > Henk Slager wrote on 2016/03/30 16:03 +0200: >> >> On Wed, Mar 30, 2016 at 9:00 AM, Qu Wenruo >> wrote: >>> >>> First of all. >>> >>> The "crossing stripe boundary" error message itself is

Re: "bad metadata" not fixed by btrfs repair

Henk Slager wrote on 2016/03/30 16:03 +0200: On Wed, Mar 30, 2016 at 9:00 AM, Qu Wenruo wrote: First of all. The "crossing stripe boundary" error message itself is *HARMLESS* for recent kernels. It only means, that metadata extent won't be checked by scrub on

Re: "bad metadata" not fixed by btrfs repair

Henk Slager wrote on 2016/03/30 16:03 +0200: On Wed, Mar 30, 2016 at 9:00 AM, Qu Wenruo wrote: First of all. The "crossing stripe boundary" error message itself is *HARMLESS* for recent kernels. It only means, that metadata extent won't be checked by scrub on

Re: "bad metadata" not fixed by btrfs repair

On Wed, Mar 30, 2016 at 9:00 AM, Qu Wenruo wrote: > First of all. > > The "crossing stripe boundary" error message itself is *HARMLESS* for recent > kernels. > > It only means, that metadata extent won't be checked by scrub on recent > kernels. > Because scrub by its

Re: "bad metadata" not fixed by btrfs repair

On Wed, Mar 30, 2016 at 04:03:17PM +0800, Qu Wenruo wrote: > Did your btrfs have enough *unallocated* space? 87 Gig out of a total 200 Gig Device size. I guess that should be enough for a rebalance of 2,8 Gig Metadata. Greetings Ma "please excuse my cynism" rc --

Re: "bad metadata" not fixed by btrfs repair

Marc Haber wrote on 2016/03/30 09:18 +0200: On Wed, Mar 30, 2016 at 03:00:19PM +0800, Qu Wenruo wrote: Marc Haber wrote on 2016/03/29 08:43 +0200: On Mon, Mar 28, 2016 at 03:35:32PM -0400, Austin S. Hemmelgarn wrote: Did you convert this filesystem from ext4 (or ext3)? No. You hadn't

Re: "bad metadata" not fixed by btrfs repair

On Wed, Mar 30, 2016 at 03:00:19PM +0800, Qu Wenruo wrote: > Marc Haber wrote on 2016/03/29 08:43 +0200: > >On Mon, Mar 28, 2016 at 03:35:32PM -0400, Austin S. Hemmelgarn wrote: > >>Did you convert this filesystem from ext4 (or ext3)? > > > >No. > > > >>You hadn't mentioned what version of

Re: "bad metadata" not fixed by btrfs repair

First of all. The "crossing stripe boundary" error message itself is *HARMLESS* for recent kernels. It only means, that metadata extent won't be checked by scrub on recent kernels. Because scrub by its codes, has a limitation that, it can only check tree blocks which are inside a 64K block.

Re: "bad metadata" not fixed by btrfs repair

On Mon, Mar 28, 2016 at 02:46:54PM -0600, Chris Murphy wrote: > http://git.kernel.org/cgit/linux/kernel/git/kdave/btrfs-progs.git/tree/cmds-check.c > line 7722 discusses this error message and it looks like there's no > repair function for it yet; uncertain what problems can result from > this.

Re: "bad metadata" not fixed by btrfs repair

On Tue, Mar 29, 2016 at 08:43:51AM +0200, Marc Haber wrote: > On Mon, Mar 28, 2016 at 03:35:32PM -0400, Austin S. Hemmelgarn wrote: > > As far as what the kernel is involved with, the easy way to check is if it's > > operating on a mounted filesystem or not. If it only operates on mounted > >

Re: "bad metadata" not fixed by btrfs repair

On Mon, Mar 28, 2016 at 09:51:43PM +0300, Nazar Mokrynskyi wrote: > However, despite those messages everything seems to work fine. In my case, trying to balance the filesystem results in a the balance not finishing in hours, I/O performance going way down during the balance, and a plethora of

Re: "bad metadata" not fixed by btrfs repair

On Mon, Mar 28, 2016 at 03:35:32PM -0400, Austin S. Hemmelgarn wrote: > Did you convert this filesystem from ext4 (or ext3)? No. > You hadn't mentioned what version of btrfs-progs you're using, and that is > somewhat important for recovery. I'm not sure if current versions of btrfs > check can

Re: "bad metadata" not fixed by btrfs repair

On Mon, Mar 28, 2016 at 12:51 PM, Nazar Mokrynskyi wrote: >>> # btrfs check --repair /dev/mapper/fanbtr >>> bad metadata [4425377054720, 4425377071104) crossing stripe boundary >>> bad metadata [4425380134912, 4425380151296) crossing stripe boundary >>> bad metadata

Re: "bad metadata" not fixed by btrfs repair

On 2016-03-28 10:37, Marc Haber wrote: Hi, I have a btrfs which btrfs check --repair doesn't fix: # btrfs check --repair /dev/mapper/fanbtr bad metadata [4425377054720, 4425377071104) crossing stripe boundary bad metadata [4425380134912, 4425380151296) crossing stripe boundary bad metadata

Re: "bad metadata" not fixed by btrfs repair

On Mon, Mar 28, 2016 at 06:51:02PM +, Hugo Mills wrote: >"Could not find root 8" is harmless (and will be going away as a > message soon). It just means that systemd is probing the FS for > quotas, and you don't have quotas enabled. *phew* That message was not what I wanted to read on

Re: "bad metadata" not fixed by btrfs repair

I have the same thing with kernel 4.5 and btrfs-progs 4.4. Wrote about it 2 weeks ago and didn't get any answer: https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg51609.html However, despite those messages everything seems to work fine. Sincerely, Nazar Mokrynskyi

Re: "bad metadata" not fixed by btrfs repair

On Mon, Mar 28, 2016 at 08:42:37PM +0200, Marc Haber wrote: > On Mon, Mar 28, 2016 at 04:37:14PM +0200, Marc Haber wrote: > > I have a btrfs which btrfs check --repair doesn't fix: > > > > # btrfs check --repair /dev/mapper/fanbtr > > bad metadata [4425377054720, 4425377071104) crossing stripe

Re: "bad metadata" not fixed by btrfs repair

On Mon, Mar 28, 2016 at 04:37:14PM +0200, Marc Haber wrote: > I have a btrfs which btrfs check --repair doesn't fix: > > # btrfs check --repair /dev/mapper/fanbtr > bad metadata [4425377054720, 4425377071104) crossing stripe boundary > bad metadata [4425380134912, 4425380151296) crossing stripe

"bad metadata" not fixed by btrfs repair

Hi, I have a btrfs which btrfs check --repair doesn't fix: # btrfs check --repair /dev/mapper/fanbtr bad metadata [4425377054720, 4425377071104) crossing stripe boundary bad metadata [4425380134912, 4425380151296) crossing stripe boundary bad metadata [4427532795904, 4427532812288) crossing