Linux RAID Storage Date Index

• Thread Index

• Re: spare group
  • From: Tomka Gergely <tomka@xxxxxxxxxx>
• RFC: dealing with bad blocks: another view
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: Neil Brown <neilb@xxxxxxx>
• raid1 with nbd member hangs MD on SLES10 and RHEL5
  • From: "Mike Snitzer" <snitzer@xxxxxxxxx>
• Re: raid5: coding style cleanup / refactor
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• RE: raid5: coding style cleanup / refactor
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: raid5: coding style cleanup / refactor
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Mdadm recovery in infinite loop
  • From: "Kyle Harris" <kyle@xxxxxxxxxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [PATCH 000 of 2] md: Introduction - bugfixes for md/raid{1,10}
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: SLES 9 SP3 and mdadm 2.6.1 (via rpm)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Some RAID levels do not support bitmap
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: spare group
  • From: Neil Brown <neilb@xxxxxxx>
• Re: spare group
  • From: Tomka Gergely <tomka@xxxxxxxxxx>
• Re: SLES 9 SP3 and mdadm 2.6.1 (via rpm)
  • From: Neil Brown <neilb@xxxxxxx>
• SLES 9 SP3 and mdadm 2.6.1 (via rpm)
  • From: "Thorsten Wolf" <T_Wolf@xxxxxxx>
• Re: spare group
  • From: Neil Brown <neilb@xxxxxxx>
• Re: spare group
  • From: Tomka Gergely <tomka@xxxxxxxxxx>
• [PATCH]is_power_of_2-dm
  • From: vignesh babu <vignesh.babu@xxxxxxxxx>
• Re: conflicting superblocks - Re: what is the best approach for fixing a degraded RAID5 (one drive failed) using mdadm?
  • From: Neil Brown <neilb@xxxxxxx>
• conflicting superblocks - Re: what is the best approach for fixing a degraded RAID5 (one drive failed) using mdadm?
  • From: simon redfern <simon@xxxxxxxxxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• [PATCH 002 of 2] md: Fix bug in error handling during raid1 repair.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 2] md: Introduction - bugfixes for md/raid{1,10}
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 2] md: Fix two raid10 bugs.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: spare group
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Some RAID levels do not support bitmap
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Some RAID levels do not support bitmap
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Paranoid read mode for raid5/6
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Paranoid read mode for raid5/6
  • From: Mattias Wadenstein <maswan@xxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• spare group
  • From: Tomka Gergely <tomka@xxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: below 10MB/s write on raid5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• what is the best approach for fixing a degraded RAID5 (one drive failed) using mdadm?
  • From: simon redfern <simon@xxxxxxxxxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Some RAID levels do not support bitmap
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: LVM on raid10 - severe performance drop
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: below 10MB/s write on raid5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• below 10MB/s write on raid5
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: RAID 6 grow problem
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Iain Rauch <groups@xxxxxxxxxxxxxxxxxxxxxx>
• Re: LVM on raid10 - severe performance drop
  • From: Bernd Schubert <bs@xxxxxxxxx>
• LVM on raid10 - severe performance drop
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: question about --assume-clean
  • From: Neil Brown <neilb@xxxxxxx>
• question about --assume-clean
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: Help on Recovering a Corrupted raid5 Partition
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Help on Recovering a Corrupted raid5 Partition
  • From: Neil Brown <neilb@xxxxxxx>
• Help on Recovering a Corrupted raid5 Partition
  • From: phyros <dlopuch@xxxxxxx>
• [patch 06/54] md: Dont write more than is required of the last page of a bitmap
  • From: Chris Wright <chrisw@xxxxxxxxxxxx>
• [patch 05/54] md: Avoid overflow in raid0 calculation with large components.
  • From: Chris Wright <chrisw@xxxxxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Regarding odd RAID5 I/O patterns
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Regarding odd RAID5 I/O patterns
  • From: Neil Brown <neilb@xxxxxxx>
• Regarding odd RAID5 I/O patterns
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• RE: RAID 6 grow problem
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• RE: RAID 6 grow problem
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• RE: RAID 6 grow problem
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Iustin Pop <iusty@xxxxxxxxx>
• bug report on mdadm --export
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Iustin Pop <iusty@xxxxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: Customize the error emails of `mdadm --monitor`
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• [PATCH] md: comment add_stripe_bio
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• RE: RAID 6 grow problem
  • From: Neil Brown <neilb@xxxxxxx>
• RE: RAID 6 grow problem
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• RE: RAID 6 grow problem
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Iain Rauch <groups@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID 6 grow problem
  • From: Bill Davidsen <davidsen@xxxxxxx>
• RE: multiple xor_block() functions
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: problems with faulty disks and superblocks 1.0, 1.1 and 1.2
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• minimum speed for raid5 check
  • From: carlos@xxxxxxxxxxxxxx (Carlos Carvalho)
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: RAID6 clean?
  • From: Neil Brown <neilb@xxxxxxx>
• RAID6 clean?
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• RE: RAID 6 grow problem
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: 5 HDD RAID5 not starting after controller failure
  • From: Karsten Desler <kdesler@xxxxxxxxxx>
• Re: 5 HDD RAID5 not starting after controller failure
  • From: Neil Brown <neilb@xxxxxxx>
• 5 HDD RAID5 not starting after controller failure
  • From: Karsten Desler <kdesler@xxxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: tj <lists@xxxxxxxx>
• RE: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Iain Rauch <groups@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID 6 grow problem
  • From: Iain Rauch <groups@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID 6 grow problem
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Iain Rauch <groups@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: multiple xor_block() functions
  • From: Jouni Malinen <j@xxxxx>
• multiple xor_block() functions
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: RAID 6 grow problem
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RAID 6 grow problem
  • From: Iain Rauch <groups@xxxxxxxxxxxxxxxxxxxxxx>
