<?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://permalink.gmane.org/gmane.linux.raid">
    <title>gmane.linux.raid</title>
    <link>http://permalink.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://permalink.gmane.org/gmane.linux.raid/38585"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38584"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38583"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38582"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38581"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38580"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38579"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38578"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38577"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38576"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38575"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38574"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38573"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38572"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38571"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38570"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38569"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38568"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38567"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.raid/38566"/>
      </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://permalink.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://permalink.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://permalink.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://permalink.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://permalink.gmane.org/gmane.linux.raid/38583">
    <title>[PATCH 0/2] Modify read error handle for RAID-4,5,6.</title>
    <link>http://permalink.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://permalink.gmane.org/gmane.linux.raid/38582">
    <title>The $1,549 per day ZERO traffic system (UPDATE) Recommends Advanced Sports to you</title>
    <link>http://permalink.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://permalink.gmane.org/gmane.linux.raid/38581">
    <title>Re: raid 10f2 vs 1 on 2 drives</title>
    <link>http://permalink.gmane.org/gmane.linux.raid/38581</link>
    <description>&lt;pre&gt;in my tests with a mysql and similar database scenarios where write /
read are near 50% / 50% (many updates/inserts and many selects) the
best raid is 1
where scenario is 10%write / 90% read
raid 10far is better (if not degraded or out of sync)


just two scenarios to help 'what's better'  question

2012/5/25 Bill Davidsen &amp;lt;davidsen&amp;lt; at &amp;gt;tmr.com&amp;gt;:



&lt;/pre&gt;</description>
    <dc:creator>Roberto Spadim</dc:creator>
    <dc:date>2012-05-25T19:40:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.raid/38580">
    <title>Re: raid 10f2 vs 1 on 2 drives</title>
    <link>http://permalink.gmane.org/gmane.linux.raid/38580</link>
    <description>&lt;pre&gt;There _is_ no extra head motion. The location of consecutive blocks is different 
on each drive, but as I read the mapping function the distance between blocks on 
the same drive will be about the same, so amount of head motion (both number and 
distance) is the same on each drive, but the location of that motion is not the 
same.

One drive may be seeking at the outer edge of the platter while another seeks 
near the spindle, but there's the same amount of seeking on each.


&lt;/pre&gt;</description>
    <dc:creator>Bill Davidsen</dc:creator>
    <dc:date>2012-05-25T19:03:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.raid/38579">
    <title>Friend,Could you "build-up" your own energy? Recommends Advanced Sports to you</title>
    <link>http://permalink.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://permalink.gmane.org/gmane.linux.raid/38578">
    <title>Re: very slow file deletion on an SSD</title>
    <link>http://permalink.gmane.org/gmane.linux.raid/38578</link>
    <description>&lt;pre&gt;
Discard is not enabled by default.

--
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>Christoph Hellwig</dc:creator>
    <dc:date>2012-05-25T16:59:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.raid/38577">
    <title>Re: very slow file deletion on an SSD</title>
    <link>http://permalink.gmane.org/gmane.linux.raid/38577</link>
    <description>&lt;pre&gt;
[...]



[...]


Ok, will do a respin over the weekend and try from there.  Thanks!

Joe


&lt;/pre&gt;</description>
    <dc:creator>Joe Landman</dc:creator>
    <dc:date>2012-05-25T16:54:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.raid/38576">
    <title>Tercume edilecek metinleriniz hakkinda</title>
    <link>http://permalink.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://permalink.gmane.org/gmane.linux.raid/38575">
    <title>Re: very slow file deletion on an SSD</title>
    <link>http://permalink.gmane.org/gmane.linux.raid/38575</link>
    <description>&lt;pre&gt;Hey Joe,

On Fri, May 25, 2012 at 06:37:05AM -0400, Joe Landman wrote:

There are a couple recent fixes related to discard that are probably
appropriate for 3.2-stable.

