Linux RAID Storage Date Index

• Thread Index

• RE: Raid1 uses partially reconstructed drive
  • From: "Danny Sung" <dsung@xxxxxxxxxxxxx>
• raidreconf for 5 x 320GB -> 8 x 320GB
  • From: "Timo Bernack" <timo.bernack@xxxxxxxxxx>
• Re: RAID5/10 chunk size and ext2/3 stride parameter
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Problem with RAID-1, inconsistent data returned if disks get out of sync
  • From: "Roger Lucas" <roger@xxxxxxxxxxxxx>
• Re: bio too big device dm-XX (256 > 255) on 2.6.17
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Raid1 uses partially reconstructed drive
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Problem booting linux 2.6.19-rc5, 2.6.19-rc5-git6, 2.6.19-rc5-mm2 with md raid 1 over lvm root
  • From: "Nicolas Mailhot" <nicolas.mailhot@xxxxxxxxxxx>
• Re: mdadm-2.5.4 issues and 2.6.18.1 kernel md issues
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Recovering from default FC6 install
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Problem booting linux 2.6.19-rc5, 2.6.19-rc5-git6, 2.6.19-rc5-mm2 with md raid 1 over lvm root
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Raid1 uses partially reconstructed drive
  • From: "Danny Sung" <dsung@xxxxxxxxxxxxx>
• Re: safest way to swap in a new physical disk
  • From: Forrest Taylor <ftaylor@xxxxxxxxxx>
• Problem booting linux 2.6.19-rc5, 2.6.19-rc5-git6, 2.6.19-rc5-mm2 with md raid 1 over lvm root
  • From: "Nicolas Mailhot" <nicolas.mailhot@xxxxxxxxxxx>
• Re: How mdadm can support > 2T
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5 hang on get_active_stripe
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: why not make everything partitionable?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: safest way to swap in a new physical disk
  • From: Forrest Taylor <ftaylor@xxxxxxxxxx>
• why not make everything partitionable?
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Raid 1 (non) performance
  • From: "Magnus Naeslund(k)" <mag@xxxxxxx>
• Re: How mdadm can support > 2T
  • From: Chris Allen <chris@xxxxxxx>
• How mdadm can support > 2T
  • From: "俞先印" <yu_xianyin@xxxxxxxxxxxxx>
• Re: Recovering from default FC6 install
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re[4]: RAID1 submirror failure causes reboot?
  • From: Jim Klimov <klimov@xxxxxxxxxxx>
• Re: raid5 hang on get_active_stripe
  • From: Chris Allen <chris@xxxxxxx>
• Re: Raid 1 up after raidhotadd without rebuild
  • From: Elmar Weber <lists@xxxxxxxxxxxxxx>
• Re: Raid 1 up after raidhotadd without rebuild
  • From: Neil Brown <neilb@xxxxxxx>
• Raid 1 up after raidhotadd without rebuild
  • From: Elmar Weber <lists@xxxxxxxxxxxxxx>
• safest way to swap in a new physical disk
  • From: Will Sheffler <willsheffler@xxxxxxxxx>
• Re: Re[2]: RAID1 submirror failure causes reboot?
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: bio too big device dm-XX (256 > 255) on 2.6.17
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH 004 of 4] md: Fix a couple more bugs in raid5/6 aligned reads
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 4] md: Fix newly introduced read-corruption with raid6.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 003 of 4] md: Misc fixes for aligned-read handling.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 4] md: Fix innocuous bug in raid6 stripe_to_pdidx
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 4] md: Various fixes for new cache-bypassing-reads in raid5/6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: bio too big device dm-XX (256 > 255) on 2.6.17
  • From: Jure Pečar <pegasus@xxxxxxxxxxx>
• Re: Re[2]: RAID1 submirror failure causes reboot?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Re[2]: RAID1 submirror failure causes reboot?
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: Checksums wrong on one disk of mirror
  • From: Henrik Holst <henrik.holst@xxxxxxxxxx>
• Re: Re[2]: RAID1 submirror failure causes reboot?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Recovering from default FC6 install
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Swap initialised as an md?
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Write cache / barrier
  • From: John K Luebs <jkluebs@xxxxxxxxxxxxxx>
• Recovering from default FC6 install
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re[2]: RAID1 submirror failure causes reboot?
  • From: Jim Klimov <klimov@xxxxxxxxxxx>
• Re: Swap initialised as an md?
  • From: Mogens Kjaer <mk@xxxxxx>
• Swap initialised as an md?
  • From: David <lists@xxxxxxxxx>
• Re: RAID1 submirror failure causes reboot?
  • From: Neil Brown <neilb@xxxxxxx>
• RAID1 submirror failure causes reboot?
  • From: Jim Klimov <klimov@xxxxxxxxxxx>
• Re: How to recover from massive disk failure
  • From: Neil Brown <neilb@xxxxxxx>
• Re: How to recover from massive disk failure
  • From: Jacob Schmidt Madsen <jacob@xxxxxxxx>
• Re: How to recover from massive disk failure
  • From: Neil Brown <neilb@xxxxxxx>
• How to recover from massive disk failure
  • From: Jacob Schmidt Madsen <jacob@xxxxxxxx>
• Re: New features?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm-2.5.4 issues and 2.6.18.1 kernel md issues
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Too much ECC?
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• md manpage of mdadm 2.5.6
  • From: Joachim Wagner <jwagner@xxxxxxxxxxxxxxxx>
• Re: [solved] (was: supermicro ejecting disks)
  • From: Louis-David Mitterrand <vindex+lists-linux-raid@xxxxxxxxxxx>
• Too much ECC?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• [consultant needed] (was: supermicro ejecting disks)
  • From: Louis-David Mitterrand <vindex+lists-linux-raid@xxxxxxxxxxx>
• [urgent] supermicro ejecting disks
  • From: Louis-David Mitterrand <vindex+lists-linux-raid@xxxxxxxxxxx>
• Randomly kernel panic with MPT SPI driver 3.04.01
  • From: "Rémi VM" <eremid@xxxxxxxxx>
• safely removing RAID information?
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 001 of 6] md: Send online/offline uevents when an md array starts/stops.
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: [PATCH 001 of 6] md: Send online/offline uevents when an md array starts/stops.
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: mdadm-2.5.4 issues and 2.6.18.1 kernel md issues
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 001 of 6] md: Send online/offline uevents when an md array starts/stops.
  • From: Neil Brown <neilb@xxxxxxx>
• bio too big device dm-XX (256 > 255) on 2.6.17
  • From: Jure Pečar <pegasus@xxxxxxxxxxx>
• Re: RAID5 array showing as degraded after motherboard replacement
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: Is my RAID broken?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID5 array showing as degraded after motherboard replacement
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: new array not starting
  • From: Bill Davidsen <davidsen@xxxxxxx>
