Linux RAID Storage Date Index

• Thread Index

• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Known good eSATA CardBus controllers
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: How to force stopping an array`
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: How to force stopping an array`
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Known good eSATA CardBus controllers
  • From: "Jeff Breidenbach" <jeff@xxxxxxx>
• Re: Known good eSATA CardBus controllers
  • From: "Jeff Breidenbach" <jeff@xxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Kasper Sandberg <lkml@xxxxxxxxxxx>
• Known good eSATA CardBus controllers
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: Proposal: non-striping RAID4
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Chris Snook <csnook@xxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Bryan Mesich <bryan.mesich@xxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Chris Snook <csnook@xxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: "Jens Bäckman" <jens.backman@xxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Chris Snook <csnook@xxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Performance Characteristics of All Linux RAIDs (mdadm/bonnie++)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: split off + mount a partitionless RAID1 device?
  • From: "Jeff Breidenbach" <jeff@xxxxxxx>
• Re: How to force stopping an array`
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: aoe disk not recognized as part of raid - solution!
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: split off + mount a partitionless RAID1 device?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: How to force stopping an array`
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: aoe disk not recognized as part of raid
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: aoe disk not recognized as part of raid
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH 003 of 3] md: Do not compute parity unless it is on a failed drive
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 3] md: fix uninitialized use of mddev->recovery_wait
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 3] md: md: fix prexor vs sync_request race
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 3] md: raid5 patches suitable for 2.6.26 and -stable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: split off + mount a partitionless RAID1 device?
  • From: "Jeff Breidenbach" <jeff@xxxxxxx>
• Re: split off + mount a partitionless RAID1 device?
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: split off + mount a partitionless RAID1 device?
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• split off + mount a partitionless RAID1 device?
  • From: "Jeff Breidenbach" <jeff@xxxxxxx>
• Re: Marvell 88SX7042 [4 Port SATA PCI-Express x4] Support/Questions
  • From: "Grant Grundler" <grundler@xxxxxxxxxx>
• Re: How to force stopping an array`
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: How to force stopping an array`
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: How to force stopping an array`
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: How to force stopping an array`
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: How to force stopping an array`
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• How to force stopping an array`
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• RE: Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system
  • From: Jan Engelhardt <jengelh@xxxxxxxxxx>
• Re: Keeping debian from auto-assembling
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: aoe disk not recognized as part of raid
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: Marvell 88SX7042 [4 Port SATA PCI-Express x4] Support/Questions
  • From: Andre Tomt <andre@xxxxxxxx>
• Re: Marvell 88SX7042 [4 Port SATA PCI-Express x4] Support/Questions
  • From: Mark Lord <liml@xxxxxx>
• Marvell 88SX7042 [4 Port SATA PCI-Express x4] Support/Questions
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: aoe disk not recognized as part of raid
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: RFI for 2.6.25.5 : Re: Regression- XFS won't mount on partitioned md array
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• RE: Proposal: non-striping RAID4
  • From: "Chris Green" <cgreen@xxxxxxxxxxxxxxxxx>
• Re: Proposal: non-striping RAID4
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RFI for 2.6.25.5 : Re: Regression- XFS won't mount on partitioned md array
  • From: Willy Tarreau <w@xxxxxx>
• RFI for 2.6.25.5 : Re: Regression- XFS won't mount on partitioned md array
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: aoe disk not recognized as part of raid
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: aoe disk not recognized as part of raid
  • From: "NeilBrown" <neilb@xxxxxxx>
• RE: Proposal: non-striping RAID4
  • From: "Chris Green" <cgreen@xxxxxxxxxxxxxxxxx>
• Re: Proposal: non-striping RAID4
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: aoe disk not recognized as part of raid
  • From: Lars Täuber <taeuber@xxxxxxx>
• aoe disk not recognized as part of raid
  • From: Lars Täuber <taeuber@xxxxxxx>
• ESATA discs spindown. Can mdadm handle this?
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• Re: Recreating undamaged RAID5
  • From: "NeilBrown" <neilb@xxxxxxx>
• RE: Proposal: non-striping RAID4
  • From: Tony Germano <tony_germano@xxxxxxxxxxx>
• Recreating undamaged RAID5
  • From: Anders Johansson <ajh@xxxxxx>
• RE: Proposal: non-striping RAID4
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Proposal: non-striping RAID4
  • From: Tony Germano <tony_germano@xxxxxxxxxxx>
• RE: Two Drive Failure on RAID-5
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: Ric Wheeler <ricwheeler@xxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: Cry <cry_regarder@xxxxxxxxx>
• RAID-6, dmcrypt, lvm, ext3
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: David Greaves <david@xxxxxxxxxxxx>
• RE: Wipe failed RAID-5 disk before RMA
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Wipe failed RAID-5 disk before RMA
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: INFO: task md2_resync:7950 blocked for more than 120 seconds
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Re: Re: Two Drive Failure on RAID-5
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• RE: Re: Re: Two Drive Failure on RAID-5
  • From: Keith Roberts <keith@xxxxxxxxxxxx>
• RE: Re: Re: Two Drive Failure on RAID-5
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Re: Two Drive Failure on RAID-5
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• Re: Wipe failed RAID-5 disk before RMA
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• Re: Wipe failed RAID-5 disk before RMA
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Wipe failed RAID-5 disk before RMA
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: Re: Two Drive Failure on RAID-5
  • From: Cry <cry_regarder@xxxxxxxxx>
