All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Filipe Manana <fdmanana@gmail.com>
Cc: David Sterba <dsterba@suse.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs progs release 5.10.1
Date: Fri, 19 Feb 2021 20:38:30 +0100	[thread overview]
Message-ID: <20210219193830.GL1993@twin.jikos.cz> (raw)
In-Reply-To: <CAL3q7H58PJk3Fyq4b7WTWGrzVmz5zATDDTCKO3SPS0EF=x0k4g@mail.gmail.com>

On Tue, Feb 16, 2021 at 11:00:18AM +0000, Filipe Manana wrote:
> On Fri, Feb 5, 2021 at 11:33 AM David Sterba <dsterba@suse.com> wrote:
> >
> > Hi,
> >
> > btrfs-progs version 5.10.1 have been released.
> >
> > The static build got broken due to libmount added in 5.10, this works now. The
> > minimum libmount version is 2.24 that is not available on some LTS distros like
> > CentOS 7. The plan is to bring the support back, reimplementing some libmount
> > functionality and dropping the dependency again.
> >
> > Tarballs: https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/
> > Git: git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git
> >
> > Shortlog:
> >
> > David Sterba (6):
> >       btrfs-progs: build: fix linking with static libmount
> 
> Btw, this causes two fstests to fail:
> 
> $ ./check btrfs/100 btrfs/101
> FSTYP         -- btrfs
> PLATFORM      -- Linux/x86_64 debian8 5.11.0-rc6-btrfs-next-80 #1 SMP
> PREEMPT Wed Feb 3 11:28:05 WET 2021
> MKFS_OPTIONS  -- /dev/sdc
> MOUNT_OPTIONS -- /dev/sdc /home/fdmanana/btrfs-tests/scratch_1
> 
> btrfs/100 6s ... [failed, exit status 1]- output mismatch (see
> /home/fdmanana/git/hub/xfstests/results//btrfs/100.out.bad)
>     --- tests/btrfs/100.out 2020-06-10 19:29:03.818519162 +0100
>     +++ /home/fdmanana/git/hub/xfstests/results//btrfs/100.out.bad
> 2021-02-16 10:55:53.145343890 +0000
>     @@ -2,10 +2,7 @@
>      Label: none  uuid: <UUID>
>       Total devices <NUM> FS bytes used <SIZE>
>       devid <DEVID> size <SIZE> used <SIZE> path SCRATCH_DEV
>     - devid <DEVID> size <SIZE> used <SIZE> path /dev/mapper/error-test
>     + devid <DEVID> size <SIZE> used <SIZE> path dm-0
> 
>     -Label: none  uuid: <UUID>
>     ...
>     (Run 'diff -u /home/fdmanana/git/hub/xfstests/tests/btrfs/100.out
> /home/fdmanana/git/hub/xfstests/results//btrfs/100.out.bad'  to see
> the entire diff)
> btrfs/101 8s ... [failed, exit status 1]- output mismatch (see
> /home/fdmanana/git/hub/xfstests/results//btrfs/101.out.bad)
>     --- tests/btrfs/101.out 2020-06-10 19:29:03.818519162 +0100
>     +++ /home/fdmanana/git/hub/xfstests/results//btrfs/101.out.bad
> 2021-02-16 10:55:58.105503554 +0000
>     @@ -2,10 +2,7 @@
>      Label: none  uuid: <UUID>
>       Total devices <NUM> FS bytes used <SIZE>
>       devid <DEVID> size <SIZE> used <SIZE> path SCRATCH_DEV
>     - devid <DEVID> size <SIZE> used <SIZE> path /dev/mapper/error-test
>     + devid <DEVID> size <SIZE> used <SIZE> path dm-0
> 
>     -Label: none  uuid: <UUID>
>     ...
>     (Run 'diff -u /home/fdmanana/git/hub/xfstests/tests/btrfs/101.out
> /home/fdmanana/git/hub/xfstests/results//btrfs/101.out.bad'  to see
> the entire diff)
> Ran: btrfs/100 btrfs/101
> Failures: btrfs/100 btrfs/101
> Failed 2 of 2 tests
> 
> 
> Is there any plan to fix this?

Yes, it's fixed in devel, the path canonicalization got accidentally
broken by my libmount workarounds.

      reply	other threads:[~2021-02-19 19:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05 11:25 Btrfs progs release 5.10.1 David Sterba
2021-02-16 11:00 ` Filipe Manana
2021-02-19 19:38   ` David Sterba [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210219193830.GL1993@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@suse.com \
    --cc=fdmanana@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.