• Customize the error emails of `mdadm --monitor`
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: When does a disk get flagged as bad?
  • From: Alberto Alonso <alberto@xxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: When does a disk get flagged as bad?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Valdis.Kletnieks@xxxxxx
• Re: RAID SB 1.x autodetection
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• possible logic bug in raid5.c
  • From: Jens Laas <jens.laas@xxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: david@xxxxxxx
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: raid1 check/repair read error recovery in 2.6.20
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: david@xxxxxxx
• MD device flag from spare to active
  • From: Philip Bergen <philip.bergen@xxxxxxxxx>
• Re: RAID SB 1.x autodetection
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: very strange (maybe) raid1 testing results
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID SB 1.x autodetection
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Stefan Bader" <Stefan.Bader@xxxxxxxxxx>
• problems with faulty disks and superblocks 1.0, 1.1 and 1.2
  • From: Hubert Verstraete <hubskml@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: When does a disk get flagged as bad?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: Neil Brown <neilb@xxxxxxx>
• Re: very strange (maybe) raid1 testing results
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Creating RAID1 with bitmap fails
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: very strange (maybe) raid1 testing results
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: very strange (maybe) raid1 testing results
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: When does a disk get flagged as bad?
  • From: Alberto Alonso <alberto@xxxxxxxxx>
• Re: very strange (maybe) raid1 testing results
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: When does a disk get flagged as bad?
  • From: Mike Accetta <maccetta@xxxxxxxxxxxxxxxxxx>
• very strange (maybe) raid1 testing results
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: Creating RAID1 with bitmap fails
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID SB 1.x autodetection
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: RAID SB 1.x autodetection
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: RAID SB 1.x autodetection
  • From: Bill Davidsen <davidsen@xxxxxxx>
• dm-crypt issue
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: RAID SB 1.x autodetection
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: david@xxxxxxx
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Creating RAID1 with bitmap fails
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: mismatch_cnt = 128 for root (/) md raid1 device
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Creating RAID1 with bitmap fails
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Creating RAID1 with bitmap fails
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: ANNOUNCE: mdadm 2.6.2 - A tool for managing Soft RAID under Linux
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Stefan Bader" <Stefan.Bader@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Stefan Bader" <Stefan.Bader@xxxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: ANNOUNCE: mdadm 2.6.2 - A tool for managing Soft RAID under Linux
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: david@xxxxxxx
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: ANNOUNCE: mdadm 2.6.2 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid10 kernel panic on sparc64
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• RAID SB 1.x autodetection
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: ANNOUNCE: mdadm 2.6.2 - A tool for managing Soft RAID under Linux
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Stefan Bader" <sbader3@xxxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Stefan Bader" <sbader3@xxxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jeremy Higdon <jeremy@xxxxxxx>
• Re: Reshaping raid0/10
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Alberto Alonso <alberto@xxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Alberto Alonso <alberto@xxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid state diagram
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Nikita Danilov <nikita@xxxxxxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Timothy Shimmin <tes@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• assemble array without rebuild - readonly mode?
  • From: Tim Harvey <tim_harvey@xxxxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: tj <lists@xxxxxxxx>
• Re: raid10 kernel panic on sparc64
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: raid10 kernel panic on sparc64
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• raid state diagram
  • From: Tomka Gergely <tomka@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Tejun Heo <htejun@xxxxxxxxx>
• mismatch_cnt = 128 for root (/) md raid1 device
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Andreas Dilger <adilger@xxxxxxxxxxxxx>
• Re: [dm-devel] [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [dm-devel] Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: "Stefan Bader" <Stefan.Bader@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: David Chinner <dgc@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Alberto Alonso <alberto@xxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• When does a disk get flagged as bad?
  • From: Alberto Alonso <alberto@xxxxxxxxx>
• raid1 check/repair read error recovery in 2.6.20
  • From: Mike Accetta <maccetta@xxxxxxxxxxxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: David Chinner <dgc@xxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: Thomas Jager <lists@xxxxxxxx>
• Re: Fwd: Identify SATA Disks
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: Fwd: Identify SATA Disks
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: Fwd: Identify SATA Disks
  • From: Colin McCabe <Colin.P.McCabe@xxxxxxxxx>
• Re: Fwd: Identify SATA Disks
  • From: Colin McCabe <Colin.P.McCabe@xxxxxxxxx>
• Re: raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• raid5: I lost a XFS file system due to a minor IDE cable problem
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Fwd: Identify SATA Disks
  • From: "lewis shobbrook" <lewis@xxxxxxxxxxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Raid-5 long write wait while reading
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• I/O errors, server unresponsive, array NOT-degraded
  • From: Alberto Alonso <alberto@xxxxxxxxx>
• Re: mdadm on huge raid sets
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Bill Davidsen <davidsen@xxxxxxx>
• mdadm on huge raid sets
  • From: Erich Weiler <weiler@xxxxxxxxxxxx>
• Raid-5 long write wait while reading
  • From: Thomas Jager <lists@xxxxxxxx>
• Re: Adding larger disks to RAID5
  • From: "Bill Rugolsky Jr." <brugolsky@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: not resyncing after power cut.
  • From: "Chris Fanning" <christopher.fanning@xxxxxxxxx>
• Re: not resyncing after power cut.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm, raid10, and problem
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Adding larger disks to RAID5
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Adding larger disks to RAID5
  • From: "Bill Rugolsky Jr." <brugolsky@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Adding larger disks to RAID5
  • From: Neil Brown <neilb@xxxxxxx>
• Adding larger disks to RAID5
  • From: Christian <cjs@xxxxxxx>
• Re: not resyncing after power cut.
  • From: thunder7@xxxxxxxxx
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• [patch 39/69] md: Avoid a possibility that a read error can wrongly propagate through md/raid1 to a filesystem.
  • From: Chris Wright <chrisw@xxxxxxxxxxxx>
• not resyncing after power cut.
  • From: "Chris Fanning" <christopher.fanning@xxxxxxxxx>
• ANNOUNCE: mdadm 2.6.2 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH 007 of 7] md: Change bitmap_unplug and others to void functions.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 006 of 7] md: Check that internal bitmap does not overlap other data.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 005 of 7] md: Improve the is_mddev_idle test fix
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 7] md: Improve message about invalid superblock during autodetect.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 003 of 7] md: Fix bug with linear hot-add and elsewhere.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 7] md: Don't write more than is required of the last page of a bitmap
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 7] md: Avoid overflow in raid0 calculation with large components.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 7] md: Introduction EXPLAIN PATCH SET HERE
  • From: NeilBrown <neilb@xxxxxxx>
