linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carsten Aulbert <Carsten.Aulbert@aei.mpg.de>
To: Tarak Anumolu <tarak.a@samsung.com>, linux-raid@vger.kernel.org
Subject: Re: Problem with XOR Engine
Date: Tue, 11 Aug 2015 08:29:53 +0200	[thread overview]
Message-ID: <55C99661.20901@aei.mpg.de> (raw)
In-Reply-To: <loom.20150811T081553-897@post.gmane.org>

Hi Tarak

On 11.08.2015 08:16, Tarak Anumolu wrote:
> I got some problem with the XOR engine while creating the RAID array.
> 

I doubt that you will get much (more) attention if you continue to spam
the list, also with people distributed around the world, expecting a
solid reply within less than 8 hours is at least a bit questionable,
don't you think so?

> 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.
> 
> Without this option everything is working fine.
> 

I think (I'm only a user myself and no developer), without much more
extra information, it will be hard to help, i.e. more information what
kern.log/dmesg shows in both situations, /proc/mdstat output, mdadm
examine, ....

Cheers

Carsten

  reply	other threads:[~2015-08-11  6:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11  6:16 Problem with XOR Engine Tarak Anumolu
2015-08-11  6:29 ` Carsten Aulbert [this message]
     [not found] <22.2C.31182.A9839C55@epcpsbgx2.samsung.com>
2015-08-11 21:05 ` NeilBrown
  -- 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=55C99661.20901@aei.mpg.de \
    --to=carsten.aulbert@aei.mpg.de \
    --cc=linux-raid@vger.kernel.org \
    --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).