From: "Lakshmipathi.G" <lakshmipathi.g@gmail.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: btrfs <linux-btrfs@vger.kernel.org>, dsterba <dsterba@suse.cz>
Subject: Re: [PATCH v4 00/20] Btrfs-progs offline scrub
Date: Sun, 18 Jun 2017 11:50:29 +0530 [thread overview]
Message-ID: <CAKuJGC_F2khXb5GT33gTj4Kzah=HZQFVJoW2qExOxk+LBqUCkA@mail.gmail.com> (raw)
In-Reply-To: <20170525062205.11660-1-quwenruo@cn.fujitsu.com>
> For any one who wants to try it, it can be get from my repo:
> https://github.com/adam900710/btrfs-progs/tree/offline_scrub
While running single corruption script receive message like
"REPARIED: corrupted data with good P/Q, repaired" along with
message from script which says "Parity stripe check passed."
complete output here:
https://github.com/Lakshmipathi/btrfs_offline_scrub/blob/master/logs-june18/single_corruption_misc-tests-results.txt
------------
multiple-corruption: While corrupting continuous blocks received:
>Filename=file256k.txt Total Stripes=4 Data Stripe to be corrupted=2,3
..
..//debugfs-tree output ends
>ERROR: full stripe 145358848 CORRUPTED: too many read error or corrupted devices
>ERROR: full stripe 145358848: tolerance: 1, missing: 0, read error: 0, csum error: 2
While corrupting non-continuous blocks:
>Filename=file512k.txt Total Stripes=8 Data Stripe to be corrupted=1,3,5
..
..//debugfs-tree output ends
>full stripe 145227776 REPARIED: corrupted data with good P/Q, repaired
>full stripe 145358848 REPARIED: corrupted data with good P/Q, repaired
>full stripe 145489920 REPARIED: corrupted data with good P/Q, repaired
output for other combinations like :
>Filename=file768k.txt Total Stripes=12 Data Stripe to be corrupted=10,8,6,4
>Filename=file1m.txt Total Stripes=16 Data Stripe to be corrupted=14,12,10,8,7,6
>Filename=file2m.txt Total Stripes=32 Data Stripe to be corrupted=23,22,21,20,19,18,16
>Filename=file4m.txt Total Stripes=64 Data Stripe to be corrupted=34,33,32,31,30,20,18,15,10,8,5
>Filename=file8m.txt Total Stripes=128 Data Stripe to be corrupted=100,90,80,70,60,50,40,30,20,10
can be found here:
https://github.com/Lakshmipathi/btrfs_offline_scrub/blob/master/logs-june18/multiple_corruptions_misc-tests-results.txt
Outputs are looking fine, but more testing required with different
file-types :-) thanks.
----
Cheers,
Lakshmipathi.G
prev parent reply other threads:[~2017-06-18 6:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 6:21 [PATCH v4 00/20] Btrfs-progs offline scrub Qu Wenruo
2017-05-25 6:21 ` [PATCH v4 01/20] btrfs-progs: raid56: Introduce raid56 header for later recovery usage Qu Wenruo
2017-05-31 13:25 ` David Sterba
2017-05-25 6:21 ` [PATCH v4 02/20] btrfs-progs: raid56: Introduce tables for RAID6 recovery Qu Wenruo
2017-05-25 6:21 ` [PATCH v4 03/20] btrfs-progs: raid56: Allow raid6 to recover 2 data stripes Qu Wenruo
2017-05-25 6:21 ` [PATCH v4 04/20] btrfs-progs: raid56: Allow raid6 to recover data and p Qu Wenruo
2017-05-25 6:21 ` [PATCH v4 05/20] btrfs-progs: Introduce wrapper to recover raid56 data Qu Wenruo
2017-05-31 13:52 ` David Sterba
2017-06-01 1:04 ` Qu Wenruo
2017-05-25 6:21 ` [PATCH v4 06/20] btrfs-progs: Introduce new btrfs_map_block function which returns more unified result Qu Wenruo
2017-05-25 6:21 ` [PATCH v4 07/20] btrfs-progs: Allow __btrfs_map_block_v2 to remove unrelated stripes Qu Wenruo
2017-05-25 6:21 ` [PATCH v4 08/20] btrfs-progs: csum: Introduce function to read out data csums Qu Wenruo
2017-05-25 6:21 ` [PATCH v4 09/20] btrfs-progs: scrub: Introduce structures to support offline scrub for RAID56 Qu Wenruo
2017-05-25 6:21 ` [PATCH v4 10/20] btrfs-progs: scrub: Introduce functions to scrub mirror based tree block Qu Wenruo
2017-05-25 6:21 ` [PATCH v4 11/20] btrfs-progs: scrub: Introduce functions to scrub mirror based data blocks Qu Wenruo
2017-05-25 6:21 ` [PATCH v4 12/20] btrfs-progs: scrub: Introduce function to scrub one mirror-based extent Qu Wenruo
2017-05-25 6:21 ` [PATCH v4 13/20] btrfs-progs: scrub: Introduce function to scrub one data stripe Qu Wenruo
2017-05-25 6:21 ` [PATCH v4 14/20] btrfs-progs: scrub: Introduce function to verify parities Qu Wenruo
2017-05-25 6:22 ` [PATCH v4 15/20] btrfs-progs: extent-tree: Introduce function to check if there is any extent in given range Qu Wenruo
2017-05-25 6:22 ` [PATCH v4 16/20] btrfs-progs: scrub: Introduce function to recover data parity Qu Wenruo
2017-05-25 6:22 ` [PATCH v4 17/20] btrfs-progs: scrub: Introduce helper to write a full stripe Qu Wenruo
2017-05-25 6:22 ` [PATCH v4 18/20] btrfs-progs: scrub: Introduce a function to scrub one " Qu Wenruo
2017-05-25 6:22 ` [PATCH v4 19/20] btrfs-progs: scrub: Introduce function to check a whole block group Qu Wenruo
2017-05-25 6:22 ` [PATCH v4 20/20] btrfs-progs: scrub: Introduce offline scrub function Qu Wenruo
2017-05-26 18:37 ` [PATCH v4 00/20] Btrfs-progs offline scrub Goffredo Baroncelli
2017-05-29 0:21 ` Qu Wenruo
2017-05-29 16:52 ` Goffredo Baroncelli
2017-05-30 18:54 ` David Sterba
2017-05-31 14:07 ` David Sterba
2017-06-18 6:20 ` Lakshmipathi.G [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='CAKuJGC_F2khXb5GT33gTj4Kzah=HZQFVJoW2qExOxk+LBqUCkA@mail.gmail.com' \
--to=lakshmipathi.g@gmail.com \
--cc=dsterba@suse.cz \
--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.