• mdadm, raid10, and problem
  • From: "Maciej 'Agaran' Pijanka" <agaran@xxxxxxxxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: "Colin McCabe" <colin.p.mccabe@xxxxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: Colin McCabe <Colin.P.McCabe@xxxxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: Andrew Burgess <aab@xxxxxxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: "Jeff Zheng" <Jeff.Zheng@xxxxxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: "Jeff Zheng" <Jeff.Zheng@xxxxxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: "Jeff Zheng" <Jeff.Zheng@xxxxxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: david@xxxxxxx
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: "Jeff Zheng" <Jeff.Zheng@xxxxxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: "Jeff Zheng" <Jeff.Zheng@xxxxxxxxxx>
• Re: Md corruption using RAID10 on linux-2.6.21
  • From: Neil Brown <neilb@xxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Neil Brown <neilb@xxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: "Colin McCabe" <colin.p.mccabe@xxxxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: "Colin McCabe" <colin.p.mccabe@xxxxxxxxx>
• Md corruption using RAID10 on linux-2.6.21
  • From: "Don Dupuis" <dondster@xxxxxxxxx>
• Re: Software raid0 will crash the file-system, when each disk is 5TB
  • From: david@xxxxxxx
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: unreadable drives can be synchronized?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Recovery of software RAID5 using FC6 rescue?
  • From: "Mark A. O'Neil" <mark.a.oneil@xxxxxxxxxxxxx>
• unreadable drives can be synchronized?
  • From: "Colin McCabe" <colin.p.mccabe@xxxxxxxxx>
• RE: Software raid0 will crash the file-system, when each disk is 5TB
  • From: "Jeff Zheng" <Jeff.Zheng@xxxxxxxxxx>
• Re: Software raid0 will crash the file-system, when each disk is 5TB
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Software raid0 will crash the file-system, when each disk is 5TB
  • From: "Michal Piotrowski" <michal.k.k.piotrowski@xxxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Gregory Seidman <gsslist+linuxraid@xxxxxxxxxxxxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: removed disk && md-device
  • From: Goswin von Brederlow <brederlo@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: how to synchronize two devices (RAID-1, but not really?)
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• how to synchronize two devices (RAID-1, but not really?)
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: /proc/mdstat showing a device missing from array
  • From: Neil Brown <neilb@xxxxxxx>
• Re: /proc/mdstat showing a device missing from array
  • From: evoltech@xxxxxxxxxxx
• Re: /proc/mdstat showing a device missing from array
  • From: Neil Brown <neilb@xxxxxxx>
• /proc/mdstat showing a device missing from array
  • From: evoltech@xxxxxxxxxxx
• Re: Neil, bug in the minimum guaranteed patch?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Questions about the speed when MD-RAID array is being initialized.
  • From: Benjamin Davenport <ben@xxxxxxxxxxxxxxx>
• Neil, bug in the minimum guaranteed patch?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: removed disk && md-device
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: removed disk && md-device
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: removed disk && md-device
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: removed disk && md-device
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: removed disk && md-device
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: 2.6.21-mm2 boot failure, raid autodetect, bd_set_size+0xb/0x80
  • From: thunder7@xxxxxxxxx
• Re: 2.6.21-mm2 boot failure, raid autodetect, bd_set_size+0xb/0x80
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: 2.6.21-mm2 boot failure, raid autodetect, bd_set_size+0xb/0x80
  • From: thunder7@xxxxxxxxx
• Re: removed disk && md-device
  • From: Bernd Schubert <bs@xxxxxxxxx>
• Re: removed disk && md-device
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: removed disk && md-device
  • From: Neil Brown <neilb@xxxxxxx>
• Re: removed disk && md-device
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Please revert 5b479c91da90eef605f851508744bfe8269591a0 (md partition rescan)
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Questions about the speed when MD-RAID array is being initialized.
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Chaining sg lists for big I/O commands: Question
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: Questions about the speed when MD-RAID array is being initialized.
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Questions about the speed when MD-RAID array is being initialized.
  • From: "Liang Yang" <multisyncfe991@xxxxxxxxxxx>
• Re: Questions about the speed when MD-RAID array is being initialized.
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Questions about the speed when MD-RAID array is being initialized.
  • From: "Liang Yang" <multisyncfe991@xxxxxxxxxxx>
• Re: Please revert 5b479c91da90eef605f851508744bfe8269591a0 (md partition rescan)
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: Chaining sg lists for big I/O commands: Question
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: removed disk && md-device
  • From: Bernd Schubert <bs@xxxxxxxxx>
• Re: Please revert 5b479c91da90eef605f851508744bfe8269591a0 (md partition rescan)
  • From: "Satyam Sharma" <satyam.sharma@xxxxxxxxx>
