From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: dsterba@suse.cz, Neal Gompa <ngompa13@gmail.com>,
David Sterba <dsterba@suse.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] RAID1 with 3- and 4- copies
Date: Thu, 14 Nov 2019 00:13:24 -0500 [thread overview]
Message-ID: <20191114051324.GZ22121@hungrycats.org> (raw)
In-Reply-To: <20191101150908.GU3001@twin.jikos.cz>
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
On Fri, Nov 01, 2019 at 04:09:08PM +0100, David Sterba wrote:
> The raid1c34 patches are not intrusive and could be backported on top of
> 5.3 because all the preparatory work has been merged already.
Indeed, that's how I ended up testing them. I couldn't get the 5.4-rc
kernels to run long enough to do meaningful testing before they locked
up. I tested with 5.3.8 + patches.
I left out the last patch that removes the raid1c3 incompat flag because
5.3 didn't have the block group tree code to apply it to.
I ran my raid1 and raid56 corruption recovery tests modified for raid1c3.
The first test is roughly:
mkfs.btrfs -draid1c3 -mraid1c3 /dev/vd[bcdef]
mount /dev/vdb /test
cp -a 9GB_data /test
sync
sysctl vm.drop_caches=3
diff -r 9GB_data /test
head -c 9g /dev/urandom > /dev/vdb
head -c 9g /dev/urandom > /dev/vdc
sync
sysctl vm.drop_caches=3
diff -r 9GB_data /test
btrfs scrub start -Bd /test
sysctl vm.drop_caches=3
diff -r 9GB_data /test
btrfs scrub start -Bd /test
sysctl vm.drop_caches=3
diff -r 9GB_data /test
First scrub reported a lot of corruption on /dev/vdb and /dev/vdc. Second
scrub reported no errors. diff (all instances) reported no differences.
Second test is:
mkfs.btrfs -draid6 -mraid1c3 /dev/vd[bcdef]
# rest as above...
Similar results: first scrub reported many errors as expected.
Second scrub reported no errors. No diffs.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-11-14 5:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 15:13 [PATCH v3 0/4] RAID1 with 3- and 4- copies David Sterba
2019-10-31 15:13 ` [PATCH v2 1/4] btrfs: add support for 3-copy replication (raid1c3) David Sterba
2019-10-31 15:13 ` [PATCH v2 2/4] btrfs: add support for 4-copy replication (raid1c4) David Sterba
2019-10-31 15:13 ` [PATCH v2 3/4] btrfs: add incompat for raid1 with 3, 4 copies David Sterba
2019-10-31 15:13 ` [PATCH v2 4/4] btrfs: drop incompat bit for raid1c34 after last block group is gone David Sterba
2019-10-31 18:43 ` [PATCH] btrfs-progs: add support for raid1c3 and raid1c4 David Sterba
2019-10-31 18:44 ` [PATCH v3 0/4] RAID1 with 3- and 4- copies David Sterba
2019-11-01 14:54 ` Neal Gompa
2019-11-01 15:09 ` David Sterba
2019-11-03 0:35 ` waxhead
2019-11-04 13:40 ` David Sterba
2019-11-14 5:13 ` Zygo Blaxell [this message]
2019-11-15 10:28 ` David Sterba
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=20191114051324.GZ22121@hungrycats.org \
--to=ce3g8jdj@umail.furryterror.org \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=ngompa13@gmail.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).