• RE: Re: Two Drive Failure on RAID-5
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• RE: Re: Two Drive Failure on RAID-5
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Two Drive Failure on RAID-5
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: David Greaves <david@xxxxxxxxxxxx>
• RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• Two Drive Failure on RAID-5
  • From: Cry <cry_regarder@xxxxxxxxx>
• Re: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: David Greaves <david@xxxxxxxxxxxx>
• RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system
  • From: Neil Brown <neilb@xxxxxxx>
• ANNOUNCE: mdadm 2.6.6 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: howto and faq
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm 2.6.5 compile issue
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH 010 of 10] md: Restart recovery cleanly after device failure.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 009 of 10] md: Allow parallel resync of md-devices.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 008 of 10] md: Improve setting of "events_cleared" for write-intent bitmaps.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 007 of 10] md: notify userspace on 'stop' events
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 006 of 10] md: Notify userspace on 'write-pending' changes to array_state
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 005 of 10] md: raid1: Fix restoration of bio between failed read and write.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 10] md: md: raid5 rate limit error printk
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 003 of 10] md: kill file_path wrapper
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 10] md: proper extern for mdp_major
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 10] md: Fix possible oops when removing a bitmap from an active array
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 10] md: Various bug fixes and small improvements for md in 2.6.26-rc
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [OT] Re: questions about softraid limitations
  • From: Neil Brown <neilb@xxxxxxx>
• Re: questions about softraid limitations
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• RE: questions about softraid limitations
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• RE: Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• RE: Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• Re: Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Mechanism to safely force repair of single md stripe w/o hurting data integrity of file system
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: David Greaves <david@xxxxxxxxxxxx>
• mdadm 2.6.5 compile issue
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: "Oliver Pinter" <oliver.pntr@xxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Regression- XFS won't mount on partitioned md array
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Regression- XFS won't mount on partitioned md array
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Neil Brown <neilb@xxxxxxx>
• Re: questions about softraid limitations
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
• Re: questions about softraid limitations
  • From: David Greaves <david@xxxxxxxxxxxx>
• RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• Re: questions about softraid limitations
  • From: David Greaves <david@xxxxxxxxxxxx>
• RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• [OT] Re: questions about softraid limitations
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: questions about softraid limitations
  • From: Neil Brown <neilb@xxxxxxx>
• Re: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: Twigathy <twigathy@xxxxxxxxx>
• RE: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• Re: (no subject): should have read--"Regarding thread '"Deleting mdadm RAID arrays'".
  • From: David Greaves <david@xxxxxxxxxxxx>
• ANNOUNCE: mdadm 2.6.5 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Linux Software RAID /sysfs repair issue
  • From: Neil Brown <neilb@xxxxxxx>
• Re: questions about softraid limitations
  • From: "Janos Haar" <djani22@xxxxxxxxxxxx>
• Re:
  • From: David Greaves <david@xxxxxxxxxxxx>
• [no subject]
  • From: "Henry, Andrew" <andrew.henry@xxxxxxxxxx>
• Re: questions about softraid limitations
  • From: David Greaves <david@xxxxxxxxxxxx>
• questions about softraid limitations
  • From: "Janos Haar" <djani22@xxxxxxxxxxxx>
• Linux Software RAID /sysfs repair issue
  • From: "Fairbanks, David" <David.Fairbanks@xxxxxxxxxxx>
• Re: Help recovering from failed disk on RAID 6
  • From: "Pascal Charest" <pascal.charest@xxxxxxxxx>
• RE: Help recovering from failed disk on RAID 6
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• RE: Help recovering from failed disk on RAID 6
  • From: "Steve Fairbairn" <steve@xxxxxxxxxxxxxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH] Remove blkdev warning triggered by using md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: mismatch_cnt questions
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: mismatch_cnt questions
  • From: Bas van Schaik <bas@xxxxxxxx>
• [no subject]
  • From: "me at tmr.com" <tmrbill@xxxxxxx>
• Re: howto and faq
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [PATCH] md: kill file_path wrapper
  • From: Neil Brown <neilb@xxxxxxx>
• Re: howto and faq
  • From: Neil Brown <neilb@xxxxxxx>
• Re: howto and faq
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: howto and faq
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: howto and faq
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: howto and faq
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: linux raid faq
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: linux raid faq
  • From: Janek Kozicki <janek_listy@xxxxx>
• Re: What to do when repair does not fix mismatch_cnt to 0 (2.6.25.1)?
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• What to do when repair does not fix mismatch_cnt to 0 (2.6.25.1)?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: howto and faq
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: howto and faq
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: linux raid faq
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Has anyone compared SWRAID for (JBOD@HW-RAID) vs. (Regular Sata PCI-e cards)?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Q. Recovering concatenated array from disk images?
  • From: Graham King <linuxraid@xxxxxxxxxxxxxx>
• Re: partitioned mirror vs. mirrors of partitions?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• [PATCH] md: kill file_path wrapper
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: partitioned mirror vs. mirrors of partitions?
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: partitioned mirror vs. mirrors of partitions?
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: partitioned mirror vs. mirrors of partitions?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: mdadm feature suggestion
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: partitioned mirror vs. mirrors of partitions?
  • From: michael@xxxxxxxxx
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Neil Brown <neilb@xxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Neil Brown <neilb@xxxxxxx>
• partitioned mirror vs. mirrors of partitions?
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: two questions re. proactive recovery and forced assembly
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: "Greg Cormier" <gcormier@xxxxxxxxx>
• Re: Autostarting arrays with V1 metadata
  • From: Bryan Mesich <bryan.mesich@xxxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: Andrew Farley <andrew@xxxxxxxxxxxxx>