• Re: [PATCH 00/16] raid acceleration and asynchronous offload api for 2.6.22
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: Please revert 5b479c91da90eef605f851508744bfe8269591a0 (md partition rescan)
  • From: Xavier Bestel <xavier.bestel@xxxxxxx>
• Re: Please revert 5b479c91da90eef605f851508744bfe8269591a0 (md partition rescan)
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• RE: [PATCH 00/16] raid acceleration and asynchronous offload api for 2.6.22
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: removed disk && md-device
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: [PATCH 002 of 2] md: Improve the is_mddev_idle test
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: [PATCH 002 of 2] md: Improve the is_mddev_idle test
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 002 of 2] md: Improve the is_mddev_idle test
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: [PATCH 002 of 2] md: Improve the is_mddev_idle test
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 002 of 2] md: Improve the is_mddev_idle test
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: removed disk && md-device
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH 002 of 2] md: Improve the is_mddev_idle test
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 2] md: Avoid a possibility that a read error can wrongly propagate through md/raid1 to a filesystem.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 2] md: Two more bugfixes.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: "No such device" on --remove
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Re: Please revert 5b479c91da90eef605f851508744bfe8269591a0 (md partition rescan)
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Please revert 5b479c91da90eef605f851508744bfe8269591a0 (md partition rescan)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: removed disk && md-device
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: "No such device" on --remove
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Recovery of software RAID5 using FC6 rescue?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Chaining sg lists for big I/O commands: Question
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: removed disk && md-device
  • From: Bernd Schubert <bs@xxxxxxxxx>
• Chaining sg lists for big I/O commands: Question
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: removed disk && md-device
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• RE: [PATCH 00/16] raid acceleration and asynchronous offload api for 2.6.22
  • From: "Ronen Shitrit" <rshitrit@xxxxxxxxxxx>
• removed disk && md-device
  • From: Bernd Schubert <bs@xxxxxxxxx>
• Re: "No such device" on --remove
  • From: Bernd Schubert <bschubert@xxxxxxxxx>
• Re: Recovery of software RAID5 using FC6 rescue?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Linux MD Raid Bug(?) w/Kernel sync_speed_min Option
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Recovery of software RAID5 using FC6 rescue?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Recovery of software RAID5 using FC6 rescue?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: "No such device" on --remove
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Recovery of software RAID5 using FC6 rescue?
  • From: "Mark A. O'Neil" <mark.a.oneil@xxxxxxxxxxxxx>
• "No such device" on --remove
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Re: Speed variation depending on disk position
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: what does md do if it finds an inconsistency?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Linux MD Raid Bug(?) w/Kernel sync_speed_min Option
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Linux MD Raid Bug(?) w/Kernel sync_speed_min Option
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Linux MD Raid Bug(?) w/Kernel sync_speed_min Option
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Swapping out for larger disks
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• Linux MD Raid Bug(?) w/Kernel sync_speed_min Option
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Swapping out for larger disks
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Swapping out for larger disks
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Swapping out for larger disks
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• Re: Raid-1 on top of multipath
  • From: Lars Marowsky-Bree <lmb@xxxxxxx>
• [PATCH 002 of 5] md: Stop using csum_partial for checksum calculation in md.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 005 of 5] md: Improve partition detection in md array.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 5] md: Allow reshape_position for md arrays to be set via sysfs.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 5] md: Move test for whether level supports bitmap to correct place.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 003 of 5] md: Remove the slash from the name of a kmem_cache used by raid5.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 5] md: assorted bug fixes and minor features
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid1 replaced with raid10?
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: Raid1 replaced with raid10?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• RAID defns
  • From: raider@xxxxxxxxxxxxx
• Re: mdadm array not found on reboot
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: mdadm array not found on reboot
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: mdadm array not found on reboot
  • From: "Jeffrey B. Layton" <laytonjb@xxxxxxxxxxx>
• Re: mdadm array not found on reboot
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: mdadm array not found on reboot
  • From: "Jeffrey B. Layton" <laytonjb@xxxxxxxxxxx>
• Re: mdadm array not found on reboot
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• mdadm array not found on reboot
  • From: "Jeffrey B. Layton" <laytonjb@xxxxxxxxxxx>
• Fwd: attempt to access beyond end of device on RAID0 with mdadm
  • From: "Sławomir Nowakowski" <nailman23@xxxxxxxxx>
• Re: Partitioned arrays initially missing from /proc/partitions
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Partitioned arrays initially missing from /proc/partitions
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Raid1 replaced with raid10?
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: Raid1 replaced with raid10?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Raid1 replaced with raid10?
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: attempt to access beyond end of device on RAID0 with mdadm
  • From: Neil Brown <neilb@xxxxxxx>
• RE: RAID6 question
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Raid1 replaced with raid10?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: what does md do if it finds an inconsistency?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Speed variation depending on disk position
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: what does md do if it finds an inconsistency?
  • From: Gavin McCullagh <gmccullagh@xxxxxxxxx>
• Re: Speed variation depending on disk position (was: Linux SW RAID: HW Raid Controller/JBOD vs. Multiple PCI-e Cards?)
  • From: Mark Hahn <hahn@xxxxxxxxxxx>
• Re: what does md do if it finds an inconsistency?
  • From: "martin f krafft" <madduck@xxxxxxxxxxx>
• Re: what does md do if it finds an inconsistency?
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: what does md do if it finds an inconsistency?
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Re: Speed variation depending on disk position
  • From: Benjamin Davenport <linux-raid-reg@xxxxxxxxxxxxxxx>
• what does md do if it finds an inconsistency?
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Speed variation depending on disk position (was: Linux SW RAID: HW Raid Controller/JBOD vs. Multiple PCI-e Cards?)
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: Linux SW RAID: HW Raid Controller/JBOD vs. Multiple PCI-e Cards?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Linux SW RAID: HW Raid Controller/JBOD vs. Multiple PCI-e Cards?
  • From: Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>
