From: "Lakshmipathi.G" <lakshmipathi.g@gmail.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: btrfs <linux-btrfs@vger.kernel.org>, "dsterba@suse.cz" <dsterba@suse.cz>
Subject: Re: [PATCH v3 00/19] Btrfs-progs offline scrub
Date: Mon, 22 May 2017 15:17:38 +0530 [thread overview]
Message-ID: <CAKuJGC8-VEm-3afkVmWzk+kVdxHZECp1soyksN4fvEJkJkB2GA@mail.gmail.com> (raw)
In-Reply-To: <b57b3e03-fc72-762f-1392-9a4ccafd0fcb@cn.fujitsu.com>
Okay sure, When I find free-time, will run few more combinations and
let you know the details along with any other suggestions/thoughts on
the interface. thanks.
On 5/22/17, Qu Wenruo <quwenruo@cn.fujitsu.com> wrote:
> Good to hear that.
>
> And you could try more combination (although I have done a lot during
> the test) to see if it's good enough to be used as a better scrub
> equivalent.
>
> And of course, any idea on the interface design (--offline under scrub
> or other place) is welcomed.
>
> Thanks,
> Qu
>
> At 05/22/2017 04:30 PM, Lakshmipathi.G wrote:
>> Yes. It detects the injected corruption.
>>
>> #btrfs scrub start --offline /dev/loop6
>> ERROR: data at bytenr 145293312 mirror 0 csum mismatch, have
>> 0x790f1fe1 expect 0xa30cb5c5
>> ERROR: full stripe 145227776 RECOVERABLE: Data stripes corrupted, but
>> P/Q is good
>>
>> Scrub result:
>> Tree bytes scrubbed: 131072
>> Tree extents scrubbed: 8
>> Data bytes scrubbed: 192512
>> Data extents scrubbed: 3
>> Data bytes without csum: 131072
>> Read error: 0
>> Verify error: 0
>> Csum error: 1
>>
>> ----
>> Cheers,
>> Lakshmipathi.G
>>
>>
>
>
>
--
----
Cheers,
Lakshmipathi.G
http://www.giis.co.in http://www.webminal.org
next prev parent reply other threads:[~2017-05-22 9:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 6:20 [PATCH v3 00/19] Btrfs-progs offline scrub Qu Wenruo
2017-03-30 6:20 ` [PATCH v3 01/19] btrfs-progs: raid56: Introduce raid56 header for later recovery usage Qu Wenruo
2017-03-30 6:20 ` [PATCH v3 02/19] btrfs-progs: raid56: Introduce tables for RAID6 recovery Qu Wenruo
2017-03-30 6:20 ` [PATCH v3 03/19] btrfs-progs: raid56: Allow raid6 to recover 2 data stripes Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 04/19] btrfs-progs: raid56: Allow raid6 to recover data and p Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 05/19] btrfs-progs: Introduce wrapper to recover raid56 data Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 06/19] btrfs-progs: Introduce new btrfs_map_block function which returns more unified result Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 07/19] btrfs-progs: Allow __btrfs_map_block_v2 to remove unrelated stripes Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 08/19] btrfs-progs: csum: Introduce function to read out data csums Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 09/19] btrfs-progs: scrub: Introduce structures to support fsck scrub for RAID56 Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 10/19] btrfs-progs: scrub: Introduce function to scrub mirror based tree block Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 11/19] btrfs-progs: scrub: Introduce function to scrub mirror based data blocks Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 12/19] btrfs-progs: scrub: Introduce function to scrub one extent Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 13/19] btrfs-progs: scrub: Introduce function to scrub one data stripe Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 14/19] btrfs-progs: scrub: Introduce function to verify parities Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 15/19] btrfs-progs: extent-tree: Introduce function to check if there is any extent in given range Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 16/19] btrfs-progs: scrub: Introduce function to recover data parity Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 17/19] btrfs-progs: scrub: Introduce a function to scrub one full stripe Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 18/19] btrfs-progs: scrub: Introduce function to check a whole block group Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 19/19] btrfs-progs: fsck: Introduce offline scrub function Qu Wenruo
2017-03-30 6:21 ` [PATCH v3 19/19] btrfs-progs: scrub: " Qu Wenruo
2017-05-09 5:46 ` [PATCH v3 00/19] Btrfs-progs offline scrub Qu Wenruo
2017-05-12 16:34 ` David Sterba
2017-05-13 13:37 ` Lakshmipathi.G
[not found] ` <46db6693-3508-6845-e80f-0db1192d7bd2@cn.fujitsu.com>
2017-05-22 6:27 ` Lakshmipathi.G
[not found] ` <f0ed81f8-a312-72b0-5da1-56cfbc1fa81e@cn.fujitsu.com>
2017-05-22 7:57 ` Lakshmipathi.G
2017-05-22 8:30 ` Lakshmipathi.G
[not found] ` <b57b3e03-fc72-762f-1392-9a4ccafd0fcb@cn.fujitsu.com>
2017-05-22 9:47 ` Lakshmipathi.G [this message]
2017-05-23 14:41 ` Lakshmipathi.G
[not found] ` <cfdab92f-469e-b8f2-8d8b-3a0544d05f57@cn.fujitsu.com>
2017-05-24 3:58 ` Lakshmipathi.G
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=CAKuJGC8-VEm-3afkVmWzk+kVdxHZECp1soyksN4fvEJkJkB2GA@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 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).