All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, clm@fb.com
Subject: Re: Btrfs progs release 4.1
Date: Wed, 9 Sep 2015 15:19:25 +0200	[thread overview]
Message-ID: <20150909131925.GG8891@suse.cz> (raw)
In-Reply-To: <55EF8CBD.3020105@cn.fujitsu.com>

On Wed, Sep 09, 2015 at 09:34:53AM +0800, Qu Wenruo wrote:
> > David Sterba (79):
> >        btrfs-progs: tests: log the test name in results file
> >        btrfs-progs: tests: support more formats of test images
> >        btrfs-progs: tests: use readlink -f to resolve path
> >        btrfs-progs: tests: sort image files
> >        btrfs-progs: test: 015-check-bad-memory-access
> >        btrfs-progs: tests: add script to clean intermediate images
> >        btrfs-progs: receive: restore capabilities after chown
> >        btrfs-progs: tests: add driver script for misc tests
> >        btrfs-progs: tests: common: add helper run_check_stdout
> >        btrfs-progs: tests: add misc test for fs features
> >        btrfs-progs: update .gitignore
> >        btrfs-progs: subvol show: print received uuid
> >        btrfs-progs: subvol show: tweak output
> >        btrfs-progs: btrfstune: rework option handling
> >        btrfs-progs: btrfstune: add option to enable NO_HOLES
> >        btrfs-progs: doc: update btrfstune manpage
> >        btrfs-progs: tests: add misc tests for uuid rewrite
> >        btrfs-progs: btrfstune: make uuid rewrite progress more verbose
> >        btrfs-progs: ioctl.h: reorder to match kernel uapi header
> >        btrfs-progs: ioctl.h: copy commented version of scrub_progress structure
> >        btrfs-progs: ioctl.h: copy commented version of balance structures
> >        btrfs-progs: ioctl.h: add EXTENT_SAME ioctl and structures
> >        btrfs-progs: ioctl.h: add send flag mask
> >        btrfs-progs: ioctl.h: update type annotations
> >        btrfs-progs: ioctl.h: update btrfs_ioctl_fs_info_args
> >        btrfs-progs: ioctl.h: add btrfs_ioctl_feature_flags struct
> >        btrfs-progs: doc: update btrfs-rescue page and drop btrfs-zero-log
> >        btrfs-progs: scrub: more friendly duration format in status
> >        btrfs-progs: add function to stringify filesystem features
> >        btrfs-progs: convert: allow to set filesystem features
> 
> Tons of new patches, but at least I didn't find the patch in mail list 
> for the above convert patch, when I want to comment on it.

Well, I'm doing lots of small and boring patches that I consider noisy
for the mailinglist, OTOH I introduced some bugs that would be caught by
reviews.

> So I can only comment here.
> 
> [[Good fix even before we found the real bug]]
> This convert patch is quite good, as it in fact addressed the 
> metadata-cross-map-boundary bug, even before we found it.

I was totally unaware of this consequence. So this narrows the bug to

* introduced: 3.19.1 (16k nodesize for convert)
* last not fixed: 4.0.1

So anything 4.1+ should be fine.

> [[True fix]]
> IMHO, I still prefer to use mixed block group for btrfs-convert, as that 
> fits better for the use case.

While I don't mind adding mixed-bg support to convert options, I think
we first need to add support to mixed bg balance filters. The typical
filesystem size being converted from extN to btrfs is much larger than
the forced mixed-bg flag (1G nowadays).

> And what we really need is, to keep fixing btrfs-convert and kernel.
> Banning mixed bg for convert case is just avoiding the real cause, and I 
> think that should be the last method.

The allowed convert features were added to the mask if they looked safe
to me at the time.

      parent reply	other threads:[~2015-09-09 13:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22 15:00 Btrfs progs release 4.1 David Sterba
2015-06-22 16:18 ` Goffredo Baroncelli
2015-06-22 18:01   ` David Sterba
2015-06-22 18:18 ` qgroup limit clearing, was " Christian Robottom Reis
2015-06-22 18:18 ` Christian Robottom Reis
2015-06-22 23:55   ` Tsutomu Itoh
2015-06-23  1:55     ` Qu Wenruo
2015-06-23 12:42     ` David Sterba
2015-06-22 20:45 ` Martin Steigerwald
2015-06-23 12:53   ` David Sterba
2015-06-23  9:03 ` Sjoerd
2015-06-23  9:18   ` Qu Wenruo
2015-06-23 14:45   ` David Sterba
2015-06-24 20:26     ` Sjoerd
2015-06-25 13:03       ` David Sterba
2015-09-09  1:34 ` Qu Wenruo
2015-09-09  3:24   ` Qu Wenruo
2015-09-09 10:35     ` Vytautas D
2015-09-09 11:25       ` Duncan
2015-09-09 13:26       ` David Sterba
2015-09-09 13:25     ` David Sterba
2015-09-09 14:01       ` Austin S Hemmelgarn
2015-09-10  0:50       ` Qu Wenruo
2015-09-09 13:19   ` 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=20150909131925.GG8891@suse.cz \
    --to=dsterba@suse.cz \
    --cc=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo@cn.fujitsu.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.