• Re: Linux SW RAID: HW Raid Controller/JBOD vs. Multiple PCI-e Cards?
  • From: Chris Wedgwood <cw@xxxxxxxx>
• Re: Linux SW RAID: HW Raid Controller/JBOD vs. Multiple PCI-e Cards?
  • From: Patrik Jonsson <patrik@xxxxxxxxxxx>
• Re: Linux SW RAID: HW Raid Controller/JBOD vs. Multiple PCI-e Cards?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Linux SW RAID: HW Raid Controller/JBOD vs. Multiple PCI-e Cards?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RE: raid10 on centos 5
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• Re: raid10 on centos 5
  • From: Eli Stair <estair@xxxxxxx>
• Re: raid10 on centos 5
  • From: Ruslan Sivak <rsivak@xxxxxxxxxxxxx>
• Re: raid10 on centos 5
  • From: Ruslan Sivak <rsivak@xxxxxxxxxxxxx>
• RE: RAID6 question
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• RE: raid10 on centos 5
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• Re: raid10 on centos 5
  • From: Ruslan Sivak <rsivak@xxxxxxxxxxxxx>
• Re: raid10 on centos 5
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: raid10 on centos 5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: raid10 on centos 5
  • From: Ruslan Sivak <rsivak@xxxxxxxxxxxxx>
• Re: raid10 on centos 5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: raid10 on centos 5
  • From: Ruslan Sivak <rsivak@xxxxxxxxxxxxx>
• Re: raid10 on centos 5
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: raid10 on centos 5
  • From: Ruslan Sivak <rsivak@xxxxxxxxxxxxx>
• RE: raid10 on centos 5
  • From: <Patrick_Boyd@xxxxxxxx>
• raid10 on centos 5
  • From: Ruslan Sivak <rsivak@xxxxxxxxxxxxx>
• Re: Raid1 replaced with raid10?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Raid1 replaced with raid10?
  • From: Peter Rabbitson <rabbit@xxxxxxxxx>
• Re: [PATCH 00/16] raid acceleration and asynchronous offload api for 2.6.22
  • From: ilmari@xxxxxxxxxx (Dagfinn Ilmari Mannsåker)
• RE: [PATCH 00/16] raid acceleration and asynchronous offload api for 2.6.22
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• RE: [PATCH 00/16] raid acceleration and asynchronous offload api for 2.6.22
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RE: [PATCH 00/16] raid acceleration and asynchronous offload api for 2.6.22
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• RE: [PATCH 00/16] raid acceleration and asynchronous offload api for 2.6.22
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RE: [PATCH 00/16] raid acceleration and asynchronous offload api for 2.6.22
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• attempt to access beyond end of device on RAID0 with mdadm
  • From: Slawek <slawekn1@xxxxxxxxxx>
• Re: [PATCH 00/16] raid acceleration and asynchronous offload api for 2.6.22
  • From: Nick Piggin <nickpiggin@xxxxxxxxxxxx>
• [PATCH 16/16] iop3xx: Surface the iop3xx DMA and AAU units to the iop-adma driver
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 15/16] iop13xx: Surface the iop13xx adma units to the iop-adma driver
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 14/16] dmaengine: driver for the iop32x, iop33x, and iop13xx raid engines
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 13/16] md: remove raid5 compute_block and compute_parity5
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 12/16] md: move raid5 io requests to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 11/16] md: use async_tx and raid5_run_ops for raid5 expansion operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 10/16] md: satisfy raid5 read requests via raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 09/16] md: move raid5 parity checks to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 08/16] md: move raid5 compute block operations to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 07/16] md: move write operations to raid5_run_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 06/16] md: use raid5_run_ops for stripe cache operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 05/16] md: add raid5_run_ops and support routines
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 04/16] dmaengine: add the async_tx api
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 03/16] ARM: Add drivers/dma to arch/arm/Kconfig
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 02/16] dmaengine: move channel management to the client
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 01/16] dmaengine: add base support for the async_tx api
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 00/16] raid acceleration and asynchronous offload api for 2.6.22
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: RAID rebuild on Create
  • From: David Greaves <david@xxxxxxxxxxxx>
• RE: RAID rebuild on Create
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• RE: RAID rebuild on Create
  • From: <Patrick_Boyd@xxxxxxxx>
• Re: RAID rebuild on Create
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: RAID rebuild on Create
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• RAID rebuild on Create
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• [PATCH 16/36] Use menuconfig objects II - MD
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• RAID6 question
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• RE: XFS on x86_64 Linux Question
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• Re: XFS on x86_64 Linux Question
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: XFS on x86_64 Linux Question
  • From: "Raz Ben-Jehuda(caro)" <raziebe@xxxxxxxxx>
• Re: XFS on x86_64 Linux Question
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Multiple disk failure, but slot numbers are corrupt and preventing assembly.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: filesystem corruption with md raid6
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: filesystem corruption with md raid6
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Multiple disk failure, but slot numbers are corrupt and preventing assembly.
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• filesystem corruption with md raid6
  • From: Clem Pryke <pryke@xxxxxxxxxxxxxxxxxx>