• Re: Booting off of RAID10 versus RAID1
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Booting off of RAID10 versus RAID1
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Re: two questions re. proactive recovery and forced assembly
  • From: rosenfield.albert@xxxxxxxxx
• Re: Autostarting arrays with V1 metadata
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Multipath behavior
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Autostarting arrays with V1 metadata
  • From: Neil Brown <neilb@xxxxxxx>
• Re: two questions re. proactive recovery and forced assembly
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Autostarting arrays with V1 metadata
  • From: Ben Winslow <rain@xxxxxxxxxxxxxx>
• Re: mdadm create corrupted md data?
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: "Hardy Garten" <mailingliste@xxxxxxx>
• Re: two questions re. proactive recovery and forced assembly
  • From: rosenfield.albert@xxxxxxxxx
• Re: two questions re. proactive recovery and forced assembly
  • From: rosenfield.albert@xxxxxxxxx
• Re: Multiple siI SATA cards and data corruption
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: mdadm create corrupted md data?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: mdadm create corrupted md data?
  • From: Marc MERLIN <marc_news@xxxxxxxxxxx>
• Re: mdadm create corrupted md data?
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: Multiple siI SATA cards and data corruption
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Multiple siI SATA cards and data corruption
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: [RFC PATCH] md: towards a replacement for the raid5 STRIPE_OP_* flags
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: mdadm create corrupted md data?
  • From: Marc MERLIN <marc_news@xxxxxxxxxxx>
• Re: Resize / file system and create /home in existing raid 1
  • From: "Tiago Pinheiro" <tpinheiro@xxxxxxxxx>
• Re: How to grow RAID1 mirror on top of LVM?
  • From: Russ Hammer <russ@xxxxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: Resize / file system and create /home in existing raid 1
  • From: Markus Hochholdinger <Markus@xxxxxxxxxxxxxxxxx>
• Re: how to recreate a raid5 array with n-1 drives?
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Neil Brown <neilb@xxxxxxx>
• how to recreate a raid5 array with n-1 drives?
  • From: Marc MERLIN <marc_news@xxxxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: mdadm raid1 stops to work after kernel panic
  • From: Federico <undicizeri@xxxxxxxxx>
• Re: [RFC PATCH] md: towards a replacement for the raid5 STRIPE_OP_* flags
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm raid1 stops to work after kernel panic
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm feature suggestion
  • From: Neil Brown <neilb@xxxxxxx>
• [RFC PATCH] md: towards a replacement for the raid5 STRIPE_OP_* flags
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Resize / file system and create /home in existing raid 1
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Resize / file system and create /home in existing raid 1
  • From: "Tiago Pinheiro" <tpinheiro@xxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: Software RAID partitions not detected at boot time with linux 2.6.25.1.
  • From: Joao Luis Meloni Assirati <assirati@xxxxxxxxxxxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: non-fresh from initrd, all fine when assembling manually
  • From: Markus Hochholdinger <Markus@xxxxxxxxxxxxxxxxx>
• Re: Software RAID partitions not detected at boot time with linux 2.6.25.1.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: mdadm raid1 stops to work after kernel panic
  • From: Federico <undicizeri@xxxxxxxxx>
• Re: mdadm raid1 stops to work after kernel panic
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: mdadm raid1 stops to work after kernel panic
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: WARNING in 2.6.25-07422-gb66e1f1
  • From: Neil Brown <neilb@xxxxxxx>
• Re: How to grow RAID1 mirror on top of LVM?
  • From: Lars Täuber <taeuber@xxxxxxx>
• mdadm raid1 stops to work after kernel panic
  • From: Federico <undicizeri@xxxxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: "Greg Cormier" <gcormier@xxxxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Software RAID partitions not detected at boot time with linux 2.6.25.1.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: How to grow RAID1 mirror on top of LVM?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Software RAID partitions not detected at boot time with linux 2.6.25.1.
  • From: Joao Luis Meloni Assirati <assirati@xxxxxxxxxxxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• RE: Sleeping hard drives in an array?
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• RE: Sharing disks amoung multiple software RAIDs
  • From: Kasper Sandberg <lkml@xxxxxxxxxxx>
• RE: Sharing disks amoung multiple software RAIDs
  • From: Alex Davis <alex14641@xxxxxxxxx>
• RE: Sleeping hard drives in an array?
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: berk walker <berk@xxxxxxxxx>
• RE: Sharing disks amoung multiple software RAIDs
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Alex Davis <alex14641@xxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Kasper Sandberg <lkml@xxxxxxxxxxx>
• [PATCH] md: fix raid5 'repair' operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [PATCH] md: fix raid5 'repair' operations
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] md: fix raid5 'repair' operations
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] md: fix raid5 'repair' operations
  • From: "George Spelvin" <linux@xxxxxxxxxxx>
• Re: How to grow RAID1 mirror on top of LVM?
  • From: Russ Hammer <russ@xxxxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Alex Davis <alex14641@xxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Helge Hafting <helge.hafting@xxxxxxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Richard Michael <rmichael-raid@xxxxxxxxxxxxxxxx>