• FYI: [2.6.16 patch] drivers/md/md.c: update START_ARRAY printk
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: [PATCH 001 of 6] md: Send online/offline uevents when an md array starts/stops.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: Checksums wrong on one disk of mirror
  • From: David <lists@xxxxxxxxx>
• Re: new array not starting
  • From: Robin Bowes <robin-lists@xxxxxxxxxxxxxx>
• Re: FYI: [2.6.16 patch] drivers/md/md.c: update START_ARRAY printk
  • From: Neil Brown <neilb@xxxxxxx>
• Re: new array not starting
  • From: Robin Bowes <robin-lists@xxxxxxxxxxxxxx>
• Re: new array not starting
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: new array not starting
  • From: Robin Bowes <robin-lists@xxxxxxxxxxxxxx>
• Re: new array not starting
  • From: Robin Bowes <robin-lists@xxxxxxxxxxxxxx>
• new array not starting
  • From: Robin Bowes <robin-lists@xxxxxxxxxxxxxx>
• Re: RAID5 array showing as degraded after motherboard replacement
  • From: "James Lee" <james.lee@xxxxxxxxxx>
• [PATCH 006 of 9] md: Define raid5_mergeable_bvec
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 007 of 9] md: Handle bypassing the read cache (assuming nothing fails).
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 9] md: Change ONLINE/OFFLINE events to a single CHANGE event
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 9] md: Tidy up device-change notification when an md array is stopped
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 003 of 9] md: Do not freeze md threads for suspend.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 009 of 9] md: Enable bypassing cache for reads.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 008 of 9] md: Allow reads that have bypassed the cache to be retried on failure.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 005 of 9] md: Change lifetime rules for 'md' devices.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 9] md: Fix sizing problem with raid5-reshape and CONFIG_LBD=n
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 9] md: udev notification, raid5 read improvements etc
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Checksums wrong on one disk of mirror
  • From: David <lists@xxxxxxxxx>
• Re: Checksums wrong on one disk of mirror
  • From: Neil Brown <neilb@xxxxxxx>
• Checksums wrong on one disk of mirror
  • From: David <lists@xxxxxxxxx>
• Re: [PATCH 001 of 6] md: Send online/offline uevents when an md array starts/stops.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: invalid (zero) superblock magic upon creation of a new RAID-1 array
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5 reshape bug with XFS
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID5 array showing as degraded after motherboard replacement
  • From: "James Lee" <james.lee@xxxxxxxxxx>
• Re: invalid (zero) superblock magic upon creation of a new RAID-1 array
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [RFC][PATCH -mm][Experimental] suspend: Do not freeze md_threads
  • From: Pavel Machek <pavel@xxxxxx>
• Re: Is my RAID broken?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [PATCH 001 of 6] md: Send online/offline uevents when an md array starts/stops.
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: RAID5 array showing as degraded after motherboard replacement
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: mdadm 2.5.5 external bitmap assemble problem
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: Is my RAID broken?
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: Is my RAID broken?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: invalid (zero) superblock magic upon creation of a new RAID-1 array
  • From: Thomas Andrews <tandrews@xxxxxxxxxx>
• Re: raid5 reshape bug with XFS
  • From: Bill Cizek <cizek@xxxxxxx>
• Re: Checking individual drive state
  • From: Mike Hardy <mhardy@xxxxxxx>
• Re: [PATCH 001 of 6] md: Send online/offline uevents when an md array starts/stops.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID5 array showing as degraded after motherboard replacement
  • From: "James Lee" <james.lee@xxxxxxxxxx>
• Re: raid5 reshape bug with XFS
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm 2.5.5 external bitmap assemble problem
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [RFC][PATCH -mm][Experimental] suspend: Do not freeze md_threads
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Is my RAID broken?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: invalid (zero) superblock magic upon creation of a new RAID-1 array
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID5 array showing as degraded after motherboard replacement
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: Checking individual drive state
  • From: dean gaudet <dean@xxxxxxxxxx>
• RAID5 array showing as degraded after motherboard replacement
  • From: "James Lee" <james.lee@xxxxxxxxxx>
• Checking individual drive state
  • From: Bradshaw <breadlord@xxxxxxxxx>
• Re: [RFC][PATCH -mm][Experimental] suspend: Do not freeze md_threads
  • From: Pavel Machek <pavel@xxxxxx>
• invalid (zero) superblock magic upon creation of a new RAID-1 array
  • From: Thomas Andrews <tandrews@xxxxxxxxxx>
• Is my RAID broken?
  • From: "Robert Hulme" <rob@xxxxxxxxxxxx>
• Re: RAID5/10 chunk size and ext2/3 stride parameter
  • From: dean gaudet <dean@xxxxxxxxxx>
• mdadm 2.5.5 external bitmap assemble problem
  • From: dean gaudet <dean@xxxxxxxxxx>
• raid5 reshape bug with XFS
  • From: Bill Cizek <cizek@xxxxxxx>
• Re: accessing windows raid with mdadm?
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: RAID5/10 chunk size and ext2/3 stride parameter
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Re: RAID5/10 chunk size and ext2/3 stride parameter
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: RAID5 refuses to accept replacement drive.
  • From: greg@xxxxxxxxxxxx
• Re: New features?
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: [PATCH 001 of 6] md: Send online/offline uevents when an md array starts/stops.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH 001 of 6] md: Send online/offline uevents when an md array starts/stops.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: New features?
  • From: Neil Brown <neilb@xxxxxxx>
• [RFC][PATCH -mm][Experimental] suspend: Do not freeze md_threads
  • From: "Rafael J. Wysocki" <rjw@xxxxxxx>
• mdadm-2.5.4 issues and 2.6.18.1 kernel md issues
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: [PATCH 001 of 6] md: Send online/offline uevents when an md array starts/stops.
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [PATCH 001 of 6] md: Send online/offline uevents when an md array starts/stops.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 001 of 6] md: Send online/offline uevents when an md array starts/stops.
  • From: "Kay Sievers" <kay.sievers@xxxxxxxx>
• accessing windows raid with mdadm?
  • From: Shaya Potter <spotter@xxxxxxxx>
• Re: md array numbering is messed up
  • From: Peb <peb-misc@xxxxxxxxxx>
• [PATCH 28/61] md: Fix bug where spares dont always get rebuilt properly when they become live.
  • From: Chris Wright <chrisw@xxxxxxxxxxxx>
• [PATCH 29/61] md: Fix calculation of ->degraded for multipath and raid10
  • From: Chris Wright <chrisw@xxxxxxxxxxxx>
• New features?
  • From: Frido Ferdinand <frido@xxxxxxxxxx>
• Re: New features?
  • From: Frido Ferdinand <frido@xxxxxxxxxx>
• Re: [PATCH 001 of 6] md: Send online/offline uevents when an md array starts/stops.
  • From: Greg KH <gregkh@xxxxxxx>
• Re: [PATCH 000 of 6] md: udev events and cache bypass for reads
  • From: Greg KH <gregkh@xxxxxxx>