• Re: Multiple disk failure, but slot numbers are corrupt and preventing assembly.
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Multiple disk failure, but slot numbers are corrupt and preventing assembly.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Multiple disk failure, but slot numbers are corrupt and preventing assembly.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Partitioned arrays initially missing from /proc/partitions
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Multiple disk failure, but slot numbers are corrupt and preventing assembly.
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Multiple disk failure, but slot numbers are corrupt and preventing assembly.
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• Re: Partitioned arrays initially missing from /proc/partitions
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Partitioned arrays initially missing from /proc/partitions
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Partitioned arrays initially missing from /proc/partitions
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Partitioned arrays initially missing from /proc/partitions
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Partitioned arrays initially missing from /proc/partitions
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Partitioned arrays initially missing from /proc/partitions
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Partitioned arrays initially missing from /proc/partitions
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Partitioned arrays initially missing from /proc/partitions
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Multiple disk failure, but slot numbers are corrupt and preventing assembly.
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Multiple disk failure, but slot numbers are corrupt and preventing assembly.
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• Re: Multiple disk failure, but slot numbers are corrupt and preventing assembly.
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• Re: mkinitrd and RAID6 on FC5
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• RE: mkinitrd and RAID6 on FC5
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• Re: Partitioned arrays initially missing from /proc/partitions
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Partitioned arrays initially missing from /proc/partitions
  • From: Mike Accetta <maccetta@xxxxxxxxxxxxxxxxxx>
• Re: Multiple disk failure, but slot numbers are corrupt and preventing assembly.
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: mkinitrd and RAID6 on FC5
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Multiple disk failure, but slot numbers are corrupt and preventing assembly.
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• Re: Partitioned arrays initially missing from /proc/partitions
  • From: David Greaves <david@xxxxxxxxxxxx>
• mkinitrd and RAID6 on FC5
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• Re: major performance drop on raid5 due to context switches caused by small max_hw_sectors [partially resolved]
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: major performance drop on raid5 due to context switches caused by small max_hw_sectors [partially resolved]
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• Re: major performance drop on raid5 due to context switches caused by small max_hw_sectors [partially resolved]
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: major performance drop on raid5 due to context switches caused by small max_hw_sectors [partially resolved]
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: major performance drop on raid5 due to context switches caused by small max_hw_sectors [partially resolved]
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: major performance drop on raid5 due to context switches caused by small max_hw_sectors [partially resolved]
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: major performance drop on raid5 due to context switches caused by small max_hw_sectors [partially resolved]
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: major performance drop on raid5 due to context switches caused by small max_hw_sectors [partially resolved]
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: major performance drop on raid5 due to context switches caused by small max_hw_sectors [partially resolved]
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: major performance drop on raid5 due to context switches caused by small max_hw_sectors [partially resolved]
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: major performance drop on raid5 due to context switches caused by small max_hw_sectors [partially resolved]
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: major performance drop on raid5 due to context switches caused by small max_hw_sectors [partially resolved]
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Re: major performance drop on raid5 due to context switches caused by small max_hw_sectors [partially resolved]
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: major performance drop on raid5 due to context switches caused by small max_hw_sectors [partially resolved]
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• major performance drop on raid5 due to context switches caused by small max_hw_sectors
  • From: Pallai Roland <dap@xxxxxxxxxxxxx>
• Raid-1 on top of multipath
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: FW: [slightly OT] expanding lvm volume group after growing raid5 array
  • From: Gavin McCullagh <gmccullagh@xxxxxxxxx>
• FW: [slightly OT] expanding lvm volume group after growing raid5 array
  • From: "Daniel Korstad" <dan@xxxxxxxxxxx>
• [slightly OT] expanding lvm volume group after growing raid5 array
  • From: Gavin McCullagh <gmccullagh@xxxxxxxxx>
• Re: raid5 write performance
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5 write performance
  • From: "Raz Ben-Jehuda(caro)" <raziebe@xxxxxxxxx>
• Re: Bug#415441: s2disk and raid
  • From: Tim Dijkstra <newsuser@xxxxxxxxxxxxxxx>
• Raid5 performance question
  • From: mickg <mickg@xxxxxxxxx>
• Re: Recovering a raid5 array with strange event count
  • From: Chris Allen <chris@xxxxxxx>
• Re: Manually hacking superblocks
  • From: Lasse Kärkkäinen <tronic+owm8@xxxxxxxxxx>
• Re: Moron Destroyed RAID6 Array Superblocks
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: Moron Destroyed RAID6 Array Superblocks
  • From: "Aaron C. de Bruyn" <aaron@xxxxxxxxxxxxx>
• Re: Moron Destroyed RAID6 Array Superblocks
  • From: "Aaron C. de Bruyn" <aaron@xxxxxxxxxxxxx>
• Re: RAID5 superblocks partly messed up after degradation
  • From: Frank Baumgart <frank.baumgart@xxxxxxx>
• Re: md0: invalid bitmap page request: 249 (> 223)
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Recovering a raid5 array with strange event count
  • From: Chris Allen <chris@xxxxxxx>
• Re: md0: invalid bitmap page request: 249 (> 223)
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Same UUID for every member of all array ?
  • From: Brice Figureau <brice+lklm@xxxxxxxxxxxxxxxx>
• Re: Manually hacking superblocks
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Recovering a raid5 array with strange event count
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Manually hacking superblocks
  • From: David Greaves <david@xxxxxxxxxxxx>
• Recovering a raid5 array with strange event count
  • From: Chris Allen <chris@xxxxxxx>
• Manually hacking superblocks
  • From: Lasse Kärkkäinen <tronic+owm8@xxxxxxxxxx>
• Re: Growing a raid 6 array
  • From: Louis-David Mitterrand <vindex+lists-linux-raid@xxxxxxxxxxx>
• Re: Growing a raid 6 array
  • From: Laurent CARON <lcaron@xxxxxxxxxxxxxxxxx>
• Re: Same UUID for every member of all array ?
  • From: Iustin Pop <iusty@xxxxxxxxx>
• Re: raid10 kernel panic on sparc64
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: raid10 kernel panic on sparc64
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: md0: invalid bitmap page request: 249 (> 223)
  • From: Bill Davidsen <davidsen@xxxxxxx>