• non-fresh from initrd, all fine when assembling manually
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: [PATCH] md: fix raid5 'repair' operations
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Alex Davis <alex14641@xxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: oops in linear_mergeable_bvec
  • From: "marco gaddoni" <marco.gaddoni@xxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: "George Spelvin" <linux@xxxxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Kasper Sandberg <lkml@xxxxxxxxxxx>
• Re: [PATCH] md: fix raid5 'repair' operations
  • From: Neil Brown <neilb@xxxxxxx>
• Re: How to grow RAID1 mirror on top of LVM?
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: "David Rees" <drees76@xxxxxxxxx>
• Re: oops in linear_mergeable_bvec
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH] md: fix raid5 'repair' operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: How to grow RAID1 mirror on top of LVM?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Can't get rid of RAID-5 mismatches
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• RE: Sharing disks amoung multiple software RAIDs
  • From: Kasper Sandberg <lkml@xxxxxxxxxxx>
• RE: Sharing disks amoung multiple software RAIDs
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: [PATCH 1/3] md: ping userspace on 'write-pending' events
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Alex Davis <alex14641@xxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Kasper Sandberg <lkml@xxxxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Nick Andrew <nick@xxxxxxxxxxxxxxx>
• Re: Raid5 grow interrupted, failed
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: parallel resync
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Can't get rid of RAID-5 mismatches
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: LSI SAS1068E based controllers and md RAID
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• RE: Can't get rid of RAID-5 mismatches
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Can't get rid of RAID-5 mismatches
  • From: "George Spelvin" <linux@xxxxxxxxxxx>
• Re: parallel resync
  • From: Bernd Schubert <bs@xxxxxxxxx>
• LSI SAS1068E based controllers and md RAID
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: [PATCH 1/3] md: ping userspace on 'write-pending' events
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Raid5 grow interrupted, failed
  • From: Twigathy <twigathy@xxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Alex Davis <alex14641@xxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Sharing disks amoung multiple software RAIDs
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Sharing disks amoung multiple software RAIDs
  • From: Alex Davis <alex14641@xxxxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Sleeping hard drives in an array?
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: parallel resync
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 2/3] md: ping userspace on 'stop' events
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 1/3] md: ping userspace on 'write-pending' events
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 3/3] md: add new / required locking for calls to blk_remove_plug and blk_plug_queue
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 3/3] md: add new / required locking for calls to blk_remove_plug and blk_plug_queue
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 3/3] md: add new / required locking for calls to blk_remove_plug and blk_plug_queue
  • From: Neil Brown <neilb@xxxxxxx>
• Sleeping hard drives in an array?
  • From: "Greg Cormier" <gcormier@xxxxxxxxx>
• Re: Keeping debian from auto-assembling
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: degraded array after reboot *again*
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Keeping debian from auto-assembling
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: diskinfo script
  • From: David Greaves <david@xxxxxxxxxxxx>
• [PATCH 3/3] md: add new / required locking for calls to blk_remove_plug and blk_plug_queue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2/3] md: ping userspace on 'stop' events
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 1/3] md: ping userspace on 'write-pending' events
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 0/3] A few more md patches for 2.6.26
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: diskinfo script
  • From: Bill Davidsen <davidsen@xxxxxxx>
• diskinfo script
  • From: Bill Davidsen <davidsen@xxxxxxx>
• RE: How to grow RAID1 mirror on top of LVM?
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: --no-degraded in mdadm.conf? / disable auto assembly
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: --no-degraded in mdadm.conf? / disable auto assembly
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: degraded array after reboot *again*
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• --no-degraded in mdadm.conf? / disable auto assembly
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• parallel resync
  • From: Bernd Schubert <bs@xxxxxxxxx>
• Re: Online resize
  • From: Wayne Gemmell <wayne@xxxxxxxxxxxxxxxx>
• Re: How to grow RAID1 mirror on top of LVM?
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: [PATCH 008 of 9] md: md: raid5 rate limit error printk
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 007 of 9] md: prevent duplicates in bind_rdev_to_array
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 008 of 9] md: md: raid5 rate limit error printk
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 007 of 9] md: prevent duplicates in bind_rdev_to_array
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• [PATCH 009 of 9] md: md: support blocking writes to an array on device failure
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 008 of 9] md: md: raid5 rate limit error printk
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 007 of 9] md: prevent duplicates in bind_rdev_to_array
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 005 of 9] md: Fix up switching md arrays between read-only and read-write
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 006 of 9] md: Remove a stray command from a copy and paste error in resync_start_store
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 9] md: Fix 'safemode' handling for external metadata.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 003 of 9] md: Reinitialise more mddev fields in do_md_stop.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 9] md: Skip all metadata update processing when using external metadata.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 9] md: Fix use after free when removing rdev via sysfs
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 9] md: Assorted patches for the 2.5.26 merge window
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Online resize
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [patch] limit error rate
  • From: Bernd Schubert <bernd-schubert@xxxxxx>
• RE: How to grow RAID1 mirror on top of LVM?
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: ahci slow transfer rate with kernel 2.6.23-2.6.25
  • From: "kyle" <kylewong@xxxxxxxxxx>
• Re: How to grow RAID1 mirror on top of LVM?
  • From: Lars Täuber <taeuber@xxxxxxx>
