<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.linux.raid">
    <title>gmane.linux.raid</title>
    <link>http://blog.gmane.org/gmane.linux.raid</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38585"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38584"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38583"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38582"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38579"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38576"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38573"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38571"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38566"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38564"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38561"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38557"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38555"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38553"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38551"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38544"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38542"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38528"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38526"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.linux.raid/38525"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38585">
    <title>[PATCH 2/2] md/raid456:Add interface for contorling eject rdev when re-write failed.</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38585</link>
    <description>&lt;pre&gt;When RAID-4/5/6 readed fail and if raid did not degrade,it will
compute,re-write and re-read.If re-read error,it will to eject the rdev.
If so, raid will recovery.
At present,disks are larger,so recovery will take a long time.
It will increasing the opportunity to become failed.
So add a interface using sysfs,to control the number of max re-write
errors.
The default value is zero,as the origin action which met re-write
error to eject the rdev.

Signed-off-by: majianpeng &amp;lt;majianpeng&amp;lt; at &amp;gt;gmail.com&amp;gt;
---
 drivers/md/md.c    |   35 +++++++++++++++++++++++++++++++++++
 drivers/md/md.h    |    2 ++
 drivers/md/raid5.c |   20 ++++++++++++--------
 3 files changed, 49 insertions(+), 8 deletions(-)

