Linux RAID Storage Date Index

• Thread Index

• help with bad performing raid6
  • From: Jon Nelson <jnelson-suse@xxxxxxxxxxx>
• sdb failure - mdadm: no devices found for /dev/md0
  • From: Andy Bailey <andy@xxxxxxxxxxxxxxxxx>
• Re: Handling mismatch_cnt
  • From: Redeeman <redeeman@xxxxxxxxxxx>
• Re: Handling mismatch_cnt
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• RE: DMA zeroing destination and zero_sum support
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• RE: Question on RAID-5 growing
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Handling mismatch_cnt
  • From: Thanassis Tsiodras <ttsiodras@xxxxxxxxx>
• Re: Question on RAID-5 growing
  • From: Drew <drew.kay@xxxxxxxxx>
• Question on RAID-5 growing
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Question regarding command completion from RAID driver
  • From: Tanmay <tanmayinamdar@xxxxxxxxx>
• Re: properly configure degraded array
  • From: Aldo Foot <lunixer@xxxxxxxxx>
• Re: Get rid of sparesmissing events
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: properly configure degraded array
  • From: "NeilBrown" <neilb@xxxxxxx>
• Get rid of sparesmissing events
  • From: Shane W <shane-kernel@xxxxxx>
• properly configure degraded array
  • From: Aldo Foot <lunixer@xxxxxxxxx>
• Re: How to handle >16TB devices on 32 bit hosts ??
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: How to handle >16TB devices on 32 bit hosts ??
  • From: Andreas Dilger <adilger@xxxxxxx>
• Re: How to handle >16TB devices on 32 bit hosts ??
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• RE: DMA zeroing destination and zero_sum support
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• DMA zeroing destination and zero_sum support
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• RE: Question on RAID-5 rmw & rcw(read modify write & read construct write)
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Question on RAID-5 rmw & rcw(read modify write & read construct write)
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• [patch] md: memory leak on error path in dm_exception_store_create()
  • From: Dan Carpenter <error27@xxxxxxxxx>
• Re: How to handle >16TB devices on 32 bit hosts ??
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: How to handle >16TB devices on 32 bit hosts ??
  • From: Tapani Tarvainen <tapani@xxxxxxxxxxxxxxxxxx>
• RE: >16TB RAID0
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: How to handle >16TB devices on 32 bit hosts ??
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• md2 won't mount at boot time, and array missing one spare
  • From: Max Waterman <davidmaxwaterman@xxxxxxxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• Re: How to handle >16TB devices on 32 bit hosts ??
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: How to handle >16TB devices on 32 bit hosts ??
  • From: Andreas Dilger <adilger@xxxxxxx>
• Re: How to handle >16TB devices on 32 bit hosts ??
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: How to handle >16TB devices on 32 bit hosts ??
  • From: Theodore Tso <tytso@xxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• Re: How to handle >16TB devices on 32 bit hosts ??
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: How to handle >16TB devices on 32 bit hosts ??
  • From: Andreas Dilger <adilger@xxxxxxx>
• Re: How to handle >16TB devices on 32 bit hosts ??
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: How to handle >16TB devices on 32 bit hosts ??
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: How to handle >16TB devices on 32 bit hosts ??
  • From: Andreas Dilger <adilger@xxxxxxx>
• Re: >16TB RAID0
  • From: "NeilBrown" <neilb@xxxxxxx>
• RE: >16TB RAID0
  • From: "NeilBrown" <neilb@xxxxxxx>
• How to handle >16TB devices on 32 bit hosts ??
  • From: Neil Brown <neilb@xxxxxxx>
• RE: >16TB RAID0
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: >16TB RAID0
  • From: Justin Maggard <jmaggard10@xxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: Gregory Maxwell <gmaxwell@xxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: hdaprm -Y /dev/sda /dev/sdb -> I/O error -> disk kicked out of RAID - is it normal?
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: hdaprm -Y /dev/sda /dev/sdb -> I/O error -> disk kicked out of RAID - is it normal?
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: hdaprm -Y /dev/sda /dev/sdb -> I/O error -> disk kicked out of RAID - is it normal?
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: hdaprm -Y /dev/sda /dev/sdb -> I/O error -> disk kicked out of RAID - is it normal?
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: hdaprm -Y /dev/sda /dev/sdb -> I/O error -> disk kicked out of RAID - is it normal?
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: >16TB RAID0
  • From: "NeilBrown" <neilb@xxxxxxx>
• >16TB RAID0
  • From: Justin Maggard <jmaggard10@xxxxxxxxx>
• hdaprm -Y /dev/sda /dev/sdb -> I/O error -> disk kicked out of RAID - is it normal?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Chassis manager?
  • From: David Lethe <david@xxxxxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: Chris Mason <chris.mason@xxxxxxxxxx>
• Chassis manager?
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: reshape raid5 to raid6
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: reshape raid5 to raid6
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• auiestion about ops_run_biodrain() using ADMA
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Re: migrate single disk to RAID 1?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: migrate single disk to RAID 1?
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: migrate single disk to RAID 1?
  • From: Ben Beuchler <insyte@xxxxxxxxx>
• Re: migrate single disk to RAID 1?
  • From: berk walker <berk@xxxxxxxxx>
• Re: migrate single disk to RAID 1?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• migrate single disk to RAID 1?
  • From: Ben Beuchler <insyte@xxxxxxxxx>