commit b1c770c273a4787069306fc82aab245e9ac72e9d
Author: Dave Chinner &amp;lt;dchinner&amp;lt; at &amp;gt;redhat.com&amp;gt;
Date:   Wed Dec 21 00:07:42 2011 +0000

    xfs: fix endian conversion issue in discard code
    
    When finding the longest extent in an AG, we read the value directly
    out of the AGF buffer without endian conversion. This will give an
    incorrect length, resulting in FITRIM operations potentially not
    trimming everything that it should.
    
    Signed-off-by: Dave Chinner &amp;lt;dchinner&amp;lt; at &amp;gt;redhat.com&amp;gt;
    Reviewed-by: Christoph Hellwig &amp;lt;hch&amp;lt; at &amp;gt;lst.de&amp;gt;
    Signed-off-by: Ben Myers &amp;lt;bpm&amp;lt; at &amp;gt;sgi.com&amp;gt;

commit a66d636385d621e98a915233250356c394a437de
Author: Dave Chinner &amp;lt;dchinner&amp;lt; at &amp;gt;redhat.com&amp;gt;
Date:   Thu Mar 22 05:15:12 2012 +0000

    xfs: fix fstrim offset calculations
    
    xfs_ioc_fstrim() doesn't treat the incoming offset and length
    correctly. It &lt;/pre&gt;</description>
    <dc:creator>Ben Myers</dc:creator>
    <dc:date>2012-05-25T16:57:19</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.raid/38574">
    <title>Re: Sequential writing to degraded RAID6 causing a lot of reading</title>
    <link>http://permalink.gmane.org/gmane.linux.raid/38574</link>
    <description>&lt;pre&gt;So Neil,

what do you think? Is this working as intended in this configuration?
If not, where can be problem?

BTW one other diff between my RAID5 and RAID6 I did not mention is
that I have LVM between filesystem and RAID6. There is no LVM in RAID5
case.

Thanks.

Patrik

On Thu, May 24, 2012 at 2:37 PM, Patrik Horník &amp;lt;patrik&amp;lt; at &amp;gt;dsl.sk&amp;gt; wrote:
--
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>Patrik Horník</dc:creator>
    <dc:date>2012-05-25T16:07:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.raid/38573">
    <title>Friend,Could you "build-up" your own energy? Recommends Advanced Sports to you</title>
    <link>http://permalink.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://permalink.gmane.org/gmane.linux.raid/38572">
    <title>[PATCH 2/4] Add --no-error argument to 'test'</title>
    <link>http://permalink.gmane.org/gmane.linux.raid/38572</link>
    <description>&lt;pre&gt;From: Jes Sorensen &amp;lt;Jes.Sorensen&amp;lt; at &amp;gt;redhat.com&amp;gt;

This allows the test suite to run to completion even if one test
fails.

Signed-off-by: Jes Sorensen &amp;lt;Jes.Sorensen&amp;lt; at &amp;gt;redhat.com&amp;gt;
---
 test |    8 ++++++--
 1 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/test b/test
index c7eb069..a0561ab 100755
--- a/test
+++ b/test
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -19,6 +19,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; fi
 testdir="tests"
 logdir="$testdir/logs"
 logsave=0