• md0: invalid bitmap page request: 249 (> 223)
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: LINEAR RAID, little help
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Same UUID for every member of all array ?
  • From: Brice Figureau <brice+lklm@xxxxxxxxxxxxxxxx>
• Re: LINEAR RAID, little help
  • From: "matt s." <cache22@xxxxxxxxxxxxx>
• Re: LINEAR RAID, little help
  • From: Neil Brown <neilb@xxxxxxx>
• Re: LINEAR RAID, little help
  • From: Rich <rich@xxxxxxxxxxxxxx>
• Re: s2disk and raid
  • From: Luis Rodrigo Gallardo Cruz <rodrigo@xxxxxxxxxxx>
• RE: [PATCH RFC 3/4] md: writeback caching policy for raid5 [experimental]
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH RFC 3/4] md: writeback caching policy for raid5 [experimental]
  • From: Al Boldi <a1426z@xxxxxxxxx>
• RE: [PATCH RFC 3/4] md: writeback caching policy for raid5 [experimental]
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH RFC 3/4] md: writeback caching policy for raid5 [experimental]
  • From: Mark Hahn <hahn@xxxxxxxxxxx>
• [patch 11/31] Fix calculation for size of filemap_attr array in md/bitmap.
  • From: Greg KH <gregkh@xxxxxxx>
• [PATCH RFC 4/4] md: delayed stripe activation
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH RFC 2/4] md: refactor raid5 cache policy code using 'struct stripe_cache_policy'
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH RFC 1/4] md: introduce struct stripe_head_state
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH RFC 3/4] md: writeback caching policy for raid5 [experimental]
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH RFC 0/4] raid5: write-back caching policy and write performance
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: RAID1 "out of memory" error, was Re: 2.6.21-rc5-mm4
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid6 rebuild
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID5 superblocks partly messed up after degradation
  • From: Neil Brown <neilb@xxxxxxx>
• Re: LINEAR RAID, little help
  • From: Neil Brown <neilb@xxxxxxx>
• Re: LINEAR RAID, little help
  • From: Henrik Holst <holst@xxxxxxxxxxx>
• [PATCH 14/30] Use menuconfig objects - MD
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• RAID5 superblocks partly messed up after degradation
  • From: Frank Baumgart <frank.baumgart@xxxxxxx>
• Re: raid1 does not seem faster
  • From: Iustin Pop <iusty@xxxxxxxxx>
• Re: raid1 does not seem faster
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Kernel 2.6.20.4: Software RAID 5: ata13.00: (irq_stat 0x00020002, failed to transmit command FIS)
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: Moron Destroyed RAID6 Array Superblocks
  • From: Andrew Burgess <aab@xxxxxxxxxxx>
• Moron Destroyed RAID6 Array Superblocks
  • From: "Aaron C. de Bruyn" <aaron@xxxxxxxxxxxxx>
• Re: LINEAR RAID, little help
  • From: Gavin McCullagh <gmccullagh@xxxxxxxxx>
• Re: LINEAR RAID, little help
  • From: Rich <rich@xxxxxxxxxxxxxx>
• Re: LINEAR RAID, little help
  • From: Gavin McCullagh <gmccullagh@xxxxxxxxx>
• LINEAR RAID, little help
  • From: Rich <rich@xxxxxxxxxxxxxx>
• Re: raid10_make_request bug: can't convert block across chunks or bigger [...]
  • From: Andy Smith <andy@xxxxxxxxxx>
• raid10_make_request bug: can't convert block across chunks or bigger [...]
  • From: Andy Smith <andy@xxxxxxxxxx>
• Re: s2disk and raid
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: RAID1 "out of memory" error, was Re: 2.6.21-rc5-mm4
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: Any Intel folks on the list? Intel PCI-E bridge ACPI resource question
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: RAID1 "out of memory" error, was Re: 2.6.21-rc5-mm4
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: raid1 does not seem faster
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Kernel 2.6.20.4: Software RAID 5: ata13.00: (irq_stat 0x00020002, failed to transmit command FIS)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: raid6 rebuild
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• RAID1 "out of memory" error, was Re: 2.6.21-rc5-mm4
  • From: Reuben Farrelly <reuben-linuxkernel@xxxxxxxx>
• Kernel 2.6.20.4: Software RAID 5: ata13.00: (irq_stat 0x00020002, failed to transmit command FIS)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: raid1 does not seem faster
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: raid1 does not seem faster
  • From: Iustin Pop <iusty@xxxxxxxxx>
• Re: raid1 does not seem faster
  • From: Iustin Pop <iusty@xxxxxxxxx>
• Re: raid6 rebuild
  • From: Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx>
• Re: raid6 rebuild
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid1 does not seem faster
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid6 rebuild
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: raid6 rebuild
  • From: Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx>
• Re: raid6 rebuild
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: raid1 does not seem faster
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: raid6 rebuild
  • From: Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx>
• Re: raid6 rebuild
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: raid6 rebuild
  • From: Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx>
• Re: raid1 does not seem faster
  • From: Iustin Pop <iusty@xxxxxxxxx>
• Re: 2.6.20.3 AMD64 oops in CFQ code
  • From: Tejun Heo <teheo@xxxxxxx>
• Re: 2.6.20.3 AMD64 oops in CFQ code
  • From: "Lee Revell" <rlrevell@xxxxxxxxxxx>
• Re: raidtools to mdadm
  • From: Casey Boone <caseyboone@xxxxxxxxx>
• Re: raid6 rebuild
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: 2.6.20.3 AMD64 oops in CFQ code
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid1 does not seem faster
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raidtools to mdadm
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: mismatch_cnt worries
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: s2disk and raid
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• raid6 rebuild
  • From: Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx>
• Re: s2disk and raid
  • From: Tim Dijkstra <newsuser@xxxxxxxxxxxxxxx>