• RE: degraded array after reboot *again*
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• degraded array after reboot *again*
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• RE: mdadm crashing server?
  • From: Keith Roberts <keith@xxxxxxxxxxxx>
• RE: mdadm crashing server?
  • From: Luke Sheldrick <luke@xxxxxxxxxxxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: Keith Roberts <keith@xxxxxxxxxxxx>
• Re: mdadm crashing server?
  • From: Keith Roberts <keith@xxxxxxxxxxxx>
• mdadm crashing server?
  • From: Luke Sheldrick <luke@xxxxxxxxxxxxxxx>
• Help recovering from failed disk on RAID 6
  • From: "Joshua Johnson" <enigma2175@xxxxxxxxx>
• Re: [patch] limit error rate
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: Mark Hahn <hahn@xxxxxxxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: Keith Roberts <keith@xxxxxxxxxxxx>
• Re: Can't create partitions on raid, --auto=mdp not possible
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: Can't create partitions on raid, --auto=mdp not possible
  • From: michael@xxxxxxxxx
• Re: managing raid on Linux
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Can't create partitions on raid, --auto=mdp not possible
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Can't create partitions on raid, --auto=mdp not possible
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Bug(?) in raid10 (raid10,f2 - lvm2 - xen)
  • From: "Tomasz Nowak" <tnowak-p@xxxxxxxxxxxxx>
• Re: [patch] limit error rate
  • From: Bernd Schubert <bernd-schubert@xxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RE: managing raid on Linux
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RE: managing raid on Linux
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: PCI ATA EIDE cards and kernel drivers
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: managing raid on linux
  • From: "Ty! Boyack" <ty@xxxxxxxxxxxxxxxxxx>
• Re: managing raid on linux
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [patch] limit error rate
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Multipath behavior
  • From: "Billy Crook" <bcrook@xxxxxxxxxxxxxxxxxxxxxx>
• Re: PCI ATA EIDE cards and kernel drivers
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Incorrect array member slot assignment during assemble
  • From: jay@xxxxxxxxxxxxxxxxxxxxxxxxx
• PCI ATA EIDE cards and kernel drivers
  • From: Keith Roberts <keith@xxxxxxxxxxxx>
• RE: Incorrect array member slot assignment during assemble
  • From: carlos@xxxxxxxxxxxxxx (Carlos Carvalho)
• RE: Incorrect array member slot assignment during assemble
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Incorrect array member slot assignment during assemble
  • From: carlos@xxxxxxxxxxxxxx (Carlos Carvalho)
• Re: mdadm.conf unnecessary?
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• mdadm.conf unnecessary?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: migrating: degrade or grow
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: migrating: degrade or grow
  • From: michael@xxxxxxxxx
• Re: Incorrect array member slot assignment during assemble
  • From: jay@xxxxxxxxxxxxxxxxxxxxxxxxx
• ext3: how to determine mkfs parameters?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• migrating: degrade or grow
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: Incorrect array member slot assignment during assemble
  • From: carlos@xxxxxxxxxxxxxx (Carlos Carvalho)
• managing raid on linux
  • From: devzero@xxxxxx
• Incorrect array member slot assignment during assemble
  • From: jay@xxxxxxxxxxxxxxxxxxxxxxxxx
• RE: Need some information and help on mdadm in order to support it on IBM z Systems
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Need some information and help on mdadm in order to support it on IBM z Systems
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• RE: RAID1 == two different ARRAY in scan, and Q on read error corrected
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: RAID1 == two different ARRAY in scan, and Q on read error corrected
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: RAID1 == two different ARRAY in scan, and Q on read error corrected
  • From: Phil Lobbes <phil@xxxxxxxxxxxxxxxx>
• Re: Software/ Hardware RAID info
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• RE: Software/ Hardware RAID info
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: RAID1 == two different ARRAY in scan, and Q on read error corrected
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• RE: Software/ Hardware RAID info
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• RE: RAID1 == two different ARRAY in scan, and Q on read error corrected
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Software/ Hardware RAID info
  • From: Rick Bragg <lists@xxxxxxxxx>
• Re: RAID1 == two different ARRAY in scan, and Q on read error corrected
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• RAID1 == two different ARRAY in scan, and Q on read error corrected
  • From: Phil Lobbes <phil@xxxxxxxxxxxxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• RE: Re: Need some information and help on mdadm in order to support it on IBM z Systems
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Need some information and help on mdadm in order to support it on IBM z Systems
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Need some information and help on mdadm in order to support it on IBM z Systems
  • From: Jean-Baptiste Joret <JORET@xxxxxxxxxx>
• RE: Mapping physical disk block to logical block to selectively repair w/o forcing rescan
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Mapping physical disk block to logical block to selectively repair w/o forcing rescan
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Welcome to linux-raid
  • From: Ulrich Enslin <ulrichenslin@xxxxxxxxx>
• Re: Mapping physical disk block to logical block to selectively repair w/o forcing rescan
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• RE: Mapping physical disk block to logical block to selectively repair w/o forcing rescan
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Mapping physical disk block to logical block to selectively repair w/o forcing rescan
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: Mapping physical disk block to logical block to selectively repair w/o forcing rescan
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: Mapping physical disk block to logical block to selectively repair w/o forcing rescan
  • From: Janek Kozicki <janek_listy@xxxxx>