diff --git a/drivers/md/md.c b/drivers/md/md.c
index 1c2f904..cd399ec 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -81,6 +81,13 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static struct workqueue_struct *md_misc_wq;
  */
 #define MD_DEFAULT_MAX_CORRECTED_READ_ERRORS 20
 /*
+ * Current RAID-4,5,6 read failed and then try to compter and rewrite,
+ * reread,if &lt;/pre&gt;</description>
    <dc:creator>majianpeng</dc:creator>
    <dc:date>2012-05-26T02:54:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38584">
    <title>[PATCH 1/2] md/raid456: When readed error and raid was degraded,it try to set badsector, not ejecting the rdev.</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38584</link>
    <description>&lt;pre&gt;In order to prevent the degraded raid from becaming fail,we should first
set badsector instead of ejecting the rdev when read fail.

Signed-off-by: majianpeng &amp;lt;majianpeng&amp;lt; at &amp;gt;gmail.com&amp;gt;
---
 drivers/md/raid5.c |   10 ++++++++--
 1 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index d267672..89cfd73 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1737,6 +1737,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static void raid5_end_read_request(struct bio * bi, int error)
 } else {
 const char *bdn = bdevname(rdev-&amp;gt;bdev, b);
 int retry = 0;
+int set_bad = 0;
 
 clear_bit(R5_UPTODATE, &amp;amp;sh-&amp;gt;dev[i].flags);
 atomic_inc(&amp;amp;rdev-&amp;gt;read_errors);
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1748,7 +1749,8 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static void raid5_end_read_request(struct bio * bi, int error)
 mdname(conf-&amp;gt;mddev),
 (unsigned long long)s,
 bdn);
-else if (conf-&amp;gt;mddev-&amp;gt;degraded &amp;gt;= conf-&amp;gt;max_degraded)
+else if (conf-&amp;gt;mddev-&amp;gt;degraded &amp;gt;= conf-&amp;gt;max_degraded) {
+set_bad = 1;
 printk_ratelimited(
 KERN_WARNING
 "md/raid:%s: read erro&lt;/pre&gt;</description>
    <dc:creator>majianpeng</dc:creator>
    <dc:date>2012-05-26T02:53:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38583">
    <title>[PATCH 0/2] Modify read error handle for RAID-4,5,6.</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38583</link>
    <description>&lt;pre&gt;When RAID-4,5,6 degraded and met read-error, it will eject the rdev.And then
the RAID will fail and lost data.Because the function of set-badsector,when 
this occur,it will set-badsector,not ejecting the rdev.
When RAID-4,5,6 met read-error, it will re-write if RAID was not degrade.But if 
re-write error,it will eject the rdev and RAID will degrade and it will take too
long time for recoverying.So I add judgement for controling how may re-write-error
can eject the rdev.

I do those for flexible controling the read-error for different situation.


majianpeng (2):
  md/raid456: When readed error and raid was degraded,it try to
    set badsector, not ejecting the rdev.
  md/raid456:Add interface for contorling eject rdev when re-write
    failed.

 drivers/md/md.c    |   35 +++++++++++++++++++++++++++++++++++
 drivers/md/md.h    |    2 ++
 drivers/md/raid5.c |   28 +++++++++++++++++++---------
 3 files changed, 56 insertions(+), 9 deletions(-)

&lt;/pre&gt;</description>
    <dc:creator>majianpeng</dc:creator>
    <dc:date>2012-05-26T02:52:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38582">
    <title>The $1,549 per day ZERO traffic system (UPDATE) Recommends Advanced Sports to you</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38582</link>
    <description>&lt;pre&gt;Email        :sniperxsystem&amp;lt; at &amp;gt;support.com
Friend Name  :Friend
Friend Email :linux-raid&amp;lt; at &amp;gt;vger.kernel.org
comment      :

Listen to this... pretty crazy...

So many people rushed to download this 
$530k/year system yesterday...

That they crashed the ENTIRE server!

=&amp;gt;&amp;gt;http://www.sniperxsystem.com/?code=4fbea9cb964f6&amp;lt;&amp;lt;=

(The site was down ALL day) Pretty crazy. 

... The "ghetto" video alone has sent shockwaves 
through the Clickbank community.

Can you believe THIS guy's one of Clickbanks
biggest super affiliates?

=&amp;gt;&amp;gt;http://www.sniperxsystem.com/?code=4fbea9cb964f6&amp;lt;&amp;lt;=

Talk soon

P.S. This is **BRAND NEW**...

It works and it's made $1,549.87 a DAY for 
the past 739 days in a ROW!

No PPC, no PPV, no CPA, no so-called 'push
button softwares' scams, no 'loopholes'...

Something TOTALLY different.

Check it out (fast, while it's still open):

=&amp;gt;&amp;gt;http://www.sniperxsystem.com/?code=4fbea9cb964f6&amp;lt;&amp;lt;=




--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo&amp;lt; at &amp;gt;v&lt;/pre&gt;</description>
    <dc:creator>sniperxsystem&lt; at &gt;support.com</dc:creator>
    <dc:date>2012-05-26T01:51:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38579">
    <title>Friend,Could you "build-up" your own energy? Recommends Advanced Sports to you</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38579</link>
    <description>&lt;pre&gt;Email        :danniel&amp;lt; at &amp;gt;gmail.com
Friend Name  :Friend
Friend Email :linux-raid&amp;lt; at &amp;gt;vger.kernel.org
comment      :


Hi Friend,

I'm sure you already found out the rumours that some
people make their own energy.
Some of them slash the energy bill by half.
Some of them cut the bill completely.
Some even make the electric company pay them(!).
That's why I was ecstatic when I found this website:

http://www.greenhomemade.com/?code=4fbd5d3bbfcd4 

I read every single word, and boy... this stuff really
got me all curious. It seems it's actually very easy 
and cheap to build and use a renewable energy system.

Anyway, I went ahead and bought their package.
I couldn't resisted... It sounds too good to be true,
yet if this turns out to be "real", then this is BIG.

I'm so enthusiasted about this, that I thought to just
send you a link so you get to see it for yourself:

http://www.greenhomemade.com/?code=4fbd5d3bbfcd4 

To a better life,

Danniel Guedotte

PS: Friend, they give a 60-day guarantee. 
You risk nothing. 
But &lt;/pre&gt;</description>
    <dc:creator>danniel&lt; at &gt;gmail.com</dc:creator>
    <dc:date>2012-05-25T18:57:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38576">
    <title>Tercume edilecek metinleriniz hakkinda</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38576</link>
    <description>&lt;pre&gt;Sayin ilgili,
 
Biz 10 yili askin bir süredir internet üzerinden profesyonel olarak
CEVIRI / TERCUME HIZMETLERI veren bir kurulusuz. Kurulusumuzun 10. yili  
serefine firmalara ozel, sayfasi 12 TL+KDV'lik bir kampanya hazirladik.

Sadece INGILIZCE - TURKCE ve TURKCE - INGILIZCE cevirilerde gecerli olan ve 
kisa bir sure 
devam edecek bu cazip fiyat avantajindan yararlanmak icin
lutfen bizi hemen simdi arayiniz veya bir e-posta gonderiniz. Diger diller 
icin lutfen fiyat sorunuz.

Not: 1 sayfa = 1000 karakter veya 180 kelimelik dunya standardi 
esas alinmistir. Teknik metinlerde %25 fark alinacaktir. Diger diller icin 
lutfen fiyat aliniz.

Saygilarimizla,
 
Levent Turer,  
Genel Koordinator
Turer Ceviri Hizmetleri

e-posta: info&amp;lt; at &amp;gt;turerceviri.com 
web: www.turerceviri.com 
Tel: 0232 421 13 60
Faks: 0232 421 13 32

Bu e-mail size otomatik olarak, yani bir reklam amaciyla rastgele 
gonderilmemistir.  Eger bizden bu veya benzeri bir konuda 
bir daha e-posta almak istemiyorsaniz, lutfen bize bildiriniz. Size 
ra&lt;/pre&gt;</description>
    <dc:creator>info&lt; at &gt;turerceviri.com</dc:creator>
    <dc:date>2012-05-23T13:14:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38573">
    <title>Friend,Could you "build-up" your own energy? Recommends Advanced Sports to you</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38573</link>
    <description>&lt;pre&gt;Email        :danniel&amp;lt; at &amp;gt;gmail.com
Friend Name  :Friend
Friend Email :linux-raid&amp;lt; at &amp;gt;vger.kernel.org
comment      :


Hi Friend,

I'm sure you already found out the rumours that some
people make their own energy.
Some of them slash the energy bill by half.
Some of them cut the bill completely.
Some even make the electric company pay them(!).
That's why I was ecstatic when I found this website:

http://www.greenhomemade.com/?code=4fbd5d3bbfcd4 

I read every single word, and boy... this stuff really
got me all curious. It seems it's actually very easy 
and cheap to build and use a renewable energy system.

Anyway, I went ahead and bought their package.
I couldn't resisted... It sounds too good to be true,
yet if this turns out to be "real", then this is BIG.

I'm so enthusiasted about this, that I thought to just
send you a link so you get to see it for yourself:

http://www.greenhomemade.com/?code=4fbd5d3bbfcd4 

To a better life,

Danniel Guedotte

PS: Friend, they give a 60-day guarantee. 
You risk nothing. 
But &lt;/pre&gt;</description>
    <dc:creator>danniel&lt; at &gt;gmail.com</dc:creator>
    <dc:date>2012-05-25T15:37:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38571">
    <title>[PATCH 0/4] More test suite enchancements</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38571</link>
    <description>&lt;pre&gt;From: Jes Sorensen &amp;lt;Jes.Sorensen&amp;lt; at &amp;gt;redhat.com&amp;gt;

Hi,

Here's another set of test suite enhancements. In particular I have
added --logdir and --save-logs, plus --no-error  which allows for one
to run all the tests, without stopping after the first error. This
makes it easier to run the test suite in an automated fashion and
getting a report of all the tests that may have failed. I also did a
bit to make the --help output more useful.

Cheers,
Jes

Jes Sorensen (4):
  Add support for saving log files in test script
  Add --no-error argument to 'test'
  Improve --help message from test
  Move setup code to a function and introduce matching cleanup argument

 test |  113 ++++++++++++++++++++++++++++++++++++++++++++++++------------------
 1 files changed, 82 insertions(+), 31 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo&amp;lt; at &amp;gt;vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Jes.Sorensen&lt; at &gt;redhat.com</dc:creator>
    <dc:date>2012-05-25T15:24:04</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38566">
    <title>[PATCH] imsm: fix: correct checking volume's degradation</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38566</link>
    <description>&lt;pre&gt;We do not check the return value of sysfs_get_ll() now. It is wrong.
If reading of the sysfs "degraded" key does not succeed,
the "new_degraded" variable will not be initiated
and accidentally it can have the value of "degraded" variable.
In that case the change of degradation will not be checked.

It happens if mdadm is compiled with gcc's "-fstack-protector" option
when one tries to stop a volume under reshape (e.g. OLCE).
Reshape seems to be finished then (metadata is in normal/clean state)
but it is not finished, it is broken and data are corrupted.

Now we always check the return value of sysfs_get_ll().
Even if reading of the sysfs "degraded" key does not succeed
(rv == -1) the change of degradation will be checked.

Signed-off-by: Lukasz Dorau &amp;lt;lukasz.dorau&amp;lt; at &amp;gt;intel.com&amp;gt;
---
 super-intel.c |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/super-intel.c b/super-intel.c
index 6c87e20..07ab9ae 100644
--- a/super-intel.c
+++ b/super-intel.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -10370,8 +10370,10 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int check_degra&lt;/pre&gt;</description>
    <dc:creator>Lukasz Dorau</dc:creator>
    <dc:date>2012-05-25T13:06:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38564">
    <title>[PATCH] mdadm: Fix Segmentation fault.</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38564</link>
    <description>&lt;pre&gt;In function write_init_super1():
If "rv = store_super1(st, di-&amp;gt;fd)" return error and the di is the last.
Then the di = NULL &amp;amp;&amp;amp; rv &amp;gt; 0, so exec:
if (rv)
    fprintf(stderr, Name ": Failed to write metadata to%s\n",
      di-&amp;gt;devname);
will be segmentation fault.

Signed-off-by: majianpeng &amp;lt;majianpeng&amp;lt; at &amp;gt;gmail.com&amp;gt;
---
 super1.c |    2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)

diff --git a/super1.c b/super1.c
index 4f20cc3..37b7a90 100644
--- a/super1.c
+++ b/super1.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1242,6 +1242,8 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static int write_init_super1(struct supertype *st)
 rv = st-&amp;gt;ss-&amp;gt;write_bitmap(st, di-&amp;gt;fd);
 close(di-&amp;gt;fd);
 di-&amp;gt;fd = -1;
+if (rv)
+goto error_out;
 }
 error_out:
 if (rv)
&lt;/pre&gt;</description>
    <dc:creator>majianpeng</dc:creator>
    <dc:date>2012-05-25T11:49:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38561">
    <title>very slow file deletion on an SSD</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38561</link>
    <description>&lt;pre&gt;Hi folks:

   Just ran into this (see posted output at bottom).  3.2.14 kernel, MD 
RAID 5, xfs file system.  Not sure (precisely) where the problem is, 
hence posting to both lists.

  [root&amp;lt; at &amp;gt;siFlash ~]# cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4]
md22 : active raid5 sdl[0] sds[7] sdx[6] sdu[5] sdk[4] sdz[3] sdw[2] sdr[1]
       1641009216 blocks super 1.2 level 5, 32k chunk, algorithm 2 [8/8] 
[UUUUUUUU]

md20 : active raid5 sdh[0] sdf[7] sdm[6] sdd[5] sdc[4] sde[3] sdi[2] sdg[1]
       1641009216 blocks super 1.2 level 5, 32k chunk, algorithm 2 [8/8] 
[UUUUUUUU]

md21 : active raid5 sdy[0] sdq[7] sdp[6] sdo[5] sdn[4] sdj[3] sdv[2] sdt[1]
       1641009216 blocks super 1.2 level 5, 32k chunk, algorithm 2 [8/8] 
[UUUUUUUU]

md0 : active raid1 sdb1[1] sda1[0]
       93775800 blocks super 1.0 [2/2] [UU]
       bitmap: 1/1 pages [4KB], 65536KB chunk


md2* are SSD RAID5 arrays we are experimenting with.  Xfs file systems 
atop them:

[root&amp;lt; at &amp;gt;siFlash ~]# mount | grep md2
/dev/md20 on /data/1 t&lt;/pre&gt;</description>
    <dc:creator>Joe Landman</dc:creator>
    <dc:date>2012-05-25T10:37:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38557">
    <title>The $1,549 per day ZERO traffic system (UPDATE) Recommends Advanced Sports to you</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38557</link>
    <description>&lt;pre&gt;Email        :sniperxsystem&amp;lt; at &amp;gt;support.com
Friend Name  :Friend
Friend Email :linux-raid&amp;lt; at &amp;gt;vger.kernel.org
comment      :

Listen to this... pretty crazy...

So many people rushed to download this 
$530k/year system yesterday...

That they crashed the ENTIRE server!

=&amp;gt;&amp;gt;http://www.sniperxsystem.com/?code=4fbea9cb964f6&amp;lt;&amp;lt;=

(The site was down ALL day) Pretty crazy. 

... The "ghetto" video alone has sent shockwaves 
through the Clickbank community.

Can you believe THIS guy's one of Clickbanks
biggest super affiliates?

=&amp;gt;&amp;gt;http://www.sniperxsystem.com/?code=4fbea9cb964f6&amp;lt;&amp;lt;=

Talk soon

P.S. This is **BRAND NEW**...

It works and it's made $1,549.87 a DAY for 
the past 739 days in a ROW!

No PPC, no PPV, no CPA, no so-called 'push
button softwares' scams, no 'loopholes'...

Something TOTALLY different.

Check it out (fast, while it's still open):

=&amp;gt;&amp;gt;http://www.sniperxsystem.com/?code=4fbea9cb964f6&amp;lt;&amp;lt;=




--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo&amp;lt; at &amp;gt;v&lt;/pre&gt;</description>
    <dc:creator>sniperxsystem&lt; at &gt;support.com</dc:creator>
    <dc:date>2012-05-25T01:33:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38555">
    <title>Hi! Is "container" more efficient in terms of I/O op. numbers ...</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38555</link>
    <description>&lt;pre&gt;   ... then several "stand-alone" RAIDs on the same HDDs? -- Say, when
using write intent bitmaps.

&lt;/pre&gt;</description>
    <dc:creator>Igor Podlesny</dc:creator>
    <dc:date>2012-05-24T15:30:54</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38553">
    <title>Activate your free commission shop now Recommends Advanced Sports to you</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38553</link>
    <description>&lt;pre&gt;Email        :kimtan&amp;lt; at &amp;gt;gmail.com
Friend Name  :Friend
Friend Email :linux-raid&amp;lt; at &amp;gt;vger.kernel.org
comment      :

Hey,

Your commission shop is ready.
Activate your free commission shop now:

==&amp;gt; http://bit.ly/KUXNMS

In a few minutes, your commission shop will be ready, 
attracting buyers from all around the world.

And each shop is designed to suck commissions and sales 
for you automatically. 

This is the first time this revolutionary technique is applied.

So don't delay. Activate your commission shop now:

==&amp;gt; http://bit.ly/KUXNMS

Sincerely,
Kim Tan



--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo&amp;lt; at &amp;gt;vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>kimtan&lt; at &gt;gmail.com</dc:creator>
    <dc:date>2012-05-24T12:00:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38551">
    <title>Activate your free commission shop now Recommends Advanced Sports to you</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38551</link>
    <description>&lt;pre&gt;Email        :kimtan&amp;lt; at &amp;gt;gmail.com
Friend Name  :Friend
Friend Email :linux-raid&amp;lt; at &amp;gt;vger.kernel.org
comment      :

Hey,

Your commission shop is ready.
Activate your free commission shop now:

==&amp;gt; http://bit.ly/KUXNMS

In a few minutes, your commission shop will be ready, 
attracting buyers from all around the world.

And each shop is designed to suck commissions and sales 
for you automatically. 

This is the first time this revolutionary technique is applied.

So don't delay. Activate your commission shop now:

==&amp;gt; http://bit.ly/KUXNMS

Sincerely,
Kim Tan



--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo&amp;lt; at &amp;gt;vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>kimtan&lt; at &gt;gmail.com</dc:creator>
    <dc:date>2012-05-24T06:03:16</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38544">
    <title>[PATCH] Increase minimum chunk size in testsuite to 64kB</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38544</link>
    <description>&lt;pre&gt;
When running the mdadm testsuite on ppc64 with a 64kB page size I
see a couple of failures because the chunk size is smaller than a
page.

Bump the chunksize to 64kB to fix these failures.

Signed-off-by: Anton Blanchard &amp;lt;anton&amp;lt; at &amp;gt;samba.org&amp;gt;
---

diff --git a/tests/02r5grow b/tests/02r5grow
index f9fd571..b91ffcd 100644
--- a/tests/02r5grow
+++ b/tests/02r5grow
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -2,7 +2,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 
 # create a small raid5 array, make it larger.  Then make it smaller
 
-mdadm -CR $md0 -e0.90 --level raid5 --chunk=32 --raid-disks 3 --size $[size/2] $dev1 $dev2 $dev3 
+mdadm -CR $md0 -e0.90 --level raid5 --chunk=64 --raid-disks 3 --size $[size/2] $dev1 $dev2 $dev3 
 check wait
 check state UUU
 testdev $md0 2 $[size/2] 32
diff --git a/tests/02r6grow b/tests/02r6grow
index 3f53904..38c7781 100644
--- a/tests/02r6grow
+++ b/tests/02r6grow
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -2,7 +2,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 
 # create a small raid6 array, make it larger.  Then make it smaller
 
-mdadm -CR $md0 -e 0.90 --level raid6 --chunk=32 --raid-disks 4 --size $[size/2] $dev1 $dev2 $dev3 $dev4 
+mda&lt;/pre&gt;</description>
    <dc:creator>Anton Blanchard</dc:creator>
    <dc:date>2012-05-24T05:10:47</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38542">
    <title>[PATCH] lib/raid6: fix sparse warnings in recovery functions</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38542</link>
    <description>&lt;pre&gt;Make the recovery functions static to fix the following sparse warnings:

lib/raid6/recov.c:25:6: warning: symbol 'raid6_2data_recov_intx1' was
not declared. Should it be static?
lib/raid6/recov.c:69:6: warning: symbol 'raid6_datap_recov_intx1' was
not declared. Should it be static?
lib/raid6/recov_ssse3.c:22:6: warning: symbol 'raid6_2data_recov_ssse3'
was not declared. Should it be static?
lib/raid6/recov_ssse3.c:197:6: warning: symbol 'raid6_datap_recov_ssse3'
was not declared. Should it be static?

Reported-by: Fengguang Wu &amp;lt;fengguang.wu&amp;lt; at &amp;gt;intel.com&amp;gt;
Signed-off-by: Jim Kukunas &amp;lt;james.t.kukunas&amp;lt; at &amp;gt;linux.intel.com&amp;gt;
---
 lib/raid6/recov.c       |    7 ++++---
 lib/raid6/recov_ssse3.c |    7 ++++---
 2 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/lib/raid6/recov.c b/lib/raid6/recov.c
index 1805a5c..a95bccb 100644
--- a/lib/raid6/recov.c
+++ b/lib/raid6/recov.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -22,8 +22,8 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt;
 #include &amp;lt;linux/raid/pq.h&amp;gt;
 
 /* Recover two failed data blocks. */