• Re: RAID5 refuses to accept replacement drive.
  • From: greg@xxxxxxxxxxxx
• Re: New features?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: New features?
  • From: Mike Hardy <mhardy@xxxxxxx>
• Re: future hardware
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: New features?
  • From: John Rowe <rowe@xxxxxxxxxxxxx>
• Re: New features?
  • From: Neil Brown <neilb@xxxxxxx>
• New features?
  • From: John Rowe <rowe@xxxxxxxxxxxxx>
• Re: [stable] [PATCH] Check bio address after mapping through partitions.
  • From: Chris Wright <chrisw@xxxxxxxxxxxx>
• Re: [PATCH 002 of 6] md: Change lifetime rules for 'md' devices.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [PATCH 002 of 6] md: Change lifetime rules for 'md' devices.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 002 of 6] md: Change lifetime rules for 'md' devices.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• Re: [PATCH 002 of 6] md: Change lifetime rules for 'md' devices.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 002 of 6] md: Change lifetime rules for 'md' devices.
  • From: Andrew Morton <akpm@xxxxxxxx>
• Re: [PATCH] Check bio address after mapping through partitions.
  • From: Jens Axboe <jens.axboe@xxxxxxxxxx>
• [PATCH 004 of 6] md: Handle bypassing the read cache (assuming nothing fails).
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 006 of 6] md: Enable bypassing cache for reads.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 005 of 6] md: Allow reads that have bypassed the cache to be retried on failure.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 003 of 6] md: Define raid5_mergeable_bvec
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 6] md: Change lifetime rules for 'md' devices.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 6] md: Send online/offline uevents when an md array starts/stops.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 6] md: udev events and cache bypass for reads
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md array numbering is messed up
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH] Check bio address after mapping through partitions.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Kernel OOPS with partitioned software raid (+ further questions)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: md array numbering is messed up
  • From: Peb <peb-misc@xxxxxxxxxx>
• Re: new features time-line
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Propose of enhancement of raid1 driver
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Kernel OOPS with partitioned software raid (+ further questions) [PATCH]
  • From: "Christian P. Schmidt" <schmidt@xxxxxxxxx>
• Re: Propose of enhancement of raid1 driver
  • From: "Jeff Breidenbach" <breidenbach@xxxxxxxxx>
• Re: Propose of enhancement of raid1 driver
  • From: Al Boldi <a1426z@xxxxxxxxx>
• Re: Propose of enhancement of raid1 driver
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Propose of enhancement of raid1 driver
  • From: Al Boldi <a1426z@xxxxxxxxx>
• Re: md array numbering is messed up
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: Raid 0 breakage (maybe)
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: md array numbering is messed up
  • From: Brad Campbell <brad@xxxxxxxxxxx>
• Re: md array numbering is messed up
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Raid 0 breakage (maybe)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Raid 0 breakage (maybe)
  • From: Matt Thrailkill <matt@xxxxxxxxxxxxxx>
• Re: future hardware
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Raid 0 breakage (maybe)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: md array numbering is messed up
  • From: Neil Brown <neilb@xxxxxxx>
• md array numbering is messed up
  • From: Peb <peb-misc@xxxxxxxxxx>
• Raid 0 breakage (maybe)
  • From: Matt Thrailkill <matt@xxxxxxxxxxxxxx>
• Re: PERC5 - MegaRaid-SAS problems..
  • From: Chris Allen <chris@xxxxxxx>
• Re: Propose of enhancement of raid1 driver
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Propose of enhancement of raid1 driver
  • From: Al Boldi <a1426z@xxxxxxxxx>
• faulty.c does not accurately simulate failures...
  • From: Roger Gammans <roger@xxxxxxxxxxxxxxxxxxxxxx>
• Re: future hardware
  • From: Daniel Korstad <dan@xxxxxxxxxxx>
• Re: future hardware
  • From: Daniel Korstad <dan@xxxxxxxxxxx>
• Re: Question of PCI bandwidth affect on SW RAID arrays.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: future hardware
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid5 bitmap performance
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• raid5 bitmap performance
  • From: Shane <shane@xxxxx>
• Question of PCI bandwidth affect on SW RAID arrays.
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: mdadm: bitmaps not supported by this kernel?
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: RAID5 refuses to accept replacement drive.
  • From: Neil Brown <neilb@xxxxxxx>
• mdadm: bitmaps not supported by this kernel?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: RAID5 refuses to accept replacement drive.
  • From: Eli Stair <estair@xxxxxxx>
• RAID5 refuses to accept replacement drive.
  • From: greg@xxxxxxxxxxxx
• Re: Bug with RAID1 hot spares?
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Bug with RAID1 hot spares?
  • From: Chase Venters <chase.venters@xxxxxxxxxxxx>
• Re: Bug with RAID1 hot spares?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: why partition arrays?
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: why partition arrays?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• RAID5/10 chunk size and ext2/3 stride parameter
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Re: Raid5 or 6 here... ?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Raid5 or 6 here... ?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Raid5 or 6 here... ?
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: resync starts over after each reboot (2.6.18.1)?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: resync starts over after each reboot (2.6.18.1)?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Raid5 or 6 here... ?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Need help recovering a raid5 array
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Need help recovering a raid5 array
  • From: eharney@xxxxxxxxxxx
• Re: resync starts over after each reboot (2.6.18.1)?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: why partition arrays?
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• LEDs for array?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: Propose of enhancement of raid1 driver
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Need help recovering a raid5 array
  • From: eharney@xxxxxxxxxxx
• [PATCH 004 of 4] md: Fix printk format warnings, seen on powerpc64:
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 003 of 4] md: Fix up maintenance of ->degraded in multipath.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 4] md: Fix bug where spares don't always get rebuilt properly when they become live.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 4] md: Simplify checking of available size when resizing an array
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 4] md: assorted bugfixes - one serious.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: resync starts over after each reboot (2.6.18.1)?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Restoring a RAID 5
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Problem with Software RAID5
  • From: Neil Brown <neilb@xxxxxxx>
• Re: patches
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid 5 read performance
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Bug with RAID1 hot spares?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID5 Recovery
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID5 Recovery
  • From: Neil Cavan <nrcavan@xxxxxxxxxxxxxxxxxxxx>
• Re: Propose of enhancement of raid1 driver
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID5 Recovery
  • From: Neil Brown <neilb@xxxxxxx>
• Re: why partition arrays?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: future hardware
  • From: Mike Hardy <mhardy@xxxxxxx>
• Re: future hardware
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• RAID5 Recovery
  • From: Neil Cavan <nrcavan@xxxxxxxxxxxxxxxxxxxx>
• Re: why partition arrays?
  • From: Bodo Thiesen <bothie@xxxxxx>
• Re: future hardware
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Propose of enhancement of raid1 driver
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: why partition arrays?
  • From: Henrik Holst <henrik.holst@xxxxxxxxxx>
• future hardware
  • From: "Dan" <dan@xxxxxxxxxxx>