• RE: Mapping physical disk block to logical block to selectively repair w/o forcing rescan
  • From: "David Lethe" <david@xxxxxxxxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: soft-lockup in raid5 / 2.6.24
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Need some information and help on mdadm in order to support it on IBM z Systems
  • From: Jean-Baptiste Joret <JORET@xxxxxxxxxx>
• Re: soft-lockup in raid5 / 2.6.24
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Question: how to identify failing disk in a RAID1
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Question: how to identify failing disk in a RAID1
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Re: two questions re. proactive recovery and forced assembly
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• [patch] limit error rate
  • From: Bernd Schubert <bernd-schubert@xxxxxx>
• Re: Need some information and help on mdadm in order to support it on IBM z Systems
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: emergency recovery
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Need some information and help on mdadm in order to support it on IBM z Systems
  • From: Jean-Baptiste Joret <JORET@xxxxxxxxxx>
• Re: Data corruption on software RAID
  • From: Mikulas Patocka <mikulas@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: emergency recovery
  • From: "jeff sacksteder" <jsacksteder@xxxxxxxxx>
• Re: emergency recovery
  • From: "jeff sacksteder" <jsacksteder@xxxxxxxxx>
• Re: emergency recovery
  • From: john <john4lists@xxxxxxxxx>
• Re: emergency recovery
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: emergency recovery
  • From: john <john4lists@xxxxxxxxx>
• Re: mdadm Issue
  • From: Stuart Clouston <stuartc@xxxxxxxxxxxxxxxxx>
• two questions re. proactive recovery and forced assembly
  • From: rosenfield.albert@xxxxxxxxx
• Re: emergency recovery
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• emergency recovery
  • From: "jeff sacksteder" <jsacksteder@xxxxxxxxx>
• Re: Data corruption on software RAID
  • From: Mikulas Patocka <mikulas@xxxxxxxxxxxxxxxxxxxxxxxx>
• [PATCH] md: close a livelock window in handle_parity_checks5
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: drive failed, need help with interpretation / recovery
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Data corruption on software RAID
  • From: Bill Davidsen <davidsen@xxxxxxx>
• drive failed, need help with interpretation / recovery
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: Write-Intent Bitmaps and disk caches
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• RAID-6/External Bitmap Issues
  • From: Henry Huang <hwh6k@xxxxxxxxxxxxx>
• Re: Re-assembling a software RAID in which device names have changed.
  • From: Michal Soltys <soltys@xxxxxxxx>
• Write-Intent Bitmaps and disk caches
  • From: "Ty! Boyack" <ty@xxxxxxxxxxxxxxxxxx>
• Re: Re-assembling a software RAID in which device names have changed.
  • From: "Sean H." <silverwraithii@xxxxxxxxx>
• Re: Is it possilble to be "delay tolerant" or have "slow dropout" of unavailable components?
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: Re-assembling a software RAID in which device names have changed.
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Is it possilble to be "delay tolerant" or have "slow dropout" of unavailable components?
  • From: "Ty! Boyack" <ty@xxxxxxxxxxxxxxxxxx>
• Re: Is it possilble to be "delay tolerant" or have "slow dropout" of unavailable components?
  • From: Markus Hochholdinger <Markus@xxxxxxxxxxxxxxxxx>
• Re: Re-assembling a software RAID in which device names have changed.
  • From: "Sean H." <silverwraithii@xxxxxxxxx>
• Is it possilble to be "delay tolerant" or have "slow dropout" of unavailable components?
  • From: "Ty! Boyack" <ty@xxxxxxxxxxxxxxxxxx>
• Re: Re-assembling a software RAID in which device names have changed.
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Data corruption on software RAID
  • From: Mikulas Patocka <mikulas@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Data corruption on software RAID
  • From: Helge Hafting <helge.hafting@xxxxxxxxxxxxx>
• Re-assembling a software RAID in which device names have changed.
  • From: "Sean H." <silverwraithii@xxxxxxxxx>
• Re: soft-lockup in raid5 / 2.6.24
  • From: dean gaudet <dean@xxxxxxxxxx>
• Data corruption on software RAID
  • From: Mikulas Patocka <mikulas@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: soft-lockup in raid5 / 2.6.24
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: How to rename MD device (e.g. md3 -> md2)?
  • From: Zlatko Calusic <zlatko.calusic@xxxxxxxx>
• Re: How to rename MD device (e.g. md3 -> md2)?
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: How to rename MD device (e.g. md3 -> md2)?
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: how to disable partition search?
  • From: Ferenc Wagner <wferi@xxxxxxx>
• How to rename MD device (e.g. md3 -> md2)?
  • From: Zlatko Calusic <zlatko.calusic@xxxxxxxx>
• soft-lockup in raid5 / 2.6.24
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: how to disable partition search?
  • From: Ferenc Wagner <wferi@xxxxxxx>
• Re: how to disable partition search?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: INFO: task md1_resync:3897 blocked for more than 120 seconds.
  • From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
• INFO: task md1_resync:3897 blocked for more than 120 seconds.
  • From: Christian Kujau <christian@xxxxxxxxxxxxxxx>
• Re: performance problems with raid10,f2
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: performance problems with raid10,f2
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: RAID 1 failure on single disk causes disk subsystem to lock up
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: Can't grow raid5 size
  • From: Shane W <shane-kernel@xxxxxx>