-void raid6_2data_recov_intx1(int disks, size_t byte&lt;/pre&gt;</description>
    <dc:creator>Jim Kukunas</dc:creator>
    <dc:date>2012-05-24T04:54:18</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38528">
    <title>[Training] Here's how to profit $600 a day Recommends Advanced Sports to you</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38528</link>
    <description>&lt;pre&gt;Email        :christian&amp;lt; at &amp;gt;aol.com
Friend Name  :Friend
Friend Email :linux-raid&amp;lt; at &amp;gt;vger.kernel.org
comment      :

Hey,

I've got a treat for you today.

You're about to receive INSTANT
ACCESS to some free training on
how you can profit up to $600 a day

=&amp;gt; http://www.bank-blogging.com/?code=4fbce89b05ddc 


There is no cost. 

Talk Soon,

Christian



=&amp;gt; http://www.bank-blogging.com/?code=4fbce89b05ddc 



--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo&amp;lt; at &amp;gt;vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>christian&lt; at &gt;aol.com</dc:creator>
    <dc:date>2012-05-23T20:14:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38526">
    <title>Sequential writing to degraded RAID6 causing a lot of reading</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38526</link>
    <description>&lt;pre&gt;Hello boys,

I am running some RAID6 arrays in degraded mode, one with
left-symmetry layout and one with left-symmetry-6 layout. I am
experiencing (potentially strange) behavior that degrades performance
of both arrays.

When I am writing sequentially a lot of data to healthy RAID5 array,
it also reads internally a bit of data. I have data on arrays, so I
only write through the filesystem. So I am not sure what causing the
reads, if writing through filesystem potentially causes skipping and
not writing whole stripes  or sometimes timing causes that the whole
stripe is not written at the same time. But anyway there is only a
small ratio of reads and the performance is almost OK.

I cant test it with full healthy RAID6 array, because I dont have any
at the moment.

But when I write sequentially to RAID6 without one drive (again
through filesystem) I get almost exactly the same amount of internal
reads as writes. Is it by design and is this expected behaviour? Why
does it behave like this? It should behave exac&lt;/pre&gt;</description>
    <dc:creator>Patrik Horník</dc:creator>
    <dc:date>2012-05-23T19:01:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38525">
    <title>[Training] Here's how to profit $600 a day Recommends Advanced Sports to you</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38525</link>
    <description>&lt;pre&gt;Email        :christian&amp;lt; at &amp;gt;aol.com
Friend Name  :Friend
Friend Email :linux-raid&amp;lt; at &amp;gt;vger.kernel.org
comment      :

Hey,

I've got a treat for you today.

You're about to receive INSTANT
ACCESS to some free training on
how you can profit up to $600 a day

=&amp;gt; http://www.bank-blogging.com/?code=4fbce89b05ddc 


There is no cost. 

Talk Soon,

Christian



=&amp;gt; http://www.bank-blogging.com/?code=4fbce89b05ddc 



--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo&amp;lt; at &amp;gt;vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>christian&lt; at &gt;aol.com</dc:creator>
    <dc:date>2012-05-23T16:36:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.linux.raid/38522">
    <title>[PATCH] md/raid456:Remove the judgement atomic_read(&amp;rdev-&gt;read_errors).</title>
    <link>http://comments.gmane.org/gmane.linux.raid/38522</link>
    <description>&lt;pre&gt;It isn't necessary to judge.Because the atomic_read and atomic_set is excuce same cpu. So
read_errors is zero or not, directly set it zero.
Signed-off-by: majianpeng &amp;lt;majianpeng&amp;lt; at &amp;gt;gmail.com&amp;gt;
---
 drivers/md/raid5.c |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index f351422..1fe2def 100644
--- a/drivers/md/raid5.c
+++ b/drivers/md/raid5.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1690,8 +1690,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static void raid5_end_read_request(struct bio * bi, int error)
 clear_bit(R5_ReadError, &amp;amp;sh-&amp;gt;dev[i].flags);
 clear_bit(R5_ReWrite, &amp;amp;sh-&amp;gt;dev[i].flags);
 }
-if (atomic_read(&amp;amp;rdev-&amp;gt;read_errors))
-atomic_set(&amp;amp;rdev-&amp;gt;read_errors, 0);
+atomic_set(&amp;amp;rdev-&amp;gt;read_errors, 0);
 } else {
 const char *bdn = bdevname(rdev-&amp;gt;bdev, b);
 int retry = 0;
&lt;/pre&gt;</description>
    <dc:creator>majianpeng</dc:creator>
    <dc:date>2012-05-23T12:38:16</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.linux.raid">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.raid</link>
  </textinput>
</rdf:RDF>