• Re: why partition arrays?
  • From: Bodo Thiesen <bothie@xxxxxx>
• Bug with RAID1 hot spares?
  • From: Chase Venters <chase.venters@xxxxxxxxxxxx>
• Re: raid 5 read performance
  • From: Stephan van Hienen <raid@xxxxxxxx>
• patches
  • From: "Michael Labuschke" <michael@xxxxxxxxxxxx>
• Re: Propose of enhancement of raid1 driver
  • From: "Jeff Breidenbach" <breidenbach@xxxxxxxxx>
• Re: [PATCH] md: Fix bug where new drives added to an md array sometimes don't sync properly.
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH 003 of 4] md: Endian annotation for v1 superblock access.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 4] md: Add another COMPAT_IOCTL for md.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 4] md: Endian annotations for the bitmap superblock
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 4] md: Fix calculation of ->degraded for multipath and raid10
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 4] md: Introduction - bugfix patches for md.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Propose of enhancement of raid1 driver
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: BUGS: internal bitmap during array create
  • From: Eli Stair <estair@xxxxxxx>
• Re: BUGS: internal bitmap during array create
  • From: Neil Brown <neilb@xxxxxxx>
• RE: why partition arrays?
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• RE: why partition arrays?
  • From: Ken Walker <ken.walker@xxxxxxxxxxxxxxxx>
• Re: BUGS: internal bitmap during array create
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Propose of enhancement of raid1 driver
  • From: Neil Brown <neilb@xxxxxxx>
• Re: new features time-line
  • From: Neil Brown <neilb@xxxxxxx>
• Re: BUGS: internal bitmap during array create
  • From: Eli Stair <estair@xxxxxxx>
• Re: [PATCH] md: Fix bug where new drives added to an md array sometimes don't sync properly.
  • From: Eli Stair <estair@xxxxxxx>
• Re: why partition arrays?
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: why partition arrays?
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Re: why partition arrays?
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• why partition arrays?
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Problem with Software RAID5
  • From: Lars Schimmer <l.schimmer@xxxxxxxxxxxxx>
• Re: Doubts about array size
  • From: Bruno Costacurta <pubmb02@xxxxxxxxx>
• Re: new features time-line
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Restoring a RAID 5
  • From: Hal Vaughan <hal@xxxxxxxxxxxxxxxxxxxx>
• Re: Doubts about array size
  • From: Forrest Taylor <ftaylor@xxxxxxxxxx>
• Re: PERC5 - MegaRaid-SAS problems..
  • From: "Andrew Moise" <chops@xxxxxxxxxxxxxxxxxxx>
• Re: Needing help with Raid 5 array with 2 failed disks of 4 [Solved]
  • From: Bobby S <at7max@xxxxxxxxxxx>
• Re: PERC5 - MegaRaid-SAS problems..
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: PERC5 - MegaRaid-SAS problems..
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Doubts about array size
  • From: Bruno Costacurta <pubmb02@xxxxxxxxx>
• Re: PERC5 - MegaRaid-SAS problems..
  • From: Greg Dickie <greg@xxxxxxxxx>
• Re: PERC5 - MegaRaid-SAS problems..
  • From: "Andrew Moise" <chops@xxxxxxxxxxxxxxxxxxx>
• mptsas driver
  • From: Clem Pryke <pryke@xxxxxxxxxxxxxxxxxx>
• Needing help with Raid 5 array with 2 failed disks of 4
  • From: Bobby S <at7max@xxxxxxxxxxx>
• Compile problem
  • From: Olivier Doremieux <olivier@xxxxxxxxxxxxx>
• RE: PERC5 - MegaRaid-SAS problems..
  • From: <Patrick_Boyd@xxxxxxxx>
• Re: PERC5 - MegaRaid-SAS problems..
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: resync starts over after each reboot (2.6.18.1)?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: resync starts over after each reboot (2.6.18.1)?
  • From: Neil Brown <neilb@xxxxxxx>
• resync starts over after each reboot (2.6.18.1)?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: libata hotplug and md raid?
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Propose of enhancement of raid1 driver
  • From: Miroslaw Mieszczak <mirek@xxxxxxxxxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: libata hotplug and md raid?
  • From: Mark Lord <mlord@xxxxxxxxx>
• Re: [PATCH] md: Fix bug where new drives added to an md array sometimes don't sync properly.
  • From: Neil Brown <neilb@xxxxxxx>
• RE: new features time-line
  • From: Neil Brown <neilb@xxxxxxx>
• Re: ANNOUNCE: mdadm 2.5.4 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: possible deadlock through raid5/md
  • From: "Peter T. Breuer" <ptb@xxxxxxxxxxxxxx>
• Re: Multiple Disk Failure Recovery
  • From: Roger Gammans <roger@xxxxxxxxxxxxxxxxxxxxxx>
• FW: Multiple Disk Failure Recovery
  • From: "Dan" <dan@xxxxxxxxxxx>
• Re: Multiple Disk Failure Recovery
  • From: "David Rees" <drees76@xxxxxxxxx>
• Multiple Disk Failure Recovery
  • From: Lane Brooks <lbrooks@xxxxxxx>
• Re: Cannot create RAID5 - device or resource busy
  • From: Ray Greene <raygr@xxxxxxxx>
• Re: Cannot create RAID5 - device or resource busy
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Cannot create RAID5 - device or resource busy
  • From: Ray Greene <raygr@xxxxxxxx>
• Re: problem during boot with linux software raid 5
  • From: Luca Berra <bluca@xxxxxxxxxx>
• problem during boot with linux software raid 5
  • From: jeff <jeff@xxxxxxxxxxxx>
• RE: new features time-line
  • From: "Dan" <dan@xxxxxxxxxxx>
• Re: new features time-line
  • From: Neil Brown <neilb@xxxxxxx>
• new features time-line
  • From: "Dan" <dan@xxxxxxxxxxx>
• Re: ANNOUNCE: mdadm 2.5.4 - A tool for managing Soft RAID under Linux
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: BUGS: internal bitmap during array create
  • From: Neil Brown <neilb@xxxxxxx>
• Re: BUGS: internal bitmap during array create
  • From: Eli Stair <estair@xxxxxxx>
• ANNOUNCE: mdadm 2.5.4 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: MegaRaid problems..
  • From: Mike Hardy <mhardy@xxxxxxx>
• Re: MegaRaid problems..
  • From: Joshua Baker-LePain <jlb17@xxxxxxxx>
• Re: [PATCH] md: Fix bug where new drives added to an md array sometimes don't sync properly.
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• MegaRaid problems..
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Starting point of the actual RAID data area
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: avoiding the initial resync on --create
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• [patch 56/67] MD: Fix problem where hot-added drives are not resynced.
  • From: Greg KH <gregkh@xxxxxxx>
• Re: Setting write-intent bitmap during array resync/create?
  • From: Eli Stair <estair@xxxxxxx>
