From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Allow more disks missing for RAID10
Date: Wed, 31 Jul 2019 15:23:42 +0200 [thread overview]
Message-ID: <20190731132342.GK28208@twin.jikos.cz> (raw)
In-Reply-To: <052a23bb-428d-3249-d8cb-b508ebca0b62@gmx.com>
On Wed, Jul 31, 2019 at 02:58:02PM +0800, Qu Wenruo wrote:
>
>
> On 2019/7/26 下午6:39, David Sterba wrote:
> > On Fri, Jul 26, 2019 at 07:41:41AM +0800, Qu Wenruo wrote:
> >>
> >>
> >> On 2019/7/26 上午2:37, David Sterba wrote:
> >>> On Thu, Jul 18, 2019 at 02:27:49PM +0800, Qu Wenruo wrote:
> >>>> RAID10 can accept as much as half of its disks to be missing, as long as
> >>>> each sub stripe still has a good mirror.
> >>>
> >>> Can you please make a test case for that?
> >>
> >> Fstests one or btrfs-progs one?
> >
> > For fstests.
>
> OK, that test case in fact exposed a long-existing bug, we can't create
> degraded chunks.
>
> So if we're replacing the missing devices on a 4 disk RAID10 btrfs, we
> will hit ENOSPC as we can't find 4 devices to fulfill a new chunk.
> And it will finally trigger transaction abort.
>
> Please discard this patch until we solve that problem.
Ok, done.
prev parent reply other threads:[~2019-07-31 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 6:27 [PATCH] btrfs: Allow more disks missing for RAID10 Qu Wenruo
2019-07-25 18:37 ` David Sterba
2019-07-25 19:14 ` Austin S. Hemmelgarn
2019-07-25 23:41 ` Qu Wenruo
2019-07-26 10:39 ` David Sterba
2019-07-31 6:58 ` Qu Wenruo
2019-07-31 13:23 ` 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=20190731132342.GK28208@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.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