From: Filipe Manana <fdmanana@gmail.com>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Marcos Paulo de Souza <marcos@mpdesouza.com>
Subject: Re: Btrfs progs release 5.10
Date: Tue, 16 Feb 2021 11:48:38 +0000 [thread overview]
Message-ID: <CAL3q7H5_bsBUL+OZg+tNbN4Tx6bT7Gwqmh1L2N-7nhn_c++vLQ@mail.gmail.com> (raw)
In-Reply-To: <20210118222021.11603-1-dsterba@suse.com>
On Tue, Jan 19, 2021 at 5:26 AM David Sterba <dsterba@suse.com> wrote:
>
> Hi,
>
> btrfs-progs version 5.10 have been released.
>
> Only minor changes snice -rc1: CI on gitlab disabled, some docs added.
>
> Changelog:
>
> * scrub status:
> * print percentage of progress
> * add size unit options
> * fi usage: also print free space from statfs
> * convert: copy full 64 bit timestamp from ext4 if avaialble
> * check:
> * add ability to repair extent item generation
> * new option to remove leftovers from inode number cache (-o inode_cache)
> * check for already running exclusive operation (balance, device add/...)
> when starting one
> * preliminary json output support for 'device stats'
> * fixes:
> * subvolume set-default: id 0 correctly falls back to tolpevel
> * receive: align internal buffer to allow fast CRC calculation
> * logical-resolve: distinguish -o subvol and bind mounts
> * build: new dependency libmount
> * other
> * doc fixes and updates
> * new tests
> * ci on gitlab temporarily disabled
> * debugging output enhancements
>
> 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:
>
> Adam Borowski (1):
> btrfs-progs: a bunch of typo fixes
>
> Daniel Xu (1):
> btrfs-progs: sort main help menu entries
>
> David Sterba (22):
> btrfs-progs: scrub status: print percents of scrubbed bytes
> btrfs-progs: scrub status: add unit mode options
> btrfs-progs: docs: add missing option to scrub status
> btrfs-progs: move path_cat_out helpers to path-utils
> btrfs-progs: docs: fix mknod arguments of the control device
> btrfs-progs: add helpers for parsing filesystem exclusive operation
> btrfs-progs: add helper to check or wait for exclusive operation
> btrfs-progs: add enqueue parameter for exclusive ops
> btrfs-progs: docs: document fs exclusive operations
> btrfs-progs: subvol show: fix required arguments in help texts
> btrfs-progs: fix short/long unit size options
> btrfs-progs: tests: add Makefile for testsuite
> btrfs-progs: initialize formatter context properly
> btrfs-progs: tests: add json formatter test coverage
> btrfs-progs: build: add missing gitignore and clean binaries
> btrfs-progs: tests: test full 64bit timestamp conversion on ext4
> btrfs-progs: subvol set-default: change id to 5 if specified as 0
> btrfs-progs: tests: set toplevel subvolume as default when specified as 0
> btrfs-progs: ci: temporarily disable gitlab CI
> btrfs-progs: docs: document command line conventions
> btrfs-progs: update CHANGES for 5.10
> Btrfs progs v5.10
>
> Eric Semeniuc (1):
> btrfs-progs: docs: grammar and typo fix for btrfs check
>
> Goldwyn Rodrigues (3):
> btrfs-progs: add get_fsid_fd() for getting fsid using fd
> btrfs-progs: add sysfs file reading helpers
> btrfs-progs: check for exclusive operation before issuing another
>
> Jiachen YANG (1):
> btrfs-progs: convert: copy extra timespec on ext4
>
> Josef Bacik (4):
> btrfs-progs: only print the parent or ref root for ref mismatches
> btrfs-progs: print the eb flags for nodes as well
> btrfs-progs: image: fix invalid size check for extent items
> btrfs-progs: check: properly exclude leaves for lowmem mode
>
> Marcos Paulo de Souza (4):
> btrfs-progs: build: add libmount dependency
> btrfs-progs: utils: introduce find_mount_fsroot
I can't find the thread for that patch on the mailing list, so I'll
report the issue here.
This change, "btrfs-progs: utils: introduce find_mount_fsroot", makes
at least one test case from fstests fail:
$ ./check btrfs/184
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/184 1s ... [failed, exit status 1]- output mismatch (see
/home/fdmanana/git/hub/xfstests/results//btrfs/184.out.bad)
--- tests/btrfs/184.out 2020-06-10 19:29:03.822519250 +0100
+++ /home/fdmanana/git/hub/xfstests/results//btrfs/184.out.bad
2021-02-16 11:42:40.755587041 +0000
@@ -1,2 +1,3 @@
QA output created by 184
-Silence is golden
+Deleted dev superblocks not scratched
+(see /home/fdmanana/git/hub/xfstests/results//btrfs/184.full for details)
...
(Run 'diff -u /home/fdmanana/git/hub/xfstests/tests/btrfs/184.out
/home/fdmanana/git/hub/xfstests/results//btrfs/184.out.bad' to see
the entire diff)
Ran: btrfs/184
Failures: btrfs/184
Failed 1 of 1 tests
Any plans to fix this?
Thanks.
> btrfs-progs: inspect: use find_mount_fsroot in logical-resolve
> btrfs-progs: tests: test logical-resolve in various scenarios
>
> Nikolay Borisov (2):
> btrfs-progs: check: add option to remove ino cache
> btrfs-progs: tests: test check --clear-ino-cache
>
> Omar Sandoval (1):
> btrfs-progs: send: fix crash on unknown option
>
> Qu Wenruo (6):
> btrfs-progs: mkfs: refactor how we handle sectorsize override
> btrfs-progs: check/lowmem: add ability to repair extent item generation
> btrfs-progs: check/original: don't reset extent generation for check_block
> btrfs-progs: check/original: add ability to repair extent item generation
> btrfs-progs: tests: enhance invalid extent item generation test cases
> btrfs-progs: check: only warn if clearing v1 cache and v2 found
>
> Sheng Mao (1):
> btrfs-progs: align receive buffer to enable fast CRC
>
> Sidong Yang (3):
> btrfs-progs: fi usage: add avail info from statfs()
> btrfs-progs: extend fmt_print_start_group to handle unnamed group
> btrfs-progs: device stats: add json output format
>
> Su Yue (2):
> btrfs-progs: subvol show: reset subvol_path to NULL after free
> btrfs-progs: print bytenr of child eb if mismatched level found in read_node_slot
>
> Tomasz Torcz (1):
> btrfs-progs: docs: add info about "single" profile requirements for swapfile
>
--
Filipe David Manana,
“Whether you think you can, or you think you can't — you're right.”
prev parent reply other threads:[~2021-02-16 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 22:20 Btrfs progs release 5.10 David Sterba
2021-01-21 15:37 ` David Sterba
2021-02-16 11:48 ` Filipe Manana [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=CAL3q7H5_bsBUL+OZg+tNbN4Tx6bT7Gwqmh1L2N-7nhn_c++vLQ@mail.gmail.com \
--to=fdmanana@gmail.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marcos@mpdesouza.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).