+exitonerror=1
 
 # Check whether to run multipath tests
 modprobe multipath 2&amp;gt; /dev/null
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -230,7 +231,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; do_test() {
     if [ "$savelogs" == "1" ]; then
       cp $targetdir/log $logdir/$_basename.log
     fi
-    if [ "$_fail" == "1" ]; then
+    if [ "$_fail" == "1" -a $"exitonerror" == "1" ]; then
       exit 1
     fi
   fi
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -238,7 +239,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; do_test() {
 
 do_help() {
   echo "Usage: "
-  echo " $0 [--tests=&amp;lt;test1,test2,..&amp;gt;] [--disable-multipath] [--logdir] [--save-logs] [setup] [prefix]"
+  echo " $0 [--tests=&amp;lt;test1,test2,..&amp;gt;] [--disable-multipath] [--logdir] [--save-logs] [--no-error] [setup] [prefix]"&lt;/pre&gt;</description>
    <dc:creator>Jes.Sorensen&lt; at &gt;redhat.com</dc:creator>
    <dc:date>2012-05-25T15:24:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.raid/38571">
    <title>[PATCH 0/4] More test suite enchancements</title>
    <link>http://permalink.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://permalink.gmane.org/gmane.linux.raid/38570">
    <title>[PATCH 4/4] Move setup code to a function and introduce matching cleanup argument</title>
    <link>http://permalink.gmane.org/gmane.linux.raid/38570</link>
    <description>&lt;pre&gt;From: Jes Sorensen &amp;lt;Jes.Sorensen&amp;lt; at &amp;gt;redhat.com&amp;gt;

Signed-off-by: Jes Sorensen &amp;lt;Jes.Sorensen&amp;lt; at &amp;gt;redhat.com&amp;gt;
---
 test |   60 +++++++++++++++++++++++++++++++++++-------------------------
 1 files changed, 35 insertions(+), 25 deletions(-)

diff --git a/test b/test
index 8e06ae2..9532ea7 100755
--- a/test
+++ b/test
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -68,33 +68,35 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; cleanup() {
 done
 }
 
-trap cleanup 0 1 2 3 15
+do_setup() {
+  trap cleanup 0 1 2 3 15
 
-devlist=
-for d in 0 1 2 3 4 5 6 7 8 9 10 11 12
-do
-   sz=$size
-   if [ $d -gt 7 ]; then sz=$ddfsize ; fi
-   [ -f $targetdir/mdtest$d ] || dd if=/dev/zero of=$targetdir/mdtest$d count=$sz bs=1K &amp;gt; /dev/null 2&amp;gt;&amp;amp;1
-   [ -b /dev/loop$d ] || mknod /dev/loop$d b 7 $d
-   if [ $d -eq 7 ]
-   then
-     losetup /dev/loop$d $targetdir/mdtest6 # for multipath use
-   else
-     losetup /dev/loop$d $targetdir/mdtest$d
-   fi
-   eval dev$d=/dev/loop$d
-   eval file$d=$targetdir/mdtest$d
-   eval devlist=\"\$devlist \$dev$d\"
+  devlist=
+  for d in 0 1 2 3 4 5 6 7 8 9 10 11 12
+  do
+    sz=$size
+    i&lt;/pre&gt;</description>
    <dc:creator>Jes.Sorensen&lt; at &gt;redhat.com</dc:creator>
    <dc:date>2012-05-25T15:24:08</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.raid/38569">
    <title>[PATCH 1/4] Add support for saving log files in test script</title>
    <link>http://permalink.gmane.org/gmane.linux.raid/38569</link>
    <description>&lt;pre&gt;From: Jes Sorensen &amp;lt;Jes.Sorensen&amp;lt; at &amp;gt;redhat.com&amp;gt;

--logdir= specifies where to save, if different from default, and
--save-logs tells test to save all log files.

Signed-off-by: Jes Sorensen &amp;lt;Jes.Sorensen&amp;lt; at &amp;gt;redhat.com&amp;gt;
---
 test |   42 ++++++++++++++++++++++++++++++++++++------
 1 files changed, 36 insertions(+), 6 deletions(-)

diff --git a/test b/test
index 7882586..c7eb069 100755
--- a/test
+++ b/test
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -16,6 +16,10 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; then
    echo &amp;gt;&amp;amp;2 "test: $mdadm isn't usable."
 fi
 
+testdir="tests"
+logdir="$testdir/logs"
+logsave=0
+
 # Check whether to run multipath tests
 modprobe multipath 2&amp;gt; /dev/null
 if grep -s 'Personalities : .*multipath' &amp;gt; /dev/null /proc/mdstat ; then
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -204,6 +208,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; rotest() {
 
 do_test() {
   _script=$1
+  _basename=`basename $_script`
   if [ -f "$_script" ]
   then
     rm -f $targetdir/stderr
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -215,8 +220,17 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; do_test() {
     # namespace, but cannot change it.
     echo -ne "$_script... "
     if ( set -ex ; . $_script )  2&amp;gt; $targetdir/log
-    then echo "succeeded"
-    else ech&lt;/pre&gt;</description>
    <dc:creator>Jes.Sorensen&lt; at &gt;redhat.com</dc:creator>
    <dc:date>2012-05-25T15:24:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.raid/38568">
    <title>[PATCH 3/4] Improve --help message from test</title>
    <link>http://permalink.gmane.org/gmane.linux.raid/38568</link>
    <description>&lt;pre&gt;From: Jes Sorensen &amp;lt;Jes.Sorensen&amp;lt; at &amp;gt;redhat.com&amp;gt;

Signed-off-by: Jes Sorensen &amp;lt;Jes.Sorensen&amp;lt; at &amp;gt;redhat.com&amp;gt;
---
 test |   11 +++++++++--
 1 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/test b/test
index a0561ab..8e06ae2 100755
--- a/test
+++ b/test
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -238,8 +238,15 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; do_test() {
 }
 
 do_help() {
-  echo "Usage: "
-  echo " $0 [--tests=&amp;lt;test1,test2,..&amp;gt;] [--disable-multipath] [--logdir] [--save-logs] [--no-error] [setup] [prefix]"
+  echo "Usage: $0 [options]"
+  echo " Options:"
+  echo "    --tests=&amp;lt;test1,test2,..&amp;gt;    Comma separated list of tests to run"
+  echo "    --disable-multipath         Disable any tests involving multipath"
+  echo "    --logdir=&amp;lt;directory&amp;gt;        Directory to save logfiles in"
+  echo "    --save-logs                 Save all logs in &amp;lt;logdir&amp;gt;"
+  echo "    --no-error                  Don't stop on error, ie. run all tests"
+  echo "    setup                       Setup test environment and exit"
+  echo "    &amp;lt;prefix&amp;gt;                    Run tests with &amp;lt;prefix&amp;gt;"
 }
 
 par&lt;/pre&gt;</description>
    <dc:creator>Jes.Sorensen&lt; at &gt;redhat.com</dc:creator>
    <dc:date>2012-05-25T15:24:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.raid/38567">
    <title>Re: very slow file deletion on an SSD</title>
    <link>http://permalink.gmane.org/gmane.linux.raid/38567</link>
    <description>&lt;pre&gt;noop scheduler could be better for ssd?

2012/5/25 Joe Landman &amp;lt;joe.landman&amp;lt; at &amp;gt;gmail.com&amp;gt;:



&lt;/pre&gt;</description>
    <dc:creator>Roberto Spadim</dc:creator>
    <dc:date>2012-05-25T14:48:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.raid/38566">
    <title>[PATCH] imsm: fix: correct checking volume's degradation</title>
    <link>http://permalink.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://permalink.gmane.org/gmane.linux.raid/38565">
    <title>Re: Reason for md raid 01 blksize limited to 4 KiB?</title>
    <link>http://permalink.gmane.org/gmane.linux.raid/38565</link>
    <description>&lt;pre&gt;Hi Neil,

On 22/05/12 01:28, NeilBrown wrote:

I've tested the RAID 01 with kernel 3.4 and it isn't fixed. It is even
worse, because direct IO doesn't work any more on the raid1 device (with
kernel 3.2 it worked).

There are still 4k chunks which aren't merged in the raid0 devices below
(blkparse -i md100 -i md200 -i md300 | less).
Could you also check this on your setup, please?

Cheers,
Sebastian


Btw. this is my test script:

#!/bin/bash
if [ "`lsmod | grep brd`" == "" ]; then
        modprobe brd rd_nr=4 rd_size=524288
fi
mdadm -C /dev/md100 --force --assume-clean -n 2 -l raid0 /dev/ram0 /dev/ram1
mdadm -C /dev/md200 --force --assume-clean -n 2 -l raid0 /dev/ram2 /dev/ram3
blktrace /dev/md100 &amp;amp;
pid=$!
dd if=/dev/zero of=/dev/md100 bs=1M oflag=direct
kill -2 $pid
blktrace /dev/md200 &amp;amp;
pid=$!
dd if=/dev/zero of=/dev/md200 bs=1M oflag=direct
kill -2 $pid
mv md100* r0_only/
mv md200* r0_only/

mdadm -C /dev/md300 --force --assume-clean -n 2 -l raid1 /dev/md100
/dev/md200
blktrace -d /dev/md100 -d /dev/md200&lt;/pre&gt;</description>
    <dc:creator>Sebastian Riemer</dc:creator>
    <dc:date>2012-05-25T12:35:57</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>

