From: "Lakshmipathi.G" <lakshmipathi.g@giis.co.in>
To: kreijack@inwind.it
Cc: linux-btrfs@vger.kernel.org
Subject: Re: List of corruption cases for scrub
Date: Sun, 26 Feb 2017 18:51:28 +0530 [thread overview]
Message-ID: <20170226132128.GA2690@giis.co.in> (raw)
In-Reply-To: <9a5fb7b9-76b3-9848-9c29-8d4aac3fdb7b@libero.it>
On Fri, Feb 24, 2017 at 06:39:20PM +0100, Goffredo Baroncelli wrote:
> Hi,
> On 2017-02-24 03:32, 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!
>
> Thanks for doing that. About the test "Device-corruption", I suppose that you want to test a scenario where one disk fails. If so you do not have to always corrupt "D0" block, but the first block of the file which is stored in the failing disk (which could be different from the D0).
>
Yes, that's right. Updated (Device-corruption) the list now.
> Another scenario which should be tested, is the reshaping of the raid: add a drive (or remove a drive) then re-balance the system (with or without some corruption). IIRC this use the same scrub code.
>
Added this as 'Rebalance-corruption' on the wiki. thanks!
Cheers.
Lakshmipathi.G
next prev parent reply other threads:[~2017-02-26 13:31 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 [this message]
[not found] ` <e1ce9d74-57e8-8078-11fb-d2e4613428ea@cn.fujitsu.com>
2017-02-27 11:01 ` 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=20170226132128.GA2690@giis.co.in \
--to=lakshmipathi.g@giis.co.in \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@vger.kernel.org \
/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).