• Re: parity check for read?
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: parity check for read?
  • From: Ric Wheeler <ric@xxxxxxx>
• Re: md126-7
  • From: Just Marc <marc@xxxxxxxxx>
• Re: parity check for read?
  • From: Mirko Benz <mirko.benz@xxxxxx>
• Re: s2disk and raid
  • From: Neil Brown <neilb@xxxxxxx>
• Re: md126-7
  • From: Neil Brown <neilb@xxxxxxx>
• Re: parity check for read?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [Suspend-devel] s2disk and raid
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• Re: [Suspend-devel] s2disk and raid
  • From: Stefan Seyfried <seife@xxxxxxx>
• md126-7
  • From: Just Marc <marc@xxxxxxxxx>
• s2disk and raid
  • From: Tim Dijkstra <newsuser@xxxxxxxxxxxxxxx>
• parity check for read?
  • From: Mirko Benz <mirko.benz@xxxxxx>
• Re: raid1 does not seem faster
  • From: Al Boldi <a1426z@xxxxxxxxx>
• Re: 2.6.20.3 AMD64 oops in CFQ code
  • From: Tejun Heo <teheo@xxxxxxx>
• Re: 2.6.20.3 AMD64 oops in CFQ code
  • From: linux@xxxxxxxxxxx
• Re: mismatch_cnt worries
  • From: Gavin McCullagh <gmccullagh@xxxxxxxxx>
• Re: 2.6.20.3 AMD64 oops in CFQ code
  • From: Tejun Heo <teheo@xxxxxxx>
• bio too big device md1 (16 > 8)
  • From: syrius.ml@xxxxxxxxxx
• Re: mismatch_cnt worries
  • From: Neil Brown <neilb@xxxxxxx>
• Question about using dmraid45 patch
  • From: "Wood, Brian J" <brian.j.wood@xxxxxxxxx>
• mismatch_cnt worries
  • From: Gavin McCullagh <gmccullagh@xxxxxxxxx>
• Re: raid5 write performance
  • From: "Raz Ben-Jehuda(caro)" <raziebe@xxxxxxxxx>
• Re: [PATCH] md: Avoid a deadlock when removing a device from an md array via sysfs.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md: Avoid a deadlock when removing a device from an md array via sysfs.
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• [PATCH] md: Avoid a deadlock when removing a device from an md array via sysfs.
  • From: NeilBrown <neilb@xxxxxxx>
• Desperate plea for help
  • From: Nevyn <nevynh@xxxxxxxxx>
• Re: raid10 kernel panic on sparc64
  • From: David Miller <davem@xxxxxxxxxxxxx>
• raid10 kernel panic on sparc64
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: raidtools to mdadm
  • From: Neil Brown <neilb@xxxxxxx>
• raidtools to mdadm
  • From: Casey Boone <caseyboone@xxxxxxxxx>
• Re: raid5 write performance
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: raid1 does not seem faster
  • From: Henrik Holst <holst@xxxxxxxxxxx>
• Re: raid1 does not seem faster
  • From: Al Boldi <a1426z@xxxxxxxxx>
• raid1 does not seem faster
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: raid5 write performance
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid5 write performance
  • From: "Raz Ben-Jehuda(caro)" <raziebe@xxxxxxxxx>
• Re: raid5 write performance
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid6 array , part id 'fd' not assembling at boot .
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: is this raid5 OK ?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: is this raid5 OK ?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid5 write performance
  • From: "Raz Ben-Jehuda(caro)" <raziebe@xxxxxxxxx>
• Re: is this raid5 OK ?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: is this raid5 OK ?
  • From: Rainer Fuegenstein <rfu@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: mdadm: RUN_ARRAY failed: Cannot allocate memory
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: is this raid5 OK ?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: is this raid5 OK ?
  • From: Rainer Fuegenstein <rfu@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Software RAID (non-preempt) server blocking question. (2.6.20.4)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: is this raid5 OK ?
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: Software RAID (non-preempt) server blocking question. (2.6.20.4)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: is this raid5 OK ?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: is this raid5 OK ?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• is this raid5 OK ?
  • From: Rainer Fuegenstein <rfu@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: split raid1 into to arrays
  • From: "Dirk Jagdmann" <jagdmann@xxxxxxxxx>
• Re: Software RAID (non-preempt) server blocking question. (2.6.20.4)
  • From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
• Re: Software RAID (non-preempt) server blocking question. (2.6.20.4)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Software RAID (non-preempt) server blocking question. (2.6.20.4)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: mdadm: RUN_ARRAY failed: Cannot allocate memory
  • From: Neil Brown <neilb@xxxxxxx>
• Re: LILO 22.6.1-9.3 not compatible with SW RAID1 metdata >= 1.0
  • From: Neil Brown <neilb@xxxxxxx>
• Re: md bitmaps on 2.6.16.y
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Software RAID (non-preempt) server blocking question. (2.6.20.4)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: split raid1 into to arrays
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Software RAID (non-preempt) server blocking question. (2.6.20.4)
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• split raid1 into to arrays
  • From: "Dirk Jagdmann" <jagdmann@xxxxxxxxx>
• md bitmaps on 2.6.16.y
  • From: "Ed L. Cashin" <ecashin@xxxxxxxxxx>
• Re: [PATCH 2.6.21-rc4 01/15] dmaengine: add base support for the async_tx api
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• LILO 22.6.1-9.3 not compatible with SW RAID1 metdata >= 1.0
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: addingdrive to raid 1
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Swap initialised as an md?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: XFS sunit/swidth for raid10
  • From: dean gaudet <dean@xxxxxxxxxx>
• addingdrive to raid 1
  • From: Robert Stanford <rob@xxxxxxxxxxxxxxx>