From: NeilBrown <neilb@suse.com>
To: Tarak Ramgopal Anumolu <tarak.a@samsung.com>
Cc: linux-raid@vger.kernel.org, sam@bingner.com, hpj@urpla.net
Subject: Re: Problem with XOR Engine
Date: Wed, 12 Aug 2015 07:05:29 +1000 [thread overview]
Message-ID: <20150812070529.7764fa15@noble> (raw)
In-Reply-To: <22.2C.31182.A9839C55@epcpsbgx2.samsung.com>
On Mon, 10 Aug 2015 23:49:46 +0000 (GMT) Tarak Ramgopal Anumolu
<tarak.a@samsung.com> wrote:
> Samsung Enterprise Portal mySingle
>
> Hi
>
>
>
> My name is Tarak.
>
>
>
> I got some problem with the XOR engine while creating the RAID array.
>
>
>
> The parity data is getting corrupted and my system is not able to recognize it and some how we are getting the hard disk error.
>
>
>
> I found the above issue is happening when I enable CONFIG_RAID_ZERO_COPY=y in my Linux configuration.
My Linux doesn't contain a CONFIG_RAID_ZERO_COPY config option.
Maybe you are using a different Linux.
NeilBrown
>
>
>
> Without this option everything is working fine.
>
>
>
> Following are the version details
>
> Linux : 3.0.34
>
> GCC : 4.6.2 (GCC) )
> mdadm : v3.2.5
>
>
>
> I want to know the way to fix the RAID parity error.
>
>
>
> Please help me on this.
>
>
>
>
>
>
>
> Tarak Ramgopal Anumolu
>
> Security Solution Division
>
> SAMSUNG TECHWIN CO.,LTD
>
> Phone : +82-70-7147-8396
>
> Mobile: +82-10-7249-8396
>
> E-mail : tarak.a@samsung.com
>
>
>
next parent reply other threads:[~2015-08-11 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <22.2C.31182.A9839C55@epcpsbgx2.samsung.com>
2015-08-11 21:05 ` NeilBrown [this message]
2015-08-11 6:16 Problem with XOR Engine Tarak Anumolu
2015-08-11 6:29 ` Carsten Aulbert
-- strict thread matches above, loose matches on Subject: below --
2013-03-27 5:17 Need some information about mdadm 3.2.5 Tarak Anumolu
2013-03-27 9:28 ` Hans-Peter Jansen
2013-03-27 10:51 ` Sam Bingner
2015-08-10 23:53 ` Problem with XOR Engine Tarak
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=20150812070529.7764fa15@noble \
--to=neilb@suse.com \
--cc=hpj@urpla.net \
--cc=linux-raid@vger.kernel.org \
--cc=sam@bingner.com \
--cc=tarak.a@samsung.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).