• Re: segfault in mdadm v2.6.4
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: Can't grow raid5 size
  • From: Shane W <shane-kernel@xxxxxx>
• Re: segfault in mdadm v2.6.4
  • From: "Brett Dikeman" <brett@xxxxxxxxxx>
• Re: segfault in mdadm v2.6.4
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: segfault in mdadm v2.6.4
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: performance problems with raid10,f2
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• segfault in mdadm v2.6.4
  • From: Brett Dikeman <brett@xxxxxxxxxx>
• Re: RAID 1 failure on single disk causes disk subsystem to lock up
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: performance problems with raid10,f2
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: (was: Re: md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors])
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: (was: Re: md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors])
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: (was: Re: md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors])
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• [RFC][PATCH] md: avoid fullsync if a faulty member missed a dirty transition
  • From: Mike Snitzer <snitzer@xxxxxxxxx>
• Re: performance problems with raid10,f2
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: RAID 1 failure on single disk causes disk subsystem to lock up
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: RAID 1 failure on single disk causes disk subsystem to lock up
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: (was: Re: md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors])
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: (was: Re: md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors])
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: RAID 1 failure on single disk causes disk subsystem to lock up
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: (was: Re: md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors])
  • From: "Conway S. Smith" <beolach@xxxxxxxxx>
• Re: (was: Re: md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors])
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• (was: Re: md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors])
  • From: Beolach <beolach@xxxxxxxxx>
• Re: RAID 1 failure on single disk causes disk subsystem to lock up
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: RAID 1 failure on single disk causes disk subsystem to lock up
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: raid1 will force fullsync when it seemingly should not
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• raid1 will force fullsync when it seemingly should not
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: RAID 1 failure on single disk causes disk subsystem to lock up
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: RAID 1 failure on single disk causes disk subsystem to lock up
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: RAID 1 failure on single disk causes disk subsystem to lock up
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: Can't grow raid5 size
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: RAID 1 failure on single disk causes disk subsystem to lock up
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RAID 1 failure on single disk causes disk subsystem to lock up
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Can't grow raid5 size
  • From: Shane W <shane-kernel@xxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: raid10 vs raid5 - strange performance
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: Iustin Pop <iusty@xxxxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: Bill Davidsen <davidsen@xxxxxxx>
• md: raid5 vs raid10 (f2,n2,o2) benchmarks [w/10 raptors]
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: [PATCH] md: Subject: introduce get_priority_stripe() to improve raid456 write performance
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] md: Subject: introduce get_priority_stripe() to improve raid456 write performance
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [PATCH] md: Subject: introduce get_priority_stripe() to improve raid456 write performance
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Reopen: 16 HDDs too much for RAID6?
  • From: Bernd Schubert <bs@xxxxxxxxx>
• Re: Reopen: 16 HDDs too much for RAID6?
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: Reopen: 16 HDDs too much for RAID6?
  • From: Bernd Schubert <bs@xxxxxxxxx>
• Re: Reopen: 16 HDDs too much for RAID6?
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: Reopen: 16 HDDs too much for RAID6?
  • From: Bernd Schubert <bs@xxxxxxxxx>
• Reopen: 16 HDDs too much for RAID6?
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: component growing in raid5
  • From: Mattias Wadenstein <maswan@xxxxxxxxxx>
• Re: [PATCH] md: Subject: introduce get_priority_stripe() to improve raid456 write performance
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] md: Subject: introduce get_priority_stripe() to improve raid456 write performance
  • From: NeilBrown <neilb@xxxxxxx>
• Re: component growing in raid5
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: data corruption: ext3/lvm2/md/mptsas/vitesse/seagate
  • From: Marc Bejarano <beej@xxxxxxxxxxxx>
• Re: component growing in raid5
  • From: Mattias Wadenstein <maswan@xxxxxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Why are MD block IO requests subject to 'plugging'?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: how to disable partition search?
  • From: Ferenc Wagner <wferi@xxxxxxx>
• Re: uuids missing
  • From: bressen@xxxxxxxxx (Andrew K. Bressen)
• Re: how to disable partition search?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: MDP major registration
  • From: Bill Davidsen <davidsen@xxxxxxx>
• uuids missing
  • From: akb+lists.linux-raid@xxxxxxxxx (Andrew K. Bressen)
• [PATCH] XFS tuning on software RAID5 partitionable array; was: MDP major registration
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: MDP major registration
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: data corruption: ext3/lvm2/md/mptsas/vitesse/seagate
  • From: "Grant Grundler" <grundler@xxxxxxxxxx>
• Re: raid, lvm, and reused disks crashing initramfs
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: MDP major registration
  • From: Bill Davidsen <davidsen@xxxxxxx>
• how to disable partition search?
  • From: Ferenc Wagner <wferi@xxxxxxx>
• raid, lvm, and reused disks crashing initramfs
  • From: akb+lists.linux-raid@xxxxxxxxx (Andrew K. Bressen)
• Re: What do Events actually mean?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: What do Events actually mean?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: MDP major registration
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: data corruption: ext3/lvm2/md/mptsas/vitesse/seagate
  • From: Marc Bejarano <beej@xxxxxxxxxxxx>
• RE: mismatch_cnt of 128 and 1408.
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• Re: data corruption: ext3/lvm2/md/mptsas/vitesse/seagate
  • From: "Grant Grundler" <grundler@xxxxxxxxxx>