• [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
  • From: David Woodhouse <dwmw2@xxxxxxxxxxxxx>
• Re: [PATCH/Resend] md: Push down data integrity code to personalities.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: Help with Failed array
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Help with Failed array
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: Help with Failed array
  • From: Sujit Karataparambil <sjt.kar@xxxxxxxxx>
• Help with Failed array
  • From: Thomas Kenyon <zhadnost@xxxxxxxxxxxxxx>
• RE: where is async_tx_clear_ack() function called.
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• RE: where is async_tx_clear_ack() function called.
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• RE: Question on RAID-5 using ADMA
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• RE: where is async_tx_clear_ack() function called.
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Re: where is async_tx_clear_ack() function called.
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• RE: Question on RAID-5 using ADMA
  • From: Neil Brown <neilb@xxxxxxx>
• where is async_tx_clear_ack() function called.
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Re: Manually specifying data_offset in component device superblock?
  • From: Mark F <gnomeza@xxxxxxxxx>
• RE: Question on RAID-5 using ADMA
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• RE: Question on RAID-5 using ADMA
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: reshape raid5 to raid6
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: reshape raid5 to raid6
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• RE: Question on RAID-5 using ADMA
  • From: "NeilBrown" <neilb@xxxxxxx>
• RE: Question on RAID-5 using ADMA
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• RE: Question on RAID-5 using ADMA
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Re: Manually specifying data_offset in component device superblock?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: partition detection problem on 2.6.29.1 and 2.6.30
  • From: david@xxxxxxx
• RE: Question on RAID-5 using ADMA
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Question on RAID-5 using ADMA
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• RE: Question on RAID-5 using ADMA
  • From: "NeilBrown" <neilb@xxxxxxx>
• RE: Question on RAID-5 using ADMA
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• RE: Question on RAID-5 using ADMA
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Re: Question on RAID-5 using ADMA
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Question on RAID-5 using ADMA
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Re: [PATCH/Resend] md: Push down data integrity code to personalities.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Manually specifying data_offset in component device superblock?
  • From: Mark F <gnomeza@xxxxxxxxx>
• Re: [PATCH/Resend] md: Push down data integrity code to personalities.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Manually specifying data_offset in component device superblock?
  • From: Mark F <gnomeza@xxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH/Resend] md: Push down data integrity code to personalities.
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Adding a smaller drive
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: Adding a smaller drive
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Adding a smaller drive
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: mdadm --wait doesn't
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Adding a smaller drive
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• RE: Adding a smaller drive
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: mdadm --wait doesn't
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: mdadm --wait doesn't
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• mdadm --wait doesn't
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Adding a smaller drive
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Adding a smaller drive
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Adding a smaller drive
  • From: Billy Crook <billycrook@xxxxxxxxx>
• RE: Adding a smaller drive
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: Adding a smaller drive
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: RAID6 questions
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: RAID6 questions
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: mdadm+lvm2: ioctl error and cannot mount the device nodes?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: RAID6 questions
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: RAID6 questions
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: mdadm+lvm2: ioctl error and cannot mount the device nodes?
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• mdadm+lvm2: ioctl error and cannot mount the device nodes?
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• Re: RAID6 questions
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RAID6 questions
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: RAID6 questions
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: RAID6 questions
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• RAID6 questions
  • From: Marek <mlf.conv@xxxxxxxxx>
• [ANNOUNCE] Einarc - universal RAID management/monitoring tool - v1.4rc
  • From: Mikhail Yakshin <greycat.na.kor@xxxxxxxxx>
• Re: Adding a smaller drive
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: device-mapper: ioctl error adding target to table, lvm will not mount
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• device-mapper: ioctl error adding target to table, lvm will not mount
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• Re: series of unfortunate events on a raid5 array
  • From: Kris Hofmans <kris.hofmans@xxxxxxxxx>
• Re: series of unfortunate events on a raid5 array
  • From: Neil Brown <neilb@xxxxxxx>
• series of unfortunate events on a raid5 array
  • From: Kris Hofmans <kris.hofmans@xxxxxxxxx>
• Fwd: series of unfortunate events
  • From: Kris Hofmans <kris.hofmans@xxxxxxxxx>
• Re: device with newer data added as spare - data now gone?
  • From: John McNulty <johnmcn1@xxxxxxxxxxxxxx>
• [PATCH/Resend] md: Push down data integrity code to personalities.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: What will happen with spares in this scenario?
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Adding a smaller drive
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• RE: Adding a smaller drive
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: Adding a smaller drive
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• [PULL REQUEST] md updates for 2.6.31-rc
  • From: Neil Brown <neilb@xxxxxxx>
• Re: device with newer data added as spare - data now gone?
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: [PATCH] MD: md, fix lock imbalance
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: md: Use new topology calls to indicate alignment and I/O sizes
  • From: Neil Brown <neilb@xxxxxxx>
• Re: What will happen with spares in this scenario?
  • From: John McNulty <johnmcn1@xxxxxxxxxxxxxx>
• Re: md: Use new topology calls to indicate alignment and I/O sizes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Adding a smaller drive
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: What will happen with spares in this scenario?
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Adding a smaller drive
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: What will happen with spares in this scenario?
  • From: John McNulty <johnmcn1@xxxxxxxxxxxxxx>
• Re: What will happen with spares in this scenario?
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Andreas Dilger <adilger@xxxxxxx>
• [mdadm git pull v2] Intel metadata and mapfile fixes for mdadm-3.0.1
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: What will happen with spares in this scenario?
  • From: John McNulty <johnmcn1@xxxxxxxxxxxxxx>
• Re: [mdadm git pull] Intel metadata and mapfile fixes for mdadm-3.0.1
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: What will happen with spares in this scenario?
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• What will happen with spares in this scenario?
  • From: John McNulty <johnmcn1@xxxxxxxxxxxxxx>