• BUGS: internal bitmap during array create
  • From: Eli Stair <estair@xxxxxxx>
• Re: Stopping and starting a RAID1 :Invalid argument
  • From: "Ian Brown" <ianbrn@xxxxxxxxx>
• Re: Setting write-intent bitmap during array resync/create?
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] md: Fix bug where new drives added to an md array sometimes don't sync properly.
  • From: Eli Stair <estair@xxxxxxx>
• Re: avoiding the initial resync on --create
  • From: "Rev. Jeffrey Paul" <sneak@xxxxxxxxxxxx>
• Re: avoiding the initial resync on --create
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: [PATCH] md: Fix bug where new drives added to an md array sometimes don't sync properly.
  • From: Eli Stair <estair@xxxxxxx>
• Re: avoiding the initial resync on --create
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: avoiding the initial resync on --create
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: [PATCH] md: Fix bug where new drives added to an md array sometimes don't sync properly.
  • From: Eli Stair <estair@xxxxxxx>
• Setting write-intent bitmap during array resync/create?
  • From: Eli Stair <estair@xxxxxxx>
• Re: avoiding the initial resync on --create
  • From: Sergey Vlasov <vsu@xxxxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: avoiding the initial resync on --create
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: raid5 hang on get_active_stripe
  • From: Bas van Schaik <bas@xxxxxxxx>
• Re: avoiding the initial resync on --create
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: md deadlock (was Re: 2.6.18-mm2)
  • From: Ingo Molnar <mingo@xxxxxxx>
• Re: md deadlock (was Re: 2.6.18-mm2)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Stopping and starting a RAID1 :Invalid argument
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md: Fix bug where new drives added to an md array sometimes don't sync properly.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5 hang on get_active_stripe
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID10: near, far, offset -- which one?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5 hang on get_active_stripe
  • From: Chris Allen <chris@xxxxxxx>
• Re: avoiding the initial resync on --create
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid5 hang on get_active_stripe
  • From: Neil Brown <neilb@xxxxxxx>
• Re: type-0.90.0 superblock and "md-1" superblocks
  • From: Neil Brown <neilb@xxxxxxx>
• Re: avoiding the initial resync on --create
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: avoiding the initial resync on --create
  • From: Neil Brown <neilb@xxxxxxx>
• Re: avoiding the initial resync on --create
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: avoiding the initial resync on --create
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: avoiding the initial resync on --create
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• type-0.90.0 superblock and "md-1" superblocks
  • From: "Mark Ryden" <markryde@xxxxxxxxx>
• Re: avoiding the initial resync on --create
  • From: Erik Mouw <erik@xxxxxxxxxxxxxxxxxxxxx>
• avoiding the initial resync on --create
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Re: raid5 hang on get_active_stripe
  • From: Chris Allen <chris@xxxxxxx>
• Re: [PATCH/BUG] mdadm: write behind value does not have endian conversion
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Stopping and starting a RAID1 :Invalid argument
  • From: "Ian Brown" <ianbrn@xxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm segfault
  • From: Frank van Maarseveen <frankvm@xxxxxxxxxxx>
• Re: mdadm segfault
  • From: Henrik Holst <henrik.holst@xxxxxxxxxx>
• Re: Stopping and starting a RAID1 :Invalid argument
  • From: "Jim Buttafuoco" <jim@xxxxxxxxxxxxxx>
• Re: Stopping and starting a RAID1 :Invalid argument
  • From: "Ian Brown" <ianbrn@xxxxxxxxx>
• mdadm segfault
  • From: Frank van Maarseveen <frankvm@xxxxxxxxxxx>
• Re: Stopping and starting a RAID1 :Invalid argument
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Stopping and starting a RAID1 :Invalid argument
  • From: "Ian Brown" <ianbrn@xxxxxxxxx>
• Re: Starting point of the actual RAID data area
  • From: Daniel Pittman <daniel@xxxxxxxxxxxx>
• Re: raid5 hang on get_active_stripe
  • From: Chris Allen <chris@xxxxxxx>
• Re: IDE panic, 2.6.18
  • From: linux@xxxxxxxxxxx
• Starting point of the actual RAID data area
  • From: Jyri Hovila <jyri.hovila@xxxxxxxxxxx>
• Re: [PATCH] md: Fix bug where new drives added to an md array sometimes don't sync properly.
  • From: Eli Stair <estair@xxxxxxx>
• Re: [PATCH/BUG] mdadm: write behind value does not have endian conversion
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• [PATCH/BUG] mdadm: write behind value does not have endian conversion
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: mdadm RAID5 Grow
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm RAID5 Grow
  • From: mickg <mickg@xxxxxxxxx>
• Re: [PATCH] md: Fix bug where new drives added to an md array sometimes don't sync properly.
  • From: Eli Stair <estair@xxxxxxx>
• Re: RAID10: near, far, offset -- which one?
  • From: Eli Stair <estair@xxxxxxx>
• RAID10: near, far, offset -- which one?
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Re: mdadm RAID5 Grow
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm RAID5 Grow
  • From: mickg <mickg@xxxxxxxxx>
• Re: converting RAID5 to RAID10
  • From: Neil Brown <neilb@xxxxxxx>
• Re: converting RAID5 to RAID10
  • From: Ask Bjørn Hansen <ask@xxxxxxxxxxxxxx>
• Re: converting RAID5 to RAID10
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Re: converting RAID5 to RAID10
  • From: "Jurriaan Kalkman" <jurriaan@xxxxxxxxxxxxxxxxxxxxxx>
• Re: converting RAID5 to RAID10
  • From: Neil Brown <neilb@xxxxxxx>
• Re: question about raid5 parity calculations
  • From: Neil Brown <neilb@xxxxxxx>
• converting RAID5 to RAID10
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• possible deadlock through raid5/md
  • From: "Peter T. Breuer" <ptb@xxxxxxxxxxxxxx>
• [PATCH] md: Fix bug where new drives added to an md array sometimes don't sync properly.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm RAID5 Grow
  • From: Neil Brown <neilb@xxxxxxx>
• mdadm RAID5 Grow
  • From: mickg <mickg@xxxxxxxxx>
• Re: old raid tools dangerous with 2.6.18?
  • From: syrius.ml@xxxxxxxxxx
• Re: Recipe for Mirrored OS Drives
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Recipe for Mirrored OS Drives
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Recipe for Mirrored OS Drives
  • From: Erik Mouw <erik@xxxxxxxxxxxxxxxxxxxxx>
• Re: old raid tools dangerous with 2.6.18?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Recipe for Mirrored OS Drives
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Simulating Drive Failure on Mirrored OS drive
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Recipe for Mirrored OS Drives
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Recipe for Mirrored OS Drives
  • From: andy liebman <andyliebman@xxxxxxx>
• Re: Simulating Drive Failure on Mirrored OS drive
  • From: andy liebman <andyliebman@xxxxxxx>