• Re: data corruption: ext3/lvm2/md/mptsas/vitesse/seagate
  • From: Marc Bejarano <beej@xxxxxxxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: raid10 vs raid5 - strange performance
  • From: "David Rees" <drees76@xxxxxxxxx>
• raid10 vs raid5 - strange performance
  • From: "Christian Pernegger" <pernegger@xxxxxxxxx>
• Re: component growing in raid5
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Why are MD block IO requests subject to 'plugging'?
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: MDP major registration
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Re: irc channel for linux-raid
  • From: Janek Kozicki <janek_listy@xxxxx>
• Re: Verifying spare drive, best practices
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: irc channel for linux-raid
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Verifying spare drive, best practices
  • From: Peter Evertz <leo2@xxxxxxxxxxxxxx>
• Re: component growing in raid5
  • From: Mattias Wadenstein <maswan@xxxxxxxxxx>
• Re: performance problems with raid10,f2
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: component growing in raid5
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: mismatch_cnt of 128 and 1408.
  • From: Janek Kozicki <janek_listy@xxxxx>
• Why are MD block IO requests subject to 'plugging'?
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: performance problems with raid10,f2
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Mattias Wadenstein <maswan@xxxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: How to grow RAID1 mirror on top of LVM?
  • From: Anton Altaparmakov <aia21@xxxxxxxxx>
• Re: MDP major registration
  • From: Neil Brown <neilb@xxxxxxx>
• Re: How to grow RAID1 mirror on top of LVM?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID5 initial resync: faster vs more secure
  • From: Neil Brown <neilb@xxxxxxx>
• Re: performance problems with raid10,f2
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm -A erased the superblock ?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Verifying spare drive, best practices
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: xfs+md(raid5) xfssyncd & kswapd & pdflush hung in d-state
  • From: Nagy Zoltan <kirk@xxxxxxxx>
• Re: What do Events actually mean?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Task blocked for more than 120 seconds
  • From: Neil Brown <neilb@xxxxxxx>
• Re: FW: [PATCH 008 of 9] md: Fix possible raid1/raid10 deadlock on read error during resync.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mismatch_cnt of 128 and 1408.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: xfs+md(raid5) xfssyncd & kswapd & pdflush hung in d-state
  • From: David Chinner <dgc@xxxxxxx>
• Re: mdadm what does it mean
  • From: Kenneth Aar <kenneth@xxxxxxxxxxxx>
• Re: mismatch_cnt of 128 and 1408.
  • From: Oliver Martin <oliver.martin@xxxxxxxxxxxxxxxxxxxx>
• Re: FW: [PATCH 008 of 9] md: Fix possible raid1/raid10 deadlock on read error during resync.
  • From: "John Z." <md2sf@xxxxxxxx>
• Re: component growing in raid5
  • From: Nagy Zoltan <kirk@xxxxxxxx>
• Re: component growing in raid5
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: component growing in raid5
  • From: Nagy Zoltan <kirk@xxxxxxxx>
• Task blocked for more than 120 seconds
  • From: Samuel Tardieu <sam@xxxxxxxxxxx>
• mismatch_cnt of 128 and 1408.
  • From: Janek Kozicki <janek_listy@xxxxx>
• Re: component growing in raid5
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: component growing in raid5
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: component growing in raid5
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• component growing in raid5
  • From: Nagy Zoltan <kirk@xxxxxxxx>
• Re: Help: Re-assemble raid-5 with inconsistent events.
  • From: Arthur Britto <ahbritto@xxxxxxx>
• Re: What do Events actually mean?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: What do Events actually mean?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: What do Events actually mean?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Help: Re-assemble raid-5 with inconsistent events.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Verifying spare drive, best practices
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: mdadm -A erased the superblock ?
  • From: Pradeep <pradeepjp@xxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Bas van Schaik <bas@xxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Theodore Tso <tytso@xxxxxxx>
• What do Events actually mean?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Help: Re-assemble raid-5 with inconsistent events.
  • From: Arthur Britto <ahbritto@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: carlos@xxxxxxxxxxxxxx (Carlos Carvalho)
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Ric Wheeler <ric@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: mdadm -A erased the superblock ?
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Theodore Tso <tytso@xxxxxxx>
• Re: Verifying spare drive, best practices
  • From: carlos@xxxxxxxxxxxxxx (Carlos Carvalho)
• Re: the '--setra 65536' mistery, analysis and WTF?
  • From: Nat Makarevitch <nat@xxxxxxxxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Ric Wheeler <ric@xxxxxxx>
• Verifying spare drive, best practices
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• mdadm -A erased the superblock ?
  • From: Pradeep <pradeepjp@xxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Theodore Tso <tytso@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: performance problems with raid10,f2
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• RAID5 initial resync: faster vs more secure
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Theodore Tso <tytso@xxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: mdadm what does it mean
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Bas van Schaik <bas@xxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Bas van Schaik <bas@xxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Redundancy check using "echo check > sync_action": error reporting?
  • From: Bas van Schaik <bas@xxxxxxxx>
• Re: the '--setra 65536' mistery, analysis and WTF?
  • From: pg_lxra@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Change Chunk Size on Array?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: ioatdma
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• mdadm what does it mean
  • From: Kenneth Aar <kenneth@xxxxxxxxxxxx>