• Re: Adding a smaller drive
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Boaz Harrosh <bharrosh@xxxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: Adding a smaller drive
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Adding a smaller drive
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Write intent bitmaps
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• RE: bug in asyn_xor() function
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Re: Adding a smaller drive
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Adding a smaller drive
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Adding a smaller drive
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Adding a smaller drive
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Adding a smaller drive
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Adding a smaller drive
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: [RFC PATCH] dm-csum: A new device mapper target that checks data integrity
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Adding a smaller drive
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Adding a smaller drive
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Adding a smaller drive
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Adding a smaller drive
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Adding a smaller drive
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• RE: Adding a smaller drive
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: Adding a smaller drive
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• RE: Adding a smaller drive
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: Adding a smaller drive
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• RE: device with newer data added as spare - data now gone?
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Adding a smaller drive
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: Write intent bitmaps
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: bug in asyn_xor() function
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• async_xor() has some issue
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Re: [RFC PATCH] dm-csum: A new device mapper target that checks data integrity
  • From: Alberto Bertogli <albertito@xxxxxxxxxxxxxx>
• Re: [RFC PATCH] dm-csum: A new device mapper target that checks data integrity
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Strange issue with async_xor
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Request on RAID5
  • From: "NeilBrown" <neilb@xxxxxxx>
• Request on RAID5
  • From: satha <satha_koti@xxxxxxxxxxx>
• Re: [RFC PATCH] dm-csum: A new device mapper target that checks data integrity
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH] dm-csum: A new device mapper target that checks data integrity
  • From: Alberto Bertogli <albertito@xxxxxxxxxxxxxx>
• Request on MD Driver
  • From: koti <koti.here.4u@xxxxxxxxx>
• Strange issue with async_xor
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• RE: RAID-5 creation crashes when files system installed while recovery going on
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Readding a drive fails because of wrong size?
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Neil Brown <neilb@xxxxxxx>
• device with newer data added as spare - data now gone?
  • From: Molinero <marianne@xxxxxxx>
• Re: [RFC PATCH] dm-csum: A new device mapper target that checks data integrity
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: [RFC PATCH] dm-csum: A new device mapper target that checks data integrity
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: resync hangs
  • From: Neil Brown <neilb@xxxxxxx>
• Re: reshape raid5 to raid6
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Questions regarding failure in the last IO path in multipath
  • From: "Ron Lai" <ronlai@xxxxxxxxxxxxxxx>
• Re: Questions regarding failure in the last IO path in multipath
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: RAID-5 creation crashes when files system installed while recovery going on
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Readding a drive fails because of wrong size?
  • From: "NeilBrown" <neilb@xxxxxxx>
• Questions regarding failure in the last IO path in multipath
  • From: "Ron Lai" <ronlai@xxxxxxxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Readding a drive fails because of wrong size?
  • From: Scott Baker <bakers@xxxxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• RE: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: <berthiaume_wayne@xxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: mdadm can't reshape/resize arrays
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: Neil Brown <neilb@xxxxxxx>
• Re: md: Use new topology calls to indicate alignment and I/O sizes
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• RE: RAID-5 creation crashes when files system installed while recovery going on
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Re: md: Use new topology calls to indicate alignment and I/O sizes
  • From: Neil Brown <neilb@xxxxxxx>
• RE: RAID-5 creation crashes when files system installed while recovery going on
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• IOPs using MD driver
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Re: mdadm can't reshape/resize arrays
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [PATCH/RFC] md: Push down data integrity code to personalities.
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: md: Use new topology calls to indicate alignment and I/O sizes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• RE: Slow raid10 resync
  • From: <Ryan_MichaelS@xxxxxxx>
• Re: reshape raid5 to raid6
  • From: Billy Crook <billycrook@xxxxxxxxx>
• Re: md: Use new topology calls to indicate alignment and I/O sizes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• mdadm can't reshape/resize arrays
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: reshape raid5 to raid6
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• Re: [PATCH/RFC] md: Push down data integrity code to personalities.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: reshape raid5 to raid6
  • From: Beolach <beolach@xxxxxxxxx>
• Re: reshape raid5 to raid6
  • From: "NeilBrown" <neilb@xxxxxxx>
• reshape raid5 to raid6
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• Re: Write barriers on MD RAID1
  • From: Neil Brown <neilb@xxxxxxx>
• Re: help please
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Write barriers on MD RAID1
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] Re: Write barriers on MD RAID1
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [PATCH] mv_xor: add support for clkdev framework
  • From: Saeed Bishara <saeed@xxxxxxxxxxx>
• Re: [dm-devel] Re: Write barriers on MD RAID1
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• RE: RAID-5 creation crashes when files system installed while recovery going on
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Write barriers on MD RAID1
  • From: Neil Brown <neilb@xxxxxxx>
• Re: help please
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm raid5 and bit errors resync
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Slow raid10 resync
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID-5 creation crashes when files system installed while recovery going on
  • From: "NeilBrown" <neilb@xxxxxxx>
• RAID-5 creation crashes when files system installed while recovery going on
  • From: "Tirumala Reddy Marri" <tmarri@xxxxxxxx>
• Re: [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: Mike Snitzer <snitzer@xxxxxxxxx>
• Re: [PATCH] mv_xor: add support for clkdev framework
  • From: Nicolas Pitre <nico@xxxxxxxxxxx>
• Re: [PATCH] mv_xor: add support for clkdev framework
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] mv_xor: add support for clkdev framework
  • From: Saeed Bishara <saeed@xxxxxxxxxxx>
• Re: [PATCH] mv_xor: add support for clkdev framework
  • From: Nicolas Pitre <nico@xxxxxxxxxxx>
• Re: [PATCH] mv_xor: add support for clkdev framework
  • From: saeed bishara <saeed.bishara@xxxxxxxxx>
• Re: [PATCH] mv_xor: add support for clkdev framework
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Slow raid10 resync
  • From: Sujit Karataparambil <sjt.kar@xxxxxxxxx>
• [PATCH] mv_xor: add support for power management
  • From: Saeed Bishara <saeed@xxxxxxxxxxx>
• [PATCH] mv_xor: add support for clkdev framework
  • From: Saeed Bishara <saeed@xxxxxxxxxxx>
• [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH/RFC] md: Push down data integrity code to personalities.
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Slow raid10 resync
  • From: <Ryan_MichaelS@xxxxxxx>
• Re: resync hangs
  • From: Randall Smith <randall@xxxxxx>
• Re: [PATCH] MD: md, fix lock imbalance
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• mdadm raid5 and bit errors resync
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• Re: resync hangs
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: resync hangs
  • From: Randall Smith <randall@xxxxxx>
• [PATCH] MD: md, fix lock imbalance
  • From: Jiri Slaby <jirislaby@xxxxxxxxx>
• Re: Subject: Raid0 Reshape . Preface
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Write intent bitmaps
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Resize Raid5 devices
  • From: Ralf Müller <ralf@xxxxxxxx>
• Re: Resize Raid5 devices
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Resize Raid5 devices
  • From: Ralf Müller <ralf@xxxxxxxx>
• Re: Write intent bitmaps
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Write intent bitmaps
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: filesystem stripe parameters
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: filesystem stripe parameters
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: filesystem stripe parameters
  • From: Wil Reichert <wil.reichert@xxxxxxxxx>
• Re: filesystem stripe parameters
  • From: Justin Perreault <justinperreault@xxxxxxxxx>
• Re: Write intent bitmaps
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• [PATCH/RFC] md: Push down data integrity code to personalities.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: Why is my raid 1 boot/root not working with autodetect?
  • From: Fredrik Pettersson <freppe@xxxxxxxxx>
• Re: filesystem stripe parameters
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Why is my raid 1 boot/root not working with autodetect?
  • From: Fredrik Pettersson <freppe@xxxxxxxxx>
• Re: filesystem stripe parameters
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Resize Raid5 devices
  • From: Ralf Müller <ralf@xxxxxxxx>
• Re: Write intent bitmaps
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Write intent bitmaps
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Write intent bitmaps
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Why is my raid 1 boot/root not working with autodetect?
  • From: Neil Brown <neilb@xxxxxxx>
• filesystem stripe parameters
  • From: Wil Reichert <wil.reichert@xxxxxxxxx>
• Re: Resize Raid5 devices
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Subject:[PATCH 001:013]: md: Raid0 reshape
  • From: Raz <raziebe@xxxxxxxxx>
• Re: Resize Raid5 devices
  • From: Ralf Müller <ralf@xxxxxxxx>
• Re: Resize Raid5 devices
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Why is my raid 1 boot/root not working with autodetect?
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Write intent bitmaps
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: [mdadm git pull] Intel metadata and mapfile fixes for mdadm-3.0.1
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md linear: Protecting mddev with rcu locks to avoid races
  • From: Neil Brown <neilb@xxxxxxx>
• [PULL REQUEST] md updates for 2.6.31
  • From: Neil Brown <neilb@xxxxxxx>
• Re: init_emergency_isa_pool calling mempool_create in non-sleeping context
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: init_emergency_isa_pool calling mempool_create in non-sleeping context
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: init_emergency_isa_pool calling mempool_create in non-sleeping context
  • From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
• Re: init_emergency_isa_pool calling mempool_create in non-sleeping context
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Subject: Raid0 Reshape . Preface
  • From: Neil Brown <neilb@xxxxxxx>
• Re: init_emergency_isa_pool calling mempool_create in non-sleeping context
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Subject:[PATCH 001:013]: md: Raid0 reshape
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Resize Raid5 devices
  • From: Ralf Müller <ralf@xxxxxxxx>
• Re: Subject:[PATCH 001:013]: md: Raid0 reshape
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Subject: Raid0 Reshape . Preface
  • From: "John Robinson" <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Subject: Raid0 Reshape . Preface
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md linear: Protecting mddev with rcu locks to avoid races in
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: [PATCH] md linear: Protecting mddev with rcu locks to avoid races in
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md linear: Protecting mddev with rcu locks to avoid races in
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md linear: Protecting mddev with rcu locks to avoid races in
  • From: Sujit Karataparambil <sjt.kar@xxxxxxxxx>
• Re: [PATCH] md linear: Protecting mddev with rcu locks to avoid races in
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: [PATCH] md linear: Protecting mddev with rcu locks to avoid races in
  • From: Sujit Karataparambil <sjt.kar@xxxxxxxxx>
• Re: [PATCH] md linear: Protecting mddev with rcu locks to avoid races in
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: Subject:[PATCH 001:013]: md: Raid0 reshape
  • From: Raz <raziebe@xxxxxxxxx>
• Re: Subject:[PATCH 001:013]: md: Raid0 reshape
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: [PATCH] md linear: Protecting mddev with rcu locks to avoid races in
  • From: Sujit Karataparambil <sjt.kar@xxxxxxxxx>
• Re: Subject:[PATCH 001:013]: md: Raid0 reshape
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: [PATCH] md linear: Protecting mddev with rcu locks to avoid races in
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [PATCH] md linear: Protecting mddev with rcu locks to avoid races in
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: [PATCH] md linear: Protecting mddev with rcu locks to avoid races in
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• [mdadm git pull] Intel metadata and mapfile fixes for mdadm-3.0.1
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Subject:[PATCH 001:013]: md: Raid0 reshape
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Subject:[PATCH 1:1]: mdadm. add raid0 grow support
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Subject:[PATCH 013:013]: kconfig:add raid0 a reshape option
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Subject:[PATCH 012:013]: raid0.c, wrap reshape code in ifdefs
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Subject:[PATCH 011:013]: raid0.h: reshape structure
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Subject:[PATCH 010:013]: raid0: reshape core code
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Subject:[PATCH 009:013]: raid0:add hot add and hot remove
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Subject:[PATCH 008:013]:raid0, split raid0_make_request
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Subject:[PATCH 007:013]: raid0 , change map_sector arguements
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Subject:[PATCH 006:013]:raid0: remove redundant argument from is_in_chunk_boundary
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Subject:[PATCH 005:013]: raid0: refactor create_strip and raid0_run
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Subject:[PATCH 004:013]: dump_zones to print_conf
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Subject:[PATCH 003:013]: raid0: raid0_size to support reshape
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Subject:[PATCH 002:013]: raid0: find_zone to return NULL
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Subject:[PATCH 001:013]: md: Raid0 reshape
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Subject: Raid0 Reshape . Preface
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (more questions)
  • From: <linux-raid.vger.kernel.org@xxxxxxxxxxx>
• Re: Re: RAID-6 mdadm disks out of sync issue (more questions)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (more questions)
  • From: <linux-raid.vger.kernel.org@xxxxxxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (more questions)
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: "cannot start dirty degraded array"
  • From: Kyler Laird <kyler-keyword-linuxraid.6e1399@xxxxxxxxxx>
• Re: "cannot start dirty degraded array"
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (more questions)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: "cannot start dirty degraded array"
  • From: Kyler Laird <kyler-keyword-linuxraid.6e1399@xxxxxxxxxx>
• Re: "cannot start dirty degraded array"
  • From: carlos@xxxxxxxxxxxxxx (Carlos Carvalho)
• Re: [PATCH] md linear: Protecting mddev with rcu locks to avoid races in
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (more questions)
  • From: <linux-raid.vger.kernel.org@xxxxxxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (more questions)
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (more questions)
  • From: <linux-raid.vger.kernel.org@xxxxxxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (success!)
  • From: <linux-raid.vger.kernel.org@xxxxxxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (no success)
  • From: <linux-raid.vger.kernel.org@xxxxxxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (no success)
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (no success)
  • From: <linux-raid.vger.kernel.org@xxxxxxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (no success)
  • From: <linux-raid.vger.kernel.org@xxxxxxxxxxx>
• Re: how to resize volume group lvm2?
  • From: Tapani Tarvainen <raid@xxxxxxxxxxxxxxxxxx>
• Re: how to resize volume group lvm2?
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• how to resize volume group lvm2?
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• Re: Strange RAID behaviour when faced with user error
  • From: Jody McIntyre <scjody@xxxxxxx>
• Re: Assembly problems with kernel 2.6.30?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• RE: Software RAID5 write issues
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Assembly problems with kernel 2.6.30?
  • From: Jim Paris <jim@xxxxxxxx>
• Re: Assembly problems with kernel 2.6.30?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (five questions)
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Computer locked up when adding bitmap=internal and now filesystem is gone
  • From: Henrik Johnson <henrik.johnson@xxxxxxxxx>
• Re: Computer locked up when adding bitmap=internal and now filesystem is gone
  • From: Neil Brown <neilb@xxxxxxx>
• Re: slow mdadm reshape, normal?
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (five questions)
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• RE: Computer locked up when adding bitmap=internal and now filesystem is gone
  • From: Henrik Johnson <henrik.johnson@xxxxxxxxx>
• RE: How do I start an array with an invalid bitmap file
  • From: Henrik Johnson <henrik.johnson@xxxxxxxxx>
• RFC: Adding new block layer error codes
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Computer locked up when adding bitmap=internal and now filesystem is gone
  • From: Henrik Johnson <henrik.johnson@xxxxxxxxx>
• Re: slow mdadm reshape, normal? lspci/iostat info
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• Re: slow mdadm reshape, normal?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: mdadm message (auto-read-only) on "/dev/md1" = swap file system
  • From: "Ing. Jair" <jairzhino@xxxxxxxxx>
• How do I start an array with an invalid bitmap file
  • From: Henrik Johnson <henrik.johnson@xxxxxxxxx>
• Re: slow mdadm reshape, normal?
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (five questions)
  • From: <linux-raid.vger.kernel.org@xxxxxxxxxxx>
• Re: slow mdadm reshape, normal?
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• Re: [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: Neil Brown <neilb@xxxxxxx>
• RE: mdadm message (auto-read-only) on "/dev/md1" = swap file system
  • From: "Simon Jackson" <sjackson@xxxxxxxxxxx>
• Re: Why is my raid 1 boot/root not working with autodetect?
  • From: Fredrik Pettersson <freppe@xxxxxxxxx>
• Re: slow mdadm reshape, normal?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Assembly problems with kernel 2.6.30?
  • From: Jim Paris <jim@xxxxxxxx>
• Re: Software RAID5 write issues
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Software RAID5 write issues
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• Re: Re: slow mdadm reshape, normal?
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• Re: slow mdadm reshape, normal?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• slow mdadm reshape, normal?
  • From: Michael Ole Olsen <gnu@xxxxxxx>
• Re: Strange RAID behaviour when faced with user error
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Strange RAID behaviour when faced with user error
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Strange RAID behaviour when faced with user error
  • From: Jody McIntyre <scjody@xxxxxxx>
• Re: Software RAID5 write issues
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• "cannot start dirty degraded array"
  • From: Kyler Laird <kyler-keyword-linuxraid.6e1399@xxxxxxxxxx>
• Re: Software RAID5 write issues
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: mdadm message (auto-read-only) on "/dev/md1" = swap file system
  • From: "Ing. Jair" <jairzhino@xxxxxxxxx>
• Re: mdadm message (auto-read-only) on "/dev/md1" = swap file system
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Software RAID5 write issues
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• Re: mdadm message (auto-read-only) on "/dev/md1" = swap file system
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• mdadm message (auto-read-only) on "/dev/md1" = swap file system
  • From: "Ing. Jair" <jairzhino@xxxxxxxxx>
• Why is my raid 1 boot/root not working with autodetect?
  • From: Fredrik Pettersson <freppe@xxxxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (long e-mail)
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: RAID-6 mdadm disks out of sync issue (long e-mail)
  • From: <linux-raid.vger.kernel.org@xxxxxxxxxxx>
• RAID-6 mdadm disks out of sync issue (long e-mail)
  • From: <linux-raid.vger.kernel.org@xxxxxxxxxxx>
• Re: [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: resync hangs
  • From: Randall Smith <randall@xxxxxx>
• Re: resync hangs
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: resync hangs
  • From: Randall Smith <randall@xxxxxx>
• Re: [dm-devel] Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• RE: Resync failing to start.
  • From: "NeilBrown" <neilb@xxxxxxx>
• RE: Resync failing to start.
  • From: "Simon Jackson" <sjackson@xxxxxxxxxxx>
• Re: Resync failing to start.
  • From: "NeilBrown" <neilb@xxxxxxx>
• Resync failing to start.
  • From: "Simon Jackson" <sjackson@xxxxxxxxxxx>
• [PULL REQUEST] md: a few more reshape fixes for 2.6.30
  • From: Neil Brown <neilb@xxxxxxx>
• [md PATCH 3/3] md/raid5: fix bug in reshape code when chunk_size decreases.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 2/3] md/raid5 - avoid deadlocks in get_active_stripe during reshape
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 1/3] md/raid5: use conf->raid_disks in preference to mddev->raid_disk
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 0/3] reshape bug fixes for 2.6.30
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: "NeilBrown" <neilb@xxxxxxx>
• [PATCH] md: Use new topology calls to indicate alignment and I/O sizes
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: Nifty Fedora Mitch <niftyfedora@xxxxxxxxxxxx>
• RE: How to un-degrade an array after a totally spurious failure?
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [dm-devel] Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH v2 05/11] md/raid5: add scribble region for buffer lists
  • From: Jody McIntyre <scjody@xxxxxxx>
• Re: Write intent bitmaps
  • From: carlos@xxxxxxxxxxxxxx (Carlos Carvalho)
• Re: How to un-degrade an array after a totally spurious failure?
  • From: carlos@xxxxxxxxxxxxxx (Carlos Carvalho)
• Re: RAID 5 re-add of removed drive? (failed drive replacement)
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: How to un-degrade an array after a totally spurious failure?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• RE: Unable to stop array
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: Unable to stop array
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Write intent bitmaps
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: How to un-degrade an array after a totally spurious failure?
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: How to un-degrade an array after a totally spurious failure?
  • From: carlos@xxxxxxxxxxxxxx (Carlos Carvalho)
• RE: How to un-degrade an array after a totally spurious failure?
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: Unable to stop array
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: Unable to stop array
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Timeout until degrade of RAID5 array
  • From: "NeilBrown" <neilb@xxxxxxx>
• Timeout until degrade of RAID5 array
  • From: Gabriel Ambuehl <gabriel_ambuehl@xxxxxx>
• Unable to stop array
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Bill Davidsen <davidsen@xxxxxxx>
• resync hangs
  • From: Randall Smith <randall@xxxxxx>
• [PATCH] md linear: Protecting mddev with rcu locks to avoid races in
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: [PATCH v2 05/11] md/raid5: add scribble region for buffer lists
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re:
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: md raid5 keeps going degraded.
  • From: Neil Brown <neilb@xxxxxxx>
• [no subject]
  • From: "Jack Etherington" <jack@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Nifty Fedora Mitch <niftyfedora@xxxxxxxxxxxx>
• Re: [dm-devel] Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Anton Altaparmakov <aia21@xxxxxxxxx>
• Re: [PATCH 4/8] md/raid6: asynchronous handle_stripe_fill6
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 2/8] md/raid6: asynchronous raid6 operations
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH v2 05/11] md/raid5: add scribble region for buffer lists
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Subject : PATCH [001:001]: raid0 devices size should be aligned to chunk size
  • From: Neil Brown <neilb@xxxxxxx>
• Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• [PATCH 8/8] md/raid6: remove synchronous infrastructure
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 7/8] md/raid6: asynchronous handle_stripe6
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 6/8] md/raid6: asynchronous handle_parity_check6
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 5/8] md/raid6: asynchronous handle_stripe_dirtying6
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 4/8] md/raid6: asynchronous handle_stripe_fill6
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 3/8] md/raid5,6: common schedule_reconstruction for raid5/6
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2/8] md/raid6: asynchronous raid6 operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 1/8] md/raid5: factor out mark_uptodate from ops_complete_compute5
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 0/8] Asynchronous raid6 acceleration (part 3 of 3)
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: import existing intel array
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: [PATCH v2 08/11] async_tx: add support for asynchronous GF multiplication
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2 08/11] async_tx: add support for asynchronous GF multiplication
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2 11/11] async_tx: raid6 recovery self test
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Awful RAID5 random read performance
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: [PATCH v2 03/11] async_tx: structify submission arguments, add scribble
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2 02/11] async_tx: kill ASYNC_TX_DEP_ACK flag
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [PATCH v2 01/11] async_tx: rename zero_sum to val
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [dm-devel] Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [dm-devel] Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Anton Altaparmakov <aia21@xxxxxxxxx>
• Re: [PATCH/RFC 0/2] md: personality pushdown patches -- intro
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Awful RAID5 random read performance
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• MD and DM (was: Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux)
  • From: Mike Snitzer <snitzer@xxxxxxxxx>
• Re: Awful RAID5 random read performance
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: OT Re: Good Day
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: slow random raid5 access?
  • From: Nifty Fedora Mitch <niftyfedora@xxxxxxxxxxxx>
• Re: OT Re: Good Day
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Upgrading a software RAID
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: Upgrading a software RAID
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID5 reconstruction ?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Upgrading a software RAID
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Upgrading a software RAID
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: Upgrading a software RAID
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID 5 re-add of removed drive? (failed drive replacement)
  • From: Alexander Rietsch <Alexander.Rietsch@xxxxxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Wil Reichert <wil.reichert@xxxxxxxxx>
• Re: RAID 5 re-add of removed drive? (failed drive replacement)
  • From: Jon Hardcastle <jd_hardcastle@xxxxxxxxx>
• Re: RAID 5 re-add of removed drive? (failed drive replacement)
  • From: Alexander Rietsch <Alexander.Rietsch@xxxxxxxxxx>
• Re: RAID 5 re-add of removed drive? (failed drive replacement)
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: RAID 5 re-add of removed drive? (failed drive replacement)
  • From: Alexander Rietsch <Alexander.Rietsch@xxxxxxxxxx>
• Re: RAID 5 re-add of removed drive? (failed drive replacement)
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: RAID 5 re-add of removed drive? (failed drive replacement)
  • From: Sujit Karataparambil <sjt.kar@xxxxxxxxx>
• Re: RAID 5 re-add of removed drive? (failed drive replacement)
  • From: Alexander Rietsch <Alexander.Rietsch@xxxxxxxxxx>
• Re: RAID 5 re-add of removed drive? (failed drive replacement)
  • From: Sujit Karataparambil <sjt.kar@xxxxxxxxx>
• Re: RAID 5 re-add of removed drive? (failed drive replacement)
  • From: Sujit Karataparambil <sjt.kar@xxxxxxxxx>
• RAID 5 re-add of removed drive? (failed drive replacement)
  • From: Alex R <Alexander.Rietsch@xxxxxxxxxx>
• ANNOUNCE: mdadm 3.0 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• raid5 rebuild/resync speed.
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Subject : PATCH [001:001]: raid0 devices size should be aligned to chunk size
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• chunk size fix -- found a bug
  • From: raz ben yehuda <raziebe@xxxxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Re: Awful RAID5 random read performance
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Awful RAID5 random read performance
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• RE: Awful RAID5 random read performance
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: Awful RAID5 random read performance
  • From: carlos@xxxxxxxxxxxxxx (Carlos Carvalho)
• Re: Awful RAID5 random read performance
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Awful RAID5 random read performance
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• RE: Awful RAID5 random read performance
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: Awful RAID5 random read performance
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: RAID5 reconstruction ?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Events?
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: Awful RAID5 random read performance
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Maxime Boissonneault <maxime.boissonneault@xxxxxxxxxxxxxx>
• RE: Events?
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: RAID-5 spare drive: Can't make spare persist across reboot
  • From: David Rea <dave@xxxxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Upgrading a software RAID
  • From: Maxime Boissonneault <maxime.boissonneault@xxxxxxxxxxxxxx>
• Re: RAID-5 spare drive: Can't make spare persist across reboot
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Upgrading a software RAID
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID-5 spare drive: Can't make spare persist across reboot
  • From: David Rea <dave@xxxxxxxxxxx>
• Re: [PATCH/RFC 0/2] md: personality pushdown patches -- intro
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Upgrading a software RAID
  • From: Maxime Boissonneault <maxime.boissonneault@xxxxxxxxxxxxxx>
• Re: RAID-5 spare drive: Can't make spare persist across reboot
  • From: Neil Brown <neilb@xxxxxxx>
• Awful RAID5 random read performance
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Re: Events?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Upgrading a software RAID
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Maxime Boissonneault <maxime.boissonneault@xxxxxxxxxxxxxx>
• Events?
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• slow random raid5 access?
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: RAID5 reconstruction ?
  • From: Redeeman <redeeman@xxxxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: RAID5 reconstruction ?
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: RAID5 reconstruction ?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• RAID-5 spare drive: Can't make spare persist across reboot
  • From: David Rea <dave@xxxxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Maxime Boissonneault <maxime.boissonneault@xxxxxxxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Upgrading a software RAID
  • From: Maxime Boissonneault <maxime.boissonneault@xxxxxxxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: Maxime Boissonneault <maxime.boissonneault@xxxxxxxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: Redeeman <redeeman@xxxxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Raid and badblocks
  • From: Sujit Karataparambil <sjt.kar@xxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: Maxime Boissonneault <maxime.boissonneault@xxxxxxxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: Sujit Karataparambil <sjt.kar@xxxxxxxxx>
• Re: Raid and badblocks
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: RAID5 reconstruction ?
  • From: Sujit Karataparambil <sjt.kar@xxxxxxxxx>
• Re: Raid and badblocks
  • From: hank peng <pengxihan@xxxxxxxxx>
• RAID5 reconstruction ?
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• Re: [PATCH 1/2] md: Push down reconstruction log message to personality code.
  • From: Raz <raziebe@xxxxxxxxx>
• Re: Need information regarding RAID 6 Async APIs for kernel version 2.6.27
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• RE: [PATCH v2 11/11] async_tx: raid6 recovery self test
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH v2 09/11] async_tx: add support for asynchronous RAID6 recovery operations
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH v2 10/11] dmatest: add pq support
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH v2 08/11] async_tx: add support for asynchronous GF multiplication
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH v2 07/11] async_tx: kill needless module_{init|exit}
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH v2 04/11] async_xor: permit callers to pass in a 'dma/page scribble' region
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH v2 06/11] async_tx: add sum check flags
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH v2 03/11] async_tx: structify submission arguments, add scribble
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH v2 02/11] async_tx: kill ASYNC_TX_DEP_ACK flag
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH v2 01/11] async_tx: rename zero_sum to val
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• [PATCH 2/2] md: Move check for bitmap presence to personality code.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH 1/2] md: Push down reconstruction log message to personality code.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH/RFC 0/2] md: personality pushdown patches -- intro
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: forcing check of RAID1 arrays causes lockup
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Need information regarding RAID 6 Async APIs for kernel version 2.6.27
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [RFC PATCH] dm-csum: A new device mapper target that checks data integrity
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Subject: [001/002 ] raid0 reshape
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: raid failure and LVM volume group availability
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Need information regarding RAID 6 Async APIs for kernel version 2.6.27
  • From: Koti <satha_koti@xxxxxxxxxxx>
• Re: resync duration ?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Maxime Boissonneault <maxime.boissonneault@xxxxxxxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Upgrading a software RAID
  • From: Maxime Boissonneault <maxime.boissonneault@xxxxxxxxxxxxxx>
• Re: Upgrading a software RAID
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Western Digital RE3
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Western Digital RE3
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: forcing check of RAID1 arrays causes lockup
  • From: Redeeman <redeeman@xxxxxxxxxxx>
• Re: forcing check of RAID1 arrays causes lockup
  • From: Kyle Liddell <kyle@xxxxxxxxxxxxxxxxxxxx>
• RE: FW: Detecting errors on the RAID disks.
  • From: "Simon Jackson" <sjackson@xxxxxxxxxxx>
• RE: Western Digital RE3
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• Re: Western Digital RE3
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Subject: [001/002 ] raid0 reshape
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: FW: Detecting errors on the RAID disks.
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• FW: Detecting errors on the RAID disks.
  • From: "Simon Jackson" <sjackson@xxxxxxxxxxx>
• Re: Western Digital RE3
  • From: russ@xxxxxxxxxx
• Re: Western Digital RE3
  • From: Redeeman <redeeman@xxxxxxxxxxx>
• Re: [PATCH 0/6] md: More sector_t conversions -- intro
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: forcing check of RAID1 arrays causes lockup
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Western Digital RE3
  • From: Nifty Fedora Mitch <niftyfedora@xxxxxxxxxxxx>
• forcing check of RAID1 arrays causes lockup
  • From: kyle@xxxxxxxxxxxxxxxxxxxx
• [RFC PATCH v2] dm-csum: A new device mapper target that checks data integrity
  • From: Alberto Bertogli <albertito@xxxxxxxxxxxxxx>
• Re: Raid and badblocks
  • From: Andrew Burgess <aab@xxxxxxxxxxx>
• Re: Raid and badblocks
  • From: Jeremy Sanders <jss@xxxxxxxxxxxxx>
• Re: [RFC PATCH] dm-csum: A new device mapper target that checks data integrity
  • From: Alberto Bertogli <albertito@xxxxxxxxxxxxxx>
• Re: raid failure and LVM volume group availability
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Subject: [001/002 ] raid0 reshape
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Subject: [001/002 ] raid0 reshape
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: raid failure and LVM volume group availability
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• RE: How to un-degrade an array after a totally spurious failure?
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [RFC PATCH] dm-csum: A new device mapper target that checks data integrity
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• RE: How to un-degrade an array after a totally spurious failure?
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: Western Digital RE3
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• [PULL REQUEST] md - various fixed for 2.6.30
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 0/6] md: More sector_t conversions -- intro
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 0/6] md: More sector_t conversions -- intro
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 4/6] md: convert conf->chunk_size and conf->prev_chunk to sectors.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 1/6] md: Make mddev->chunk_size sector-based.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Subject: [001/002 ] raid0 reshape
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Western Digital RE3
  • From: Redeeman <redeeman@xxxxxxxxxxx>
• Re: Subject: [001/002 ] raid0 reshape
  • From: Raz <raziebe@xxxxxxxxx>
• Re: Western Digital RE3
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: [RFC PATCH] dm-csum: A new device mapper target that checks data integrity
  • From: Alberto Bertogli <albertito@xxxxxxxxxxxxxx>
• Upgrading a software RAID
  • From: Maxime Boissonneault <maxime.boissonneault@xxxxxxxxxxxxxx>
• Re: Adaptec 2405 : hardware or software raid?
  • From: Andrew Burgess <aab@xxxxxxxxxxx>
• Re: raid failure and LVM volume group availability
  • From: hank peng <pengxihan@xxxxxxxxx>
• Adaptec 2405 : hardware or software raid?
  • From: Janek Kozicki <janek_listy@xxxxx>
• Western Digital RE3
  • From: "MOgWai46[Saurceful of Secrets]" <street41@xxxxxxxxx>
• Re: [PATCH 2/6] md: Fix a bug in super_1_sync().
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: LVM->RAID->LVM
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: [RFC PATCH] dm-csum: A new device mapper target that checks data integrity
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Subject: [001/002 ] raid0 reshape
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: raid failure and LVM volume group availability
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: [PATCH 2/6] md: Fix a bug in super_1_sync().
  • From: "NeilBrown" <neilb@xxxxxxx>
• [PATCH 6/6] md/raid5: Kill outdated comment.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH 5/6] md/raid5: Use is_power_of_2() in raid5_reconfig()/raid6_reconfig().
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH 4/6] md: convert conf->chunk_size and conf->prev_chunk to sectors.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH 3/6] md: Convert mddev->new_chunk to sectors.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH 1/6] md: Make mddev->chunk_size sector-based.
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH 2/6] md: Fix a bug in super_1_sync().
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [PATCH 0/6] md: More sector_t conversions -- intro
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 04/11] async_xor: permit callers to pass in a 'dma/page scribble' region
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• [md PATCH 3/3] md: export 'frozen' resync state through sysfs
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 2/3] md: bitmap: improve bitmap maintenance code.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 1/3] md: improve errno return when setting array_size
  • From: NeilBrown <neilb@xxxxxxx>
• Re: LVM->RAID->LVM
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• LVM->RAID->LVM
  • From: Billy Crook <billycrook@xxxxxxxxx>
• Re: Missing md superblock on added devices after grow ...
  • From: Billy Crook <billycrook@xxxxxxxxx>