• Re: mdadm and raidtools - noob
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Monitoring hardware raid
  • From: Jon Lewis <jlewis@xxxxxxxxx>
• Re: md deadlock (was Re: 2.6.18-mm2)
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: Monitoring hardware raid
  • From: Joshua Baker-LePain <jlb17@xxxxxxxx>
• Monitoring hardware raid
  • From: Mauricio Tavares <raub@xxxxxxx>
• mdadm and raidtools - noob
  • From: "Mark Ryden" <markryde@xxxxxxxxx>
• Re: [PATCH 003 of 6] md: Remove 'experimental' classification from raid5 reshape.
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Recipe for Mirrored OS Drives
  • From: David Greaves <david@xxxxxxxxxxxx>
• Re: Simulating Drive Failure on Mirrored OS drive
  • From: David Greaves <david@xxxxxxxxxxxx>
• Simulating Drive Failure on Mirrored OS drive
  • From: andy liebman <andyliebman@xxxxxxx>
• Recipe for Mirrored OS Drives
  • From: andy liebman <andyliebman@xxxxxxx>
• Re: old raid tools dangerous with 2.6.18?
  • From: syrius.ml@xxxxxxxxxx
• adp94xx driver giving errors and system crash
  • From: Clem Pryke <pryke@xxxxxxxxxxxxxxxxxx>
• Re: md deadlock (was Re: 2.6.18-mm2)
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: raid superblock checksum problem
  • From: Oliver Paulus <oliver@xxxxxxxxxxxxxxxx>
• Re: md deadlock (was Re: 2.6.18-mm2)
  • From: Neil Brown <neilb@xxxxxxx>
• md deadlock (was Re: 2.6.18-mm2)
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: [BUG/PATCH] md bitmap broken on big endian machines
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: [PATCH 003 of 6] md: Remove 'experimental' classification from raid5 reshape.
  • From: Jeff Breidenbach <jeff@xxxxxxx>
• [PATCH 006 of 6] md: Add error reporting to superblock write failure
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 004 of 6] md: Use ffz instead of find_first_set to convert multiplier to shift.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 005 of 6] md: Allow SET_BITMAP_FILE to work on 64bit kernel with 32bit userspace.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 003 of 6] md: Remove 'experimental' classification from raid5 reshape.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 002 of 6] md: Remove MAX_MD_DEVS which is an arbitrary limit.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 001 of 6] md: Fix duplicity of levels in md.txt
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 000 of 6] md: Introduction
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [BUG/PATCH] md bitmap broken on big endian machines
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: [BUG/PATCH] md bitmap broken on big endian machines
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• old raid tools dangerous with 2.6.18?
  • From: "Richard Bollinger" <rabollinger@xxxxxxxxx>
• Re: 2.6.18-mm2
  • From: "Michal Piotrowski" <michal.k.k.piotrowski@xxxxxxxxx>
• Re: [PATCH] md SET_BITMAP_FILE compat ioctl
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [BUG/PATCH] md bitmap broken on big endian machines
  • From: Neil Brown <neilb@xxxxxxx>
• Re: raid superblock checksum problem
  • From: Oliver Paulus <oliver@xxxxxxxxxxxxxxxx>
• Re: raid superblock checksum problem
  • From: Ask Bjørn Hansen <ask@xxxxxxxxxxxxxx>
• raid superblock checksum problem
  • From: Oliver Paulus <oliver@xxxxxxxxxxxxxxxx>
• Re: raid 1 recovery steps
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: how to set stride / raid-howto still up to date?
  • From: Mark Hahn <hahn@xxxxxxxxxxxxxxxxxxx>
• raid 1 recovery steps
  • From: chapman <chris@xxxxxxxxxxxxx>
• Re: ATA cables and drives
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: ATA cables and drives
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
• Re: ATA cables and drives
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• how to set stride / raid-howto still up to date?
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: ATA cables and drives
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
• Re: Memory issues with RAID5?
  • From: Mark Hahn <hahn@xxxxxxxxxxxxxxxxxxx>
• Memory issues with RAID5?
  • From: "Fredrik Lindgren" <fli@xxxxxxxx>
• [PATCH] md SET_BITMAP_FILE compat ioctl
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: Interesting RAID checking observations
  • From: linux@xxxxxxxxxxx
• Re: Interesting RAID checking observations
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• [BUG/PATCH] md bitmap broken on big endian machines
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: scrub was Re: RAID5 Problem - $1000 reward for help
  • From: linux@xxxxxxxxxxx
• Re: scrub was Re: RAID5 Problem - $1000 reward for help
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: Interesting RAID checking observations
  • From: linux@xxxxxxxxxxx
• Re: ATA cables and drives
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: ATA cables and drives
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: access array from knoppix
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: proactive-raid-disk-replacement
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Interesting RAID checking observations
  • From: linux@xxxxxxxxxxx
• Re: USB disks for RAID storage (was Re: Please help me save my data)
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
• Re: USB disks for RAID storage
  • From: Daniel Pittman <daniel@xxxxxxxxxxxx>
• Re: RAID-5 making big partition fails
  • From: Gaspar Bakos <gbakos@xxxxxxxxxxxxxxx>
• Re: RAID-5 making big partition fails
  • From: Joshua Baker-LePain <jlb17@xxxxxxxx>
• RAID-5 making big partition fails
  • From: Gaspar Bakos <gbakos@xxxxxxxxxxxxxxx>
• Re: [PATCH] dmaengine: clean up and abstract function types (was Re: [PATCH 08/19] dmaengine: enable multiple clients and operations)
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: [PATCH] dmaengine: clean up and abstract function types (was Re: [PATCH 08/19] dmaengine: enable multiple clients and operations)
  • From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
• Re: USB disks for RAID storage (was Re: Please help me save my data)
  • From: "Patrick Hoover" <phoover.eml@xxxxxxxxx>
• Re: [PATCH] dmaengine: clean up and abstract function types (was Re: [PATCH 08/19] dmaengine: enable multiple clients and operations)
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: Slackware and RAID
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: USB and raid... Device names change
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: [PATCH] dmaengine: clean up and abstract function types (was Re: [PATCH 08/19] dmaengine: enable multiple clients and operations)
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• USB and raid... Device names change
  • From: Eduardo Jacob <edu@xxxxxxxxx>
• Re: USB disks for RAID storage (was Re: Please help me save my data)
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
• Re: scrub was Re: RAID5 Problem - $1000 reward for help
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• scrub was Re: RAID5 Problem - $1000 reward for help
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: RAID5 Problem - $1000 reward for help
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: RAID5 Problem - $1000 reward for help
  • From: Ask Bjørn Hansen <ask@xxxxxxxxxxxxxx>
• Re: RAID5 Problem - $1000 reward for help
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• RE: ATA cables and drives
  • From: "Guy" <bugzilla@xxxxxxxxxxxxxxxx>
• USB disks for RAID storage (was Re: Please help me save my data)
  • From: Daniel Pittman <daniel@xxxxxxxxxxxx>
• Re: Please help me save my data
  • From: martin.kihlgren@xxxxxxxxxx
• Re: Slackware and RAID
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: Slackware and RAID
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Slackware and RAID
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• RE: proactive-raid-disk-replacement
  • From: "Guy" <bugzilla@xxxxxxxxxxxxxxxx>
• Re: Slackware and RAID
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: ATA cables and drives
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: ATA cables and drives
  • From: Jeff Woods <Kazrak+kernel@xxxxxxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: proactive-raid-disk-replacement
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID5 fill up?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• ATA cables and drives
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
• Re: Please help me save my data
  • From: "Molle Bestefich" <molle.bestefich@xxxxxxxxx>
• Slackware and RAID
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: access array from knoppix
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: 2.6.18-rc5-mm1 - bd_claim_by_disk oops
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• [PATCH] [v2] dmaengine: clean up and abstract function types (was Re: [PATCH 08/19] dmaengine: enable multiple clients and operations)
  • From: Olof Johansson <olof@xxxxxxxxx>
• [PATCH] dmaengine: clean up and abstract function types (was Re: [PATCH 08/19] dmaengine: enable multiple clients and operations)
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• Re: [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: [PATCH 16/19] dmaengine: Driver for the Intel IOP 32x, 33x, and 13xx RAID engines
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: [PATCH 09/19] dmaengine: reduce backend address permutations
  • From: Olof Johansson <olof@xxxxxxxxx>
• Re: RAID5 Problem - $1000 reward for help
  • From: Ask Bjørn Hansen <ask@xxxxxxxxxxxxxx>
• RAID5 Problem - $1000 reward for help
  • From: Reza Naima <reza@xxxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Lem <l3mming@xxxxxxxxxxxx>
• Re: [PATCH] missing close in mdassemble
  • From: Luca Berra <bluca@xxxxxxxxxx>
• I think there is a trick to improve performance of md.
  • From: liyiming <liyiming@xxxxxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: Greg KH <gregkh@xxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: PROBLEM: system crash on AMD64 with 2.6.17.11 while accessing 3TB Software-RAID5
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raidhotadd works, mdadm --add doesn't
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: access *exisiting* array from knoppix
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: access array from knoppix
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: access *exisiting* array from knoppix
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: access *exisiting* array from knoppix
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: Turbo Fredriksson <turbo@xxxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: Jakob Oestergaard <jakob@xxxxxxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• [PATCH] missing close in mdassemble
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: access *existing* array from knoppix
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: access *existing* array from knoppix
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• raid 5 kernel error
  • From: Sterpu Victor <victor@xxxxxxxx>
• Re: libata hotplug and md raid?
  • From: Tejun Heo <htejun@xxxxxxxxx>
• Re: libata hotplug and md raid?
  • From: Ric Wheeler <ric@xxxxxxx>
• libata hotplug and md raid?
  • From: "Leon Woestenberg" <leon.woestenberg@xxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: Jakob Oestergaard <jakob@xxxxxxxxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Lem <l3mming@xxxxxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• RE: Correct way to create multiple RAID volumes with hot-spare?
  • From: "Ruth Ivimey-Cook" <Ruth.Ivimey-Cook@xxxxxxxxxx>
• Re: Correct way to create multiple RAID volumes with hot-spare?
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: access *existing* array from knoppix
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: access *existing* array from knoppix
  • From: Henrik Holst <henrik.holst@xxxxxxxxxx>
• Re: Moving a raid5 array
  • From: Clive Messer <clive@xxxxxxxxxxxxxxxxx>
• Re: access *existing* array from knoppix
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: Moving a raid5 array
  • From: Neil Brown <neilb@xxxxxxx>
• Moving a raid5 array
  • From: Clive Messer <clive@xxxxxxxxxxxxxxxxx>
• Re: access *existing* array from knoppix
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: access *existing* array from knoppix
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: access *exisiting* array from knoppix
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: access array from knoppix
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• access array from knoppix
  • From: Dexter Filmore <Dexter.Filmore@xxxxxx>
• Re: [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: Evgeniy Polyakov <johnpol@xxxxxxxxxxx>
• Re: [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: Roland Dreier <rdreier@xxxxxxxxx>
• Re: [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 18/19] iop3xx: Give Linux control over PCI (ATU) initialization
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 17/19] iop3xx: define IOP3XX_REG_ADDR[32|16|8] and clean up DMA/AAU defs
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 15/19] dmaengine: raid5 dma client
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: "Dan Williams" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 14/19] dmaengine: add dma_sync_wait
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 12/19] dmaengine: dma_async_memcpy_err for DMA engines that do not support memcpy
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 11/19] dmaengine: add memset as an asynchronous dma operation
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 02/19] raid5: move write operations to a workqueue
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: [PATCH 01/19] raid5: raid5_do_soft_block_ops
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• [PATCH 07/19] raid5: remove compute_block and compute_parity5
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 02/19] raid5: move write operations to a workqueue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 03/19] raid5: move check parity operations to a workqueue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 05/19] raid5: move read completion copies to a workqueue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 10/19] dmaengine: expose per channel dma mapping characteristics to clients
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 19/19] iop3xx: IOP 32x and 33x support for the iop-adma driver
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 13/19] dmaengine: add support for dma xor zero sum operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 08/19] dmaengine: enable multiple clients and operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 12/19] dmaengine: dma_async_memcpy_err for DMA engines that do not support memcpy
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 09/19] dmaengine: reduce backend address permutations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 17/19] iop3xx: define IOP3XX_REG_ADDR[32|16|8] and clean up DMA/AAU defs
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 15/19] dmaengine: raid5 dma client
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 16/19] dmaengine: Driver for the Intel IOP 32x, 33x, and 13xx RAID engines
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 18/19] iop3xx: Give Linux control over PCI (ATU) initialization
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 14/19] dmaengine: add dma_sync_wait
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 06/19] raid5: move the reconstruct write expansion operation to a workqueue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 11/19] dmaengine: add memset as an asynchronous dma operation
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 04/19] raid5: move compute block operations to a workqueue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 01/19] raid5: raid5_do_soft_block_ops
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 00/19] Hardware Accelerated MD RAID5: Introduction
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: raidhotadd works, mdadm --add doesn't
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: Please help me save my data
  • From: "Patrick Hoover" <phoover.eml@xxxxxxxxx>
• Re: Please help me save my data
  • From: martin.kihlgren@xxxxxxxxxx
• raidhotadd works, mdadm --add doesn't
  • From: Leon Avery <leon@xxxxxxxxxxxxxxxxxx>
• raidhotadd works, mdadm --add doesn't
  • From: Leon Avery <leon@xxxxxxxxxxxxxxxxxx>
• Re: proactive-raid-disk-replacement
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Lem <l3mming@xxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: UUID's
  • From: dean gaudet <dean@xxxxxxxxxx>
• RE: 2 Hard Drives & RAID
  • From: "Guy" <bugzilla@xxxxxxxxxxxxxxxx>
• Re: 2 Hard Drives & RAID
  • From: Sandra McGrew <nurse1@xxxxxxxxxxxxxxxx>
• Re: proactive-raid-disk-replacement
  • From: Bodo Thiesen <bothie@xxxxxx>
• Re: 2 Hard Drives & RAID
  • From: berk walker <berk@xxxxxxxxx>
• Re: 2 Hard Drives & RAID
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Check/repair on composite RAID
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• 2 Hard Drives & RAID
  • From: "Sandra L. McGrew" <momo_1@xxxxxxxxxx>
• Re: Please help me save my data
  • From: "Tuomas Leikola" <tuomas.leikola@xxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Check/repair on composite RAID
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: UUID's
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: UUID's
  • From: dean gaudet <dean@xxxxxxxxxx>
• UUID's
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Messed up creating new array...
  • From: "David Rees" <drees76@xxxxxxxxx>
• Re: proactive-raid-disk-replacement
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: RAID5 fill up?
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• Please help me save my data
  • From: martin.kihlgren@xxxxxxxxxx
• Please help me save my data
  • From: martin.kihlgren@xxxxxxxxxx
• 2.6.18-rc5-mm1 - bd_claim_by_disk oops
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Messed up creating new array...
  • From: "Ruth Ivimey-Cook" <Ruth.Ivimey-Cook@xxxxxxxxxx>
• Re: RAID5 fill up?
  • From: Lars Schimmer <l.schimmer@xxxxxxxxxxxxx>
• Re: RAID5 fill up?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: RAID5 fill up?
  • From: Lars Schimmer <l.schimmer@xxxxxxxxxxxxx>
• Re: proactive-raid-disk-replacement
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: RAID5 fill up?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• RAID5 fill up?
  • From: Lars Schimmer <l.schimmer@xxxxxxxxxxxxx>
• RAID5 fill up?
  • From: Lars Schimmer <l.schimmer@xxxxxxxxxxxxx>
• Re: Interesting RAID checking observations - I'm getting it too
  • From: Mark Smith <nanog@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: proactive-raid-disk-replacement
  • From: dean gaudet <dean@xxxxxxxxxx>
• proactive-raid-disk-replacement
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: PROBLEM: system crash on AMD64 with 2.6.17.11 while accessing 3TB Software-RAID5
  • From: Ralf Herrmann <ralf.herrmann@xxxxxxxxxxxxx>
• Re: RAID-5 recovery
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: Raid5 reads and cpu
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: Raid5 reads and cpu
  • From: "Rob Bray" <raid@xxxxxxxxxxx>
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• Re: checking state of RAID (for automated notifications)
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: RAID-5 recovery
  • From: John McMonagle <johnm@xxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: checking state of RAID (for automated notifications)
  • From: Mike Hardy <mhardy@xxxxxxx>
• Re: checking md device parity (forced resync) - is it necessary?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: checking md device parity (forced resync) - is it necessary?
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• checking state of RAID (for automated notifications)
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: checking md device parity (forced resync) - is it necessary?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: Care and feeding of RAID?
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: checking md device parity (forced resync) - is it necessary?
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Re: Superblock checksum problems
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: "Rev. Jeffrey Paul" <sneak@xxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: checking md device parity (forced resync) - is it necessary?
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Patrik Jonsson <patrik@xxxxxxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Mike Hardy <mhardy@xxxxxxx>
• Re: Care and feeding of RAID?
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Steve Cousins <steve.cousins@xxxxxxxxx>
• Re: RAID over Firewire
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Care and feeding of RAID?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: Care and feeding of RAID?
  • From: Benjamin Schieder <blindcoder@xxxxxxxxxxxxxxxxxxxx>
• Care and feeding of RAID?
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: checking md device parity (forced resync) - is it necessary?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: large copy to mdadm array fails, marks readonly
  • From: Neil Brown <neilb@xxxxxxx>
• Re: checking md device parity (forced resync) - is it necessary?
  • From: Neil Brown <neilb@xxxxxxx>
• large copy to mdadm array fails, marks readonly
  • From: "Alan Gibson" <alan.gibson@xxxxxxxxx>
• checking md device parity (forced resync) - is it necessary?
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: Feature Request/Suggestion - "Drive Linking"
  • From: dean gaudet <dean@xxxxxxxxxx>
• Re: Superblock checksum problems
  • From: Henrik Holst <henrik.holst@xxxxxxxxxx>
• Re: Superblock checksum problems
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• Re: checkarray: E: no kernel support for parity checks.
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• Re: Superblock checksum problems
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Interesting RAID checking observations - I'm getting it too
  • From: Mark Smith <nanog@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Interesting RAID checking observations
  • From: linux@xxxxxxxxxxx
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• Re: RAID over Firewire
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Can you IMAGE Mirrored OS Drives?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID5 producing fake partition table on single drive
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID over Firewire
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Linux: Why software RAID?
  • From: Joel Jaeggli <joelja@xxxxxxxxxxx>
• Re: Linux: Why software RAID?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Linux: Why software RAID?
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Interesting RAID checking observations
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Raid5 reads and cpu
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: PROBLEM: system crash on AMD64 with 2.6.17.11 while accessing 3TB Software-RAID5
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: 3ware glitches cause softraid rebuilds
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Feature Request/Suggestion - "Drive Linking"
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Interesting RAID checking observations - I'm getting it too
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID6 fallen apart
  • From: Ferenc Wagner <wferi@xxxxxxx>
• Re: Superblock checksum problems
  • From: Josh Litherland <josh@xxxxxxxxxxx>
• checkarray: E: no kernel support for parity checks.
  • From: Guillaume Filion <gfk@xxxxxxxxxxx>
• Re: Strange IO stats on RAID1?
  • From: Paul Waldo <pwaldo@xxxxxxxxxxxxx>
• Re: RAID-5 recovery
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Raid5 reads and cpu
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID6 Problem (in conjunction with nested LVM and encryption)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID6 Problem (in conjunction with nested LVM and encryption)
  • From: Bodo Thiesen <bothie@xxxxxx>
• Re: Newbie: Kernel panic during RAID1 test & reboot loses one disk
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 001 of 4] md: Define backing_dev_info.congested_fn for raid0 and linear
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Strange IO stats on RAID1?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm dynamic multipathing
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Superblock checksum problems
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID6 Problem (in conjunction with nested LVM and encryption)
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID-5 recovery
  • From: Neil Brown <neilb@xxxxxxx>
• RAID-0 on the Intel ICH7R chipset and swap configuration...
  • From: "Julio Meca Hansen" <julio28@xxxxxxxxxxxxxxxx>
• Re: RAID-5 recovery
  • From: "Martin Schröder" <martin@xxxxxxxxxx>
• Re: RAID-5 recovery
  • From: Clive Messer <clive@xxxxxxxxxxxxxxxxx>