From: "Lakshmipathi.G" <lakshmipathi.g@giis.co.in>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: List of corruption cases for scrub
Date: Mon, 27 Feb 2017 16:31:38 +0530 [thread overview]
Message-ID: <20170227110138.GA2667@giis.co.in> (raw)
In-Reply-To: <e1ce9d74-57e8-8078-11fb-d2e4613428ea@cn.fujitsu.com>
On Mon, Feb 27, 2017 at 11:40:31AM +0800, Qu Wenruo wrote:
>
>
> At 02/24/2017 10:32 AM, Lakshmipathi.G wrote:
> >Hi.
> >
> >I tried to a create list of corruption test scenarios for scrubbing process with RAID5.
> >Here's the list: https://btrfs.wiki.kernel.org/index.php/Scrub_corruption_cases
> >
> >If similar list already exists in btrfs wiki, let me know, I'll move this data
> >to there. Feel free to add/update/delete entries or suggest new corrupt ideas!
>
> What about adding testing result for latest kernel release?
>
> Thanks,
> Qu
True, Ideally, the wiki should have list-corruption cases along with result for
each latest kernel version.
Planning to add more cases, gradually. For example, I think inode object
with RAID5 can be replicated across drives. If thats correct, can scrub
fix those corruption too? cases like this may be more important than other
to-do items like raid5 with features like snapshot/quota etc
I think it should be possible to add test-results for few cases but list has
repeated-cases with different sizes,drives etc for these cases we need some
kind of automated scripts.
Hope to extend the cases first and then start updating results with manual or
automated tests.
Cheers.
Lakshmipathi.G
prev parent reply other threads:[~2017-02-27 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 2:32 List of corruption cases for scrub Lakshmipathi.G
2017-02-24 17:39 ` Goffredo Baroncelli
2017-02-26 13:21 ` Lakshmipathi.G
[not found] ` <e1ce9d74-57e8-8078-11fb-d2e4613428ea@cn.fujitsu.com>
2017-02-27 11:01 ` 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=20170227110138.GA2667@giis.co.in \
--to=lakshmipathi.g@giis.co.in \
--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).