From: "Garry T. Williams" <gtwilliams@gmail.com>
To: dsterba@suse.cz, Qu Wenruo <quwenruo.btrfs@gmx.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs release 5.14.1
Date: Wed, 22 Sep 2021 22:48:56 -0400 [thread overview]
Message-ID: <11964729.O9o76ZdvQC@gtw> (raw)
In-Reply-To: <20210922095044.GS9286@twin.jikos.cz>
On Wednesday, September 22, 2021 5:50:44 AM EDT David Sterba wrote:
> On Wed, Sep 22, 2021 at 09:26:50AM +0800, Qu Wenruo wrote:
> > On 2021/9/22 09:10, Garry T. Williams wrote:
> > > On Monday, September 20, 2021 12:22:24 PM EDT David Sterba wrote:
> > >> Hi,
> > >>
> > >> btrfs-progs version 5.14.1 have been released. This is a bugfix release.
> > >
> > > FYI,
> > >
> > > === START TEST /home/garry/src/btrfs-progs/tests/fsck-tests/013-extent-tree-rebuild
> > > $TEST_DEV not given, using /home/garry/src/btrfs-progs/tests/test.img as fallback
> > > ====== RUN CHECK root_helper /home/garry/src/btrfs-progs/mkfs.btrfs -f /home/garry/src/btrfs-progs/tests/test.img
> > > ERROR: /home/garry/src/btrfs-progs/tests/test.img is mounted
> >
> > This means your previous run has hit some errors and the test image is
> > not unmounted.
>
> The test suite is designed so that it leaves the last state where it
> failed to allow analysis. After failed tests most failures can be fixed
> by 'make test-clean', manual check can be done by 'losetup' and 'mount'
> looking for the paths from the git repository.
Thank you, David. Running make test-clean was the key. I didn't know
that was required.
--
Garry T. Williams
prev parent reply other threads:[~2021-09-23 2:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-20 16:22 Btrfs progs release 5.14.1 David Sterba
2021-09-22 1:10 ` Garry T. Williams
2021-09-22 1:26 ` Qu Wenruo
2021-09-22 9:50 ` David Sterba
2021-09-23 2:48 ` Garry T. Williams [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=11964729.O9o76ZdvQC@gtw \
--to=gtwilliams@gmail.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
/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.