Linux RAID Storage Date Index

• Thread Index

• Re: About seting up Raid5 on a four disk box.
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: xfs > md 50% write performance drop on .30+ kernel?
  • From: mark delfman <markdelfman@xxxxxxxxxxxxxx>
• Re: xfs > md 50% write performance drop on .30+ kernel?
  • From: mark delfman <markdelfman@xxxxxxxxxxxxxx>
• Re: About seting up Raid5 on a four disk box.
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: About seting up Raid5 on a four disk box.
  • From: Antonio Perez <ap23563m@xxxxxxx>
• Re: xfs > md 50% write performance drop on .30+ kernel?
  • From: Asdo <asdo@xxxxxxxxxxxxx>
• Re: xfs > md 50% write performance drop on .30+ kernel?
  • From: Asdo <asdo@xxxxxxxxxxxxx>
• Re: About seting up Raid5 on a four disk box.
  • From: "Majed B." <majedb@xxxxxxxxx>
• About seting up Raid5 on a four disk box.
  • From: Antonio Perez <ap23563m@xxxxxxx>
• Re: raid1 running fine for years .. and then
  • From: Michael-John Turner <mj@xxxxxxxxxxxx>
• Re: xfs > md 50% write performance drop on .30+ kernel?
  • From: mark delfman <markdelfman@xxxxxxxxxxxxxx>
• Re: xfs > md 50% write performance drop on .30+ kernel?
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: xfs > md 50% write performance drop on .30+ kernel?
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: xfs > md 50% write performance drop on .30+ kernel?
  • From: mark delfman <markdelfman@xxxxxxxxxxxxxx>
• Re: xfs > md 50% write performance drop on .30+ kernel?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: xfs > md 50% write performance drop on .30+ kernel?
  • From: Asdo <asdo@xxxxxxxxxxxxx>
• Re: xfs > md 50% write performance drop on .30+ kernel?
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: xfs > md 50% write performance drop on .30+ kernel?
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: xfs > md 50% write performance drop on .30+ kernel?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Load-balancing mirrors w/ asymmetric performance
  • From: Mike Snitzer <snitzer@xxxxxxxxx>
• Feature request: ability to exchange drive without failing the old one
  • From: Christian Pernegger <pernegger@xxxxxxxxx>
• Re: xfs > md 50% write performance drop on .30+ kernel?
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: raid1 running fine for years .. and then
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• xfs > md 50% write performance drop on .30+ kernel?
  • From: mark delfman <markdelfman@xxxxxxxxxxxxxx>
• Re: raid1 running fine for years .. and then
  • From: Michael-John Turner <mj@xxxxxxxxxxxx>
• Re: Load-balancing mirrors w/ asymmetric performance
  • From: Chris Worley <worleys@xxxxxxxxx>
• Re: Load-balancing mirrors w/ asymmetric performance
  • From: Mike Snitzer <snitzer@xxxxxxxxx>
• Re: [PATCH 1/1] md: drivers/md/unroll.pl replaced with awk analog
  • From: Vladimir Dronnikov <dronnikov@xxxxxxxxx>
• Re: [PATCH 1/1] md: drivers/md/unroll.pl replaced with awk analog
  • From: Neil Brown <neilb@xxxxxxx>
• Re: MVSAS 1669:mvs_abort_task:rc= 5
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• [BUG] Soft lockups in 2.6.32-rc3
  • From: "Steinar H. Gunderson" <sgunderson@xxxxxxxxxxx>
• stuck in resync=DELAYED if other resyncing array is stopped
  • From: Anssi Hannula <anssi.hannula@xxxxxxxxx>
• Re: md: could not bd_claim hde1
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: MVSAS 1669:mvs_abort_task:rc= 5
  • From: Christian Vilhelm <christian.vilhelm@xxxxxxxxxxxxxx>
• Re: [PATCH 0/3] md fixes for 2.6.32-rc
  • From: Asdo <asdo@xxxxxxxxxxxxx>
• Re: md: could not bd_claim hde1
  • From: Jon Lewis <jlewis@xxxxxxxxx>
• Re: [PATCH 0/3] md fixes for 2.6.32-rc
  • From: Asdo <asdo@xxxxxxxxxxxxx>
• Re: md: could not bd_claim hde1
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• RE: NAS Remote Side of a Mirror
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: md: could not bd_claim hde1
  • From: Jon Lewis <jlewis@xxxxxxxxx>
• Re: md: could not bd_claim hde1
  • From: "NeilBrown" <neilb@xxxxxxx>
• md: could not bd_claim hde1
  • From: Jon Lewis <jlewis@xxxxxxxxx>
• Re: MVSAS 1669:mvs_abort_task:rc= 5
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: MVSAS 1669:mvs_abort_task:rc= 5
  • From: "Thomas Fjellstrom" <tfjellstrom@xxxxxxx>
• Re: NAS Remote Side of a Mirror
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: NAS Remote Side of a Mirror
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: NAS Remote Side of a Mirror
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: NAS Remote Side of a Mirror
  • From: Drew <drew.kay@xxxxxxxxx>
• RE: NAS Remote Side of a Mirror
  • From: adfas asd <chimera_god@xxxxxxxxx>
• RE: NAS Remote Side of a Mirror
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: raid1 running fine for years .. and then
  • From: Clinton Lee Taylor <clintonlee.taylor@xxxxxxxxx>
• Re: raid1 running fine for years .. and then
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: raid1 running fine for years .. and then
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: NAS Remote Side of a Mirror
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: NAS Remote Side of a Mirror
  • From: russ@xxxxxxxxxx
• Re: NAS Remote Side of a Mirror
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: NAS Remote Side of a Mirror
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: NAS Remote Side of a Mirror
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: NAS Remote Side of a Mirror
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: NAS Remote Side of a Mirror
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• RE: NAS Remote Side of a Mirror
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: [PATCH 0/3] md fixes for 2.6.32-rc
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: NAS Remote Side of a Mirror
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• raid1 running fine for years .. and then
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• RE: NAS Remote Side of a Mirror
  • From: Chris Green <cgreen@xxxxxxxxxxxxxxxxx>
• Re: NAS Remote Side of a Mirror
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: [PATCH 0/3] md fixes for 2.6.32-rc
  • From: Asdo <asdo@xxxxxxxxxxxxx>
• RE: A few remaining questions about installing to RAID-10
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: mdadm segfault when assembling the array
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: mdadm segfault when assembling the array
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: [PATCH 0/3] md fixes for 2.6.32-rc
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: mdadm segfault when assembling the array
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: mdadm segfault when assembling the array
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: mdadm segfault when assembling the array
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• Re: mdadm segfault when assembling the array
  • From: Beolach <beolach@xxxxxxxxx>
• Re: mdadm segfault when assembling the array
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: mdadm segfault when assembling the array
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• mdadm segfault when assembling the array
  • From: Tomasz Chmielewski <mangoo@xxxxxxxx>
• [PATCH 0/8] Add vsprintf extension %pU to print UUID/GUIDs and use it
  • From: Joe Perches <joe@xxxxxxxxxxx>
• [PATCH 4/8] drivers/md/md.c: Use %pU to print UUIDs
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH 0/3] md fixes for 2.6.32-rc
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 0/3] md fixes for 2.6.32-rc
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Ben DJ <bendj095124367913213465@xxxxxxxxx>
• Re: NAS Remote Side of a Mirror
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: NAS Remote Side of a Mirror
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: [PATCH 1/1] md: drivers/md/unroll.pl replaced with awk analog
  • From: Rob Landley <rob@xxxxxxxxxxx>
• Re: [PATCH 1/1] md: drivers/md/unroll.pl replaced with awk analog
  • From: Vladimir Dronnikov <dronnikov@xxxxxxxxx>
• [PATCH 1/1] md: drivers/md/unroll.pl replaced with awk analog, revisited
  • From: Vladimir Dronnikov <dronnikov@xxxxxxxxx>
• Re: [PATCH 1/1] md: drivers/md/unroll.pl replaced with awk analog
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: [PATCH 1/1] md: drivers/md/unroll.pl replaced with awk analog
  • From: Rob Landley <rob@xxxxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Drew <drew.kay@xxxxxxxxx>
• RE: A few remaining questions about installing to RAID-10
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: [PATCH 1/1] md: drivers/md/unroll.pl replaced with awk analog
  • From: berk walker <berk@xxxxxxxxx>
• Re: [PATCH 1/1] md: drivers/md/unroll.pl replaced with awk analog
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 1/1] md: drivers/md/unroll.pl replaced with awk analog
  • From: Rob Landley <rob@xxxxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Drew <drew.kay@xxxxxxxxx>
• RE: A few remaining questions about installing to RAID-10
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: A few remaining questions about installing to RAID-10
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: ANNOUNCE: mdadm 3.0.1 - A tool for managing Soft RAID under Linux
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Drew <drew.kay@xxxxxxxxx>
• [PATCH 1/1] md: drivers/md/unroll.pl replaced with awk analog
  • From: Vladimir Dronnikov <dronnikov@xxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Drew <drew.kay@xxxxxxxxx>
• NAS Remote Side of a Mirror
  • From: adfas asd <chimera_god@xxxxxxxxx>
• RE: A few remaining questions about installing to RAID-10
  • From: adfas asd <chimera_god@xxxxxxxxx>
• RE: A few remaining questions about installing to RAID-10
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: ANNOUNCE: mdadm 3.0.1 - A tool for managing Soft RAID under Linux
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Full use of varying drive sizes?---maybe a new raid mode is the answer?
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• RE: A few remaining questions about installing to RAID-10
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: ANNOUNCE: mdadm 3.0.1 - A tool for managing Soft RAID under Linux
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• Load-balancing mirrors w/ asymmetric performance
  • From: Chris Worley <worleys@xxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: [PATCH 0/3] md fixes for 2.6.32-rc
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: RAID10 - migrating disks without failing/degrading array?
  • From: Tom Carlson <twigathy@xxxxxxxxx>
• Shifting 0xFD partition's end boundary && 0.90 format superblock == Bad Idea(?)
  • From: Igor Podlesny <for.poige+linux@xxxxxxxxx>
• Re: RAID10 - migrating disks without failing/degrading array?
  • From: David Rees <drees76@xxxxxxxxx>
• RAID10 - migrating disks without failing/degrading array?
  • From: David Rees <drees76@xxxxxxxxx>
• Re: [PATCH] md: Track raid5/6 statistics
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Ben DJ <bendj095124367913213465@xxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: [PATCH] md: Track raid5/6 statistics
  • From: Jody McIntyre <scjody@xxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Ben DJ <bendj095124367913213465@xxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: [patch 4/4] [ext3] Add journal guided resync (data=declared mode)
  • From: Jody McIntyre <scjody@xxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Ben DJ <bendj095124367913213465@xxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Ben DJ <bendj095124367913213465@xxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: raid0 failures
  • From: mark delfman <markdelfman@xxxxxxxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: raid0 failures
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH 0/3] md fixes for 2.6.32-rc
  • From: Neil Brown <neilb@xxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Ben DJ <bendj095124367913213465@xxxxxxxxx>
• Re: A few remaining questions about installing to RAID-10
  • From: Neil Brown <neilb@xxxxxxx>
• A few remaining questions about installing to RAID-10
  • From: Ben DJ <bendj095124367913213465@xxxxxxxxx>
• A few remaining questions about installing to RAID-10
  • From: Ben DJ <bendj095124367913213465@xxxxxxxxx>
• Re: [patch 4/4] [ext3] Add journal guided resync (data=declared mode)
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH 1/3] md/raid5: initialize conf->device_lock earlier
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 3/3] Allow sysfs_notify_dirent to be called from interrupt context.
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2/3] Revert "md/raid456: distribute raid processing over multiple cores"
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 0/3] md fixes for 2.6.32-rc
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [patch 0/4] Journal guided resync and support
  • From: Andi Kleen <andi@xxxxxxxxxxxxxx>
• Re: [patch 3/4] [jbd] Add support for journal guided resync.
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• [patch 1/4] [md] Add SKIP_RESYNC ioctl
  • From: scjody@xxxxxxx
• [patch 0/4] Journal guided resync and support
  • From: scjody@xxxxxxx
• [patch 3/4] [jbd] Add support for journal guided resync.
  • From: scjody@xxxxxxx
• [patch 2/4] [md] Add RESYNC_RANGE ioctl
  • From: scjody@xxxxxxx
• [patch 4/4] [ext3] Add journal guided resync (data=declared mode)
  • From: scjody@xxxxxxx
• Re: software raid rebuilding and O_DIRECT access (xfs_repair) slowness
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• software raid rebuilding and O_DIRECT access (xfs_repair) slowness
  • From: Arkadiusz Miskiewicz <a.miskiewicz@xxxxxxxxx>
• Re: HW Raid Question
  • From: Drew <drew.kay@xxxxxxxxx>
• raid0 failures
  • From: Raz <raziebe@xxxxxxxxx>
• Re: BUG: soft lockup in [md4_raid5:21137]
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: HW Raid Question
  • From: Mikhail Yakshin <greycat@xxxxxxxxxxxx>
• Re: [Bugme-new] [Bug 14214] New: BUG at drivers/scsi/scsi_lib.c:1108!
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• RE: Remote NAS
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: Cannnot umount to fix a corrupted Superblock on Buffalo Terastation (Linux) RAID 5
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: Slow network speeds between Linux RAID box and Windows PC
  • From: Eric Ramsey <tomoyodaidoji@xxxxxxxxx>
• Re: Slow network speeds between Linux RAID box and Windows PC
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: Slow network speeds between Linux RAID box and Windows PC
  • From: "Majed B." <majedb@xxxxxxxxx>
• Slow network speeds between Linux RAID box and Windows PC
  • From: Dylan Distasio <interzone@xxxxxxxxx>
• Cannnot umount to fix a corrupted Superblock on Buffalo Terastation (Linux) RAID 5
  • From: sidmanm <sidmanm@xxxxxxxxx>
• Re: BUG: soft lockup in [md4_raid5:21137]
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: HW Raid Question
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: HW Raid Question
  • From: Mikhail Yakshin <greycat@xxxxxxxxxxxx>
• Re: Remote NAS
  • From: adfas asd <chimera_god@xxxxxxxxx>
• RE: Remote NAS
  • From: adfas asd <chimera_god@xxxxxxxxx>
• RE: Remote NAS
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: Remote NAS
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: BUG: soft lockup in [md4_raid5:21137]
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• [PATCH 5/9] drivers/md/md.c: Use %pU to print UUIDs
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: mdadm 3.0.2 won't read mdadm.conf file
  • From: Aggelos Kyritsis <filodoksos@xxxxxxxxx>
• Re: mdadm 3.0.2 won't read mdadm.conf file
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: mdadm 3.0.2 won't read mdadm.conf file
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: mdadm 3.0.2 won't read mdadm.conf file
  • From: Aggelos Kyritsis <filodoksos@xxxxxxxxx>
• Re: mdadm 3.0.2 won't read mdadm.conf file
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: HW Raid Question
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• Re: HW Raid Question
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: mdadm 3.0.2 won't read mdadm.conf file
  • From: Aggelos Kyritsis <filodoksos@xxxxxxxxx>
• raid6 recovery suboptimal
  • From: Frank Mori Hess <frank.hess@xxxxxxxx>
• Re: Remote NAS
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: mdadm 3.0.2 won't read mdadm.conf file
  • From: Aggelos Kyritsis <filodoksos@xxxxxxxxx>
• Re: Full use of varying drive sizes?---maybe a new raid mode is the answer?
  • From: Konstantinos Skarlatos <k.skarlatos@xxxxxxxxx>
• RE: Remote NAS
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: Full use of varying drive sizes?---maybe a new raid mode is the answer?
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: mdadm 3.0.2 won't read mdadm.conf file
  • From: Kristleifur Daðason <kristleifur@xxxxxxxxx>
• mdadm 3.0.2 won't read mdadm.conf file
  • From: Aggelos Kyritsis <filodoksos@xxxxxxxxx>
• Re: HW Raid Question
  • From: "Majed B." <majedb@xxxxxxxxx>
• HW Raid Question
  • From: Drew <drew.kay@xxxxxxxxx>
• RE: Remote NAS
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: Remote NAS
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: Remote NAS
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: Remote NAS
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: Remote NAS
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: Full use of varying drive sizes?---maybe a new raid mode is the answer?
  • From: Konstantinos Skarlatos <k.skarlatos@xxxxxxxxx>
• Re: mdraid causing mvsas to lockup?
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: [PATCH] md: stop using do_sync_mapping_range
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: RAID1 assembled broken array
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• RE: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Sunpyo Hong" <sunpyo.hong@xxxxxxxx>
• RAID0 fail monitoring
  • From: mark delfman <markdelfman@xxxxxxxxxxxxxx>
• Re: md data-check causes soft lockup
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: md data-check causes soft lockup
  • From: kwick <kwick@xxxxxxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID1 assembled broken array
  • From: Neil Brown <neilb@xxxxxxx>
• Re: SET_BITMAP_FILE assembling raid1
  • From: Neil Brown <neilb@xxxxxxx>
• ANNOUNCE: mdadm 3.0.1 - A tool for managing Soft RAID under Linux
  • From: Neil Brown <neilb@xxxxxxx>
• Re: md data-check causes soft lockup
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Full use of varying drive sizes?---maybe a new raid mode is the answer?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: mdadm 3.0: segfault. known issue?
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Full use of varying drive sizes?---maybe a new raid mode is the answer?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• PULL REQUEST - md updates for 2.6.32
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Remote NAS
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: Remote NAS
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: [PATCH] md: stop using do_sync_mapping_range
  • From: Neil Brown <neilb@xxxxxxx>
• RE: Full use of varying drive sizes?---maybe a new raid mode is the answer?
  • From: Chris Green <cgreen@xxxxxxxxxxxxxxxxx>
• Re: Remote NAS
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Full use of varying drive sizes?---maybe a new raid mode is the answer?
  • From: Konstantinos Skarlatos <k.skarlatos@xxxxxxxxx>
• Re: Remote NAS
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• RE: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Sunpyo Hong" <sunpyo.hong@xxxxxxxx>
• Re: Remote NAS
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: Remote NAS
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Remote NAS
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: Full use of varying drive sizes?
  • From: Jon Hardcastle <jd_hardcastle@xxxxxxxxx>
• Re: Remote NAS
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• RE: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Sunpyo Hong" <sunpyo.hong@xxxxxxxx>
• Re: [PATCH] md: stop using do_sync_mapping_range
  • From: Jamie Lokier <jamie@xxxxxxxxxxxxx>
• [PATCH] md: stop using do_sync_mapping_range
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: Full use of varying drive sizes?
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Full use of varying drive sizes?
  • From: Tapani Tarvainen <raid@xxxxxxxxxxxxxxxxxx>
• Re: Full use of varying drive sizes?
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Remote NAS
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Full use of varying drive sizes?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Remote NAS
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• RE: md data-check causes soft lockup
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• RE: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• Re: md data-check causes soft lockup
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: md data-check causes soft lockup
  • From: Gabriele Trombetti <gabriele.trombetti@xxxxxxxxxx>
• Re: Remote NAS
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: Remote NAS
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Remote NAS
  • From: adfas asd <chimera_god@xxxxxxxxx>
• RE: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Sunpyo Hong" <sunpyo.hong@xxxxxxxx>
• Re: md data-check causes soft lockup
  • From: kwick <kwick@xxxxxxxxxxxxx>
• Re: Full use of varying drive sizes?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Full use of varying drive sizes?
  • From: Ryan Wagoner <rswagoner@xxxxxxxxx>
• Re: Full use of varying drive sizes?
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Full use of varying drive sizes?
  • From: Jon Hardcastle <jd_hardcastle@xxxxxxxxx>
• Re: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: md data-check causes soft lockup
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• RE: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Sunpyo Hong" <sunpyo.hong@xxxxxxxx>
• Re: md data-check causes soft lockup
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: md data-check causes soft lockup
  • From: Lee Howard <faxguy@xxxxxxxxxxxxxxxx>
• Re: md data-check causes soft lockup
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: md data-check causes soft lockup
  • From: Lee Howard <faxguy@xxxxxxxxxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: Full use of varying drive sizes?
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Full use of varying drive sizes?
  • From: Tapani Tarvainen <raid@xxxxxxxxxxxxxxxxxx>
• Re: Full use of varying drive sizes?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Full use of varying drive sizes?
  • From: Kristleifur Daðason <kristleifur@xxxxxxxxx>
• Full use of varying drive sizes?
  • From: Jon Hardcastle <jd_hardcastle@xxxxxxxxx>
• Re: Random bit flips - better data integrity needed [Was: Re: mismatch_count != 0 on multiple hosts]
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• [PATCH] Re: raid6 recovery with read errors
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• RE: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "NeilBrown" <neilb@xxxxxxx>
• [git pull] ioat/async_tx fixes for 2.6.32
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: LVM and Raid5
  • From: "Majed B." <majedb@xxxxxxxxx>
• mdadm 3.0: segfault. known issue?
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: md data-check causes soft lockup
  • From: "Majed B." <majedb@xxxxxxxxx>
• md data-check causes soft lockup
  • From: Lee Howard <faxguy@xxxxxxxxxxxxxxxx>
• Re: LVM and Raid5
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: LVM and Raid5
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: LVM and Raid5
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: LVM and Raid5
  • From: Jon Hardcastle <jd_hardcastle@xxxxxxxxx>
• Re: mdraid causing mvsas to lockup?
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• RE: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Sunpyo Hong" <sunpyo.hong@xxxxxxxx>
• Re: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• RE: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Sunpyo Hong" <sunpyo.hong@xxxxxxxx>
• Re: LVM and Raid5
  • From: Mike Snitzer <snitzer@xxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: "Majed B." <majedb@xxxxxxxxx>
• RE: RAID 5 array recovery - two drives errors in external enclosure
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: Tim Bostrom <tbostrom@xxxxxxxxx>
• RE: External enclosure - USB : How are the drives presented for software RAID?
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: [PATCH] barrier support for other md/raid levels
  • From: Neil Brown <neilb@xxxxxxx>
• Re: Random bit flips - better data integrity needed
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Random bit flips - better data integrity needed
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PATCH] barrier support for other md/raid levels
  • From: Clinton Lee Taylor <clintonlee.taylor@xxxxxxxxx>
• Re: RAID 16?
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: CPU util with and without Raid5
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• kernel BUG when umounting xfs on read-only md
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Dumb questions about mdadm #1 - replacing broken disks - "slot" reuse?
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Random bit flips - better data integrity needed [Was: Re: mismatch_count != 0 on multiple hosts]
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: BUG: soft lockup in [md4_raid5:21137]
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: Random bit flips - better data integrity needed [Was: Re: mismatch_count != 0 on multiple hosts]
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Random bit flips - better data integrity needed [Was: Re: mismatch_count != 0 on multiple hosts]
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• CPU util with and without Raid5
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Random bit flips - better data integrity needed [Was: Re: mismatch_count != 0 on multiple hosts]
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: mismatch_count != 0 on multiple hosts
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: [PATCH] barrier support for other md/raid levels
  • From: Michael Guntsche <mike@xxxxxxxxxxxx>
• RE: RAID 5 array recovery - two drives errors in external enclosure
  • From: "Guy Watkins" <guy@xxxxxxxxxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: Tom Carlson <twigathy@xxxxxxxxx>
• Re: mismatch_count != 0 on multiple hosts
  • From: Bryan Mesich <bryan.mesich@xxxxxxxx>
• CPU util with and without Raid5
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: Tim Bostrom <tbostrom@xxxxxxxxx>
• Re: mdraid causing mvsas to lockup? (was: Re: recommended 4port SATA controller ?)
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: [PATCH] barrier support for other md/raid levels
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Dumb questions about mdadm #1 - replacing broken disks - "slot" reuse?
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Can md/mdadm deal with non-standard size of internal bitmap?
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: [PATCH] barrier support for other md/raid levels
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• RE: [PATCH] barrier support for other md/raid levels
  • From: Chris Green <cgreen@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] barrier support for other md/raid levels
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: [PATCH] barrier support for other md/raid levels
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: BUG: soft lockup in [md4_raid5:21137]
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: SET_BITMAP_FILE assembling raid1
  • From: aristizb@xxxxxxxxxxx
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: Tim Bostrom <tbostrom@xxxxxxxxx>
• BUG: soft lockup in [md4_raid5:21137]
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Dumb questions about mdadm #1 - replacing broken disks - "slot" reuse?
  • From: John Hughes <john@xxxxxxxxx>
• Re: [PATCH] barrier support for other md/raid levels
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• mdraid causing mvsas to lockup? (was: Re: recommended 4port SATA controller ?)
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: SET_BITMAP_FILE assembling raid1
  • From: Neil Brown <neilb@xxxxxxx>
• [PATCH] barrier support for other md/raid levels
  • From: Neil Brown <neilb@xxxxxxx>
• PULL REQUEST - md updates for 2.6.32, mostly raid6 offload
  • From: Neil Brown <neilb@xxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: Tim Bostrom <tbostrom@xxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: Tim Bostrom <tbostrom@xxxxxxxxx>
• RE: RAID 5 array recovery - two drives errors in external enclosure
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: John Bridges <john.bridges@xxxxxxxxx>
• External enclosure - USB : How are the drives presented for software RAID?
  • From: Tim Bostrom <tbostrom@xxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: John Bridges <john.bridges@xxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: "Rainer Fuegenstein" <rfu@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: Tim Bostrom <tbostrom@xxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Kristleifur Daðason <kristleifur@xxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: Tim Bostrom <tbostrom@xxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Kristleifur Daðason <kristleifur@xxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: Tim Bostrom <tbostrom@xxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Majed B." <majedb@xxxxxxxxx>
• SET_BITMAP_FILE assembling raid1
  • From: aristizb@xxxxxxxxxxx
• Re: Formatting Raid5 device as NTFS
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: Tim Bostrom <tbostrom@xxxxxxxxx>
• RE: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Sunpyo Hong" <sunpyo.hong@xxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: Formatting Raid5 device as NTFS
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• RE: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Sunpyo Hong" <sunpyo.hong@xxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: John Bridges <john.bridges@xxxxxxxxx>
• Re: Formatting Raid5 device as NTFS
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Formatting Raid5 device as NTFS
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: RAID 5 array recovery - two drives errors in external enclosure
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Raid 5 Issue, cannot recognize EXT3 File system.
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• RAID 5 array recovery - two drives errors in external enclosure
  • From: Tim Bostrom <tbostrom@xxxxxxxxx>
• Raid 5 Issue, cannot recognize EXT3 File system.
  • From: "Sunpyo Hong" <sunpyo.hong@xxxxxxxx>
• Re: Formatting Raid5 device as NTFS
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Formatting Raid5 device as NTFS
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• [git pull] dmaengine, async_tx, and raid6 for 2.6.32
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Jon Hardcastle <jd_hardcastle@xxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Rui Santos <rsantos@xxxxxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Rainer Fuegenstein <rfu@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Christian Pernegger <pernegger@xxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Tapani Tarvainen <raid@xxxxxxxxxxxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Max Waterman <davidmaxwaterman@xxxxxxxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Jon Lewis <jlewis@xxxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: LVM and Raid5
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: recommended 4port SATA controller ?
  • From: "Majed B." <majedb@xxxxxxxxx>
• recommended 4port SATA controller ?
  • From: Rainer Fuegenstein <rfu@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: Andre Noll <maan@xxxxxxxxxxxxxxx>
• How to change stripe cache size
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Raid5 Read stats for parity cal...
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH] md: set the md raid 4,5,6 thead name by its level
  • From: Neil Brown <neilb@xxxxxxx>
• changing stripe cache size
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: Raid5 Read stats for parity cal...
  • From: "Majed B." <majedb@xxxxxxxxx>
• Raid5 Read stats for parity cal...
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: mismatch_count != 0 on multiple hosts
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• mismatch_count != 0 on multiple hosts
  • From: Bryan Mesich <bryan.mesich@xxxxxxxx>
• Re: Port Multipliers
  • From: Tom Carlson <twigathy@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: Port Multipliers
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Port Multipliers
  • From: "Majed B." <majedb@xxxxxxxxx>
• Remote NAS
  • From: adfas asd <chimera_god@xxxxxxxxx>
• Re: Port Multipliers
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Assemble and Stop array
  • From: "Majed B." <majedb@xxxxxxxxx>
• RE: Port Multipliers
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: Port Multipliers
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Port Multipliers
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• RE: Assemble and Stop array
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: Assemble and Stop array
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: Port Multipliers
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Port Multipliers
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: LVM and Raid5
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Alex Butcher <linraid@xxxxxxxxxxxxxx>
• Re: Port Multipliers
  • From: Tom Carlson <twigathy@xxxxxxxxx>
• Re: LVM and Raid5
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: LVM and Raid5
  • From: Jon Hardcastle <jd_hardcastle@xxxxxxxxx>
• Re: LVM and Raid5
  • From: "Majed B." <majedb@xxxxxxxxx>
• Reducing retries of devices in RAID 1 sets.
  • From: Simon Jackson <sjackson@xxxxxxxxxxx>
• Re: LVM and Raid5
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: LVM and Raid5
  • From: Jon Hardcastle <jd_hardcastle@xxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Goswin von Brederlow <goswin-v-b@xxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: "Majed B." <majedb@xxxxxxxxx>
• [PATCH] md: set the md raid 4,5,6 thead name by its level
  • From: Jinzc <zhenchengjin@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• [PATCH] md: set the md raid 4,5,6 thead name by its level
  • From: Jinzc <zhenchengjin@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• LVM and Raid5
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: Assemble and Stop array
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Assemble and Stop array
  • From: "NeilBrown" <neilb@xxxxxxx>
• RE: Assemble and Stop array
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: Port Multipliers
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Port Multipliers
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Port Multipliers
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Port Multipliers
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Port Multipliers
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Assemble and Stop array
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: Port Multipliers
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: [PATCH 21/29] ioat2,3: dynamically resize descriptor ring
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Port Multipliers
  • From: David Rees <drees76@xxxxxxxxx>
• Re: Port Multipliers
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Can md/mdadm deal with non-standard size of internal bitmap?
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Port Multipliers
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Port Multipliers
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: Port Multipliers
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Port Multipliers
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Port Multipliers
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: RAID1 assembled broken array
  • From: "Majed B." <majedb@xxxxxxxxx>
• RAID1 assembled broken array
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Port Multipliers
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Port Multipliers
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: raid disappearing mdadm: cannot get array info
  • From: "Majed B." <majedb@xxxxxxxxx>
• raid disappearing mdadm: cannot get array info
  • From: aristizb@xxxxxxxxxxx
• Re: Can md/mdadm deal with non-standard size of internal bitmap?
  • From: Louis-Michel Gelinas <coradiant.kernel@xxxxxxxxx>
• Re: [PATCH 02/18] dmaengine, async_tx: add a "no channel switch" allocator
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: What's in async_tx.git/next for 2.6.32?
  • From: Atsushi Nemoto <anemo@xxxxxxxxxxxxx>
• RE: [PATCH 18/18] I/OAT: Convert to PCI_VDEVICE()
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 17/18] Add MODULE_DEVICE_TABLE() so ioatdma module is autoloaded
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 15/18] ioat3: ioat3.2 pci ids for Jasper Forest
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 14/18] ioat3: interrupt descriptor support
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 13/18] ioat3: support xor via pq descriptors
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 12/18] ioat3: pq support
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 16/18] ioat3: segregate raid engines
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 11/18] ioat3: xor self test
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 08/18] ioat: add 'ioat' sysfs attributes
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 09/18] ioat3: enable dca for completion writes
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 10/18] ioat3: xor support
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 07/18] ioat3: split ioat3 support to its own file, add memset
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 06/18] ioat3: hardware version 3.2 register / descriptor definitions
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 05/18] ioat2+: add fence support
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 02/18] dmaengine, async_tx: add a "no channel switch" allocator
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 01/18] dmaengine: add fence support
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 04/18] dmaengine, async_tx: support alignment checks
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 03/18] dmaengine: cleanup unused transaction types
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: mdadm and TLER (Time Limited Error Recovery)
  • From: Simon Jackson <sjackson@xxxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: "Majed B." <majedb@xxxxxxxxx>
• ext3 crash with tune2fs and MD RAID10 device.
  • From: David Martínez Moreno <ender@xxxxxxxxxx>
• Re: [PATCH v2 7/9] md/raid6: asynchronous handle_stripe6
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Alex Butcher <linraid@xxxxxxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: Alex Butcher <linraid@xxxxxxxxxxxxxx>
• Re: Re-map disk sectors in userspace when rewriting after read errors
  • From: berk walker <berk@xxxxxxxxx>
• Re-map disk sectors in userspace when rewriting after read errors
  • From: Matthias Urlichs <matthias@xxxxxxxxxx>
• Re: [PATCH v2 2/9] md/raid6: asynchronous raid6 operations
  • From: Neil Brown <neilb@xxxxxxx>
• Re: [PATCH v2 7/9] md/raid6: asynchronous handle_stripe6
  • From: Neil Brown <neilb@xxxxxxx>
• RE: [PATCH 29/29] ioat2, 3: cacheline align software descriptor allocations
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 28/29] dmaengine: kill tx_list
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 26/29] ioat: implement a private tx_list
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 22/29] net_dma: poll for a descriptor after allocation failure
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 21/29] ioat2,3: dynamically resize descriptor ring
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 20/29] ioat: switch watchdog and reset handler from workqueue to timer
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• RE: [PATCH 19/29] ioat1: trim ioat_dma_desc_sw
  • From: "Sosnowski, Maciej" <maciej.sosnowski@xxxxxxxxx>
• Re: RAID mirror, resyncing from bad disk
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: RAID mirror, resyncing from bad disk
  • From: Ronny Adsetts <ronny.adsetts@xxxxxxxxxxxxxxxxxxx>
• Re: RAID mirror, resyncing from bad disk
  • From: Ronny Adsetts <ronny.adsetts@xxxxxxxxxxxxxxxxxxx>
• Re: RAID mirror, resyncing from bad disk
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: RAID mirror, resyncing from bad disk
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• RAID mirror, resyncing from bad disk
  • From: Ronny Adsetts <ronny.adsetts@xxxxxxxxxxxxxxxxxxx>
• Re: What's in async_tx.git/next for 2.6.32?
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: What's in async_tx.git/next for 2.6.32?
  • From: Atsushi Nemoto <anemo@xxxxxxxxxxxxx>
• Assemble array: failed to create bitmap (-5)
  • From: Siegfried Thoma <thoma.siegfried@xxxxxxxx>
• Re: Raid 5 Read performance
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Array Power Management
  • From: Ryan Wagoner <rswagoner@xxxxxxxxx>
• Re: sync_action missing in action in linux-2.6.12 ?
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: sync_action missing in action in linux-2.6.12 ?
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• sync_action missing in action in linux-2.6.12 ?
  • From: Louis-Michel Gelinas <coradiant.kernel@xxxxxxxxx>
• Re: Raid 5 Read performance
  • From: "Majed B." <majedb@xxxxxxxxx>
• Raid 5 Read performance
  • From: Koti <satha_koti@xxxxxxxxxxx>
• Re: Port Multipliers
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• Re: Port Multipliers
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Port Multipliers
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Port Multipliers
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: Port Multipliers
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Port Multipliers
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: Port Multipliers
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Port Multipliers
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• Re: Array Power Management
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: Port Multipliers
  • From: "Majed B." <majedb@xxxxxxxxx>
• Port Multipliers
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: mdadm and TLER (Time Limited Error Recovery)
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: mdadm and TLER (Time Limited Error Recovery)
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: "Majed B." <majedb@xxxxxxxxx>
• RE: mdadm and TLER (Time Limited Error Recovery)
  • From: Simon Jackson <sjackson@xxxxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: Raid5 Read Perf drop in 2.6.27
  • From: "Majed B." <majedb@xxxxxxxxx>
• Raid5 Read Perf drop in 2.6.27
  • From: Linux Raid Study <linuxraid.study@xxxxxxxxx>
• Re: Software Raid 5 work on ROOT ?
  • From: Nagilum <nagilum@xxxxxxxxxxx>
• Re: mdadm and TLER (Time Limited Error Recovery)
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: mdadm and TLER (Time Limited Error Recovery)
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Adaptec 1430SA
  • From: "Majed B." <majedb@xxxxxxxxx>
• RE: mdadm and TLER (Time Limited Error Recovery)
  • From: Simon Jackson <sjackson@xxxxxxxxxxx>
• Re: Adaptec 1430SA
  • From: Jon Hardcastle <jd_hardcastle@xxxxxxxxx>
• Re: Adaptec 1430SA
  • From: Jon Hardcastle <jd_hardcastle@xxxxxxxxx>
• Re: mdadm and TLER (Time Limited Error Recovery)
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Re: Adaptec 1430SA
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: Adaptec 1430SA
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Adaptec 1430SA
  • From: Michał Przyłuski <mikylie@xxxxxxxxx>
• Re: Adaptec 1430SA
  • From: Kristleifur Daðason <kristleifur@xxxxxxxxx>
• Re: mdadm --wait doesn't (part II) [was: Re: question about bitmaps and dirty percentile]
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Adaptec 1430SA
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: mdadm /dev/md0 --detail returns nothing / no LUKS partition
  • From: "Johannes 'fish' Ziemke" <fish@xxxxxxxxxxxxx>
• Re: mdadm /dev/md0 --detail returns nothing / no LUKS partition
  • From: "NeilBrown" <neilb@xxxxxxx>
• mdadm /dev/md0 --detail returns nothing / no LUKS partition
  • From: "Johannes 'fish' Ziemke" <fish@xxxxxxxxxxxxx>
• Re: mdadm and TLER (Time Limited Error Recovery)
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: mdadm and TLER (Time Limited Error Recovery)
  • From: Iustin Pop <iusty@xxxxxxxxx>
• mdadm --wait doesn't (part II) [was: Re: question about bitmaps and dirty percentile]
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Adaptec 1430SA
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Adaptec 1430SA
  • From: Ryan Wagoner <rswagoner@xxxxxxxxx>
• Re: Adaptec 1430SA
  • From: Jon Hardcastle <jd_hardcastle@xxxxxxxxx>
• Re: mdadm and TLER (Time Limited Error Recovery)
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Adaptec 1430SA
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Adaptec 1430SA
  • From: "Majed B." <majedb@xxxxxxxxx>
• Adaptec 1430SA
  • From: Jon Hardcastle <jd_hardcastle@xxxxxxxxx>
• Can md/mdadm deal with non-standard size of internal bitmap?
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: Software Raid 5 work on ROOT ?
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Software Raid 5 work on ROOT ?
  • From: Nagilum <nagilum@xxxxxxxxxxx>
• mdadm and TLER (Time Limited Error Recovery)
  • From: Tim Rutter <timrutter@xxxxxxxxx>
• Re: 2 Disks Jumped Out While Reshaping RAID5
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Array Power Management
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: Array Power Management
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: Array Power Management
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: Array Power Management
  • From: Tapani Tarvainen <raid@xxxxxxxxxxxxxxxxxx>
• Re: Software, Raid 5, Different Size Drives.
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: Software, Raid 5, Different Size Drives.
  • From: Jon Hardcastle <jd_hardcastle@xxxxxxxxx>
• Re: Array Power Management
  • From: Jon Hardcastle <jd_hardcastle@xxxxxxxxx>
• Re: Array Power Management
  • From: "Majed B." <majedb@xxxxxxxxx>
• Array Power Management
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: 2 Disks Jumped Out While Reshaping RAID5
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: 2 Disks Jumped Out While Reshaping RAID5
  • From: "NeilBrown" <neilb@xxxxxxx>
• Re: 2 Disks Jumped Out While Reshaping RAID5
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: 2 Disks Jumped Out While Reshaping RAID5
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: 2 Disks Jumped Out While Reshaping RAID5
  • From: Neil Brown <neilb@xxxxxxx>
• Re: 2 Disks Jumped Out While Reshaping RAID5
  • From: "Majed B." <majedb@xxxxxxxxx>
• Re: [PATCH 10/18] ioat3: xor support
  • From: Pavel Machek <pavel@xxxxxx>
• Re: 2 Disks Jumped Out While Reshaping RAID5
  • From: "NeilBrown" <neilb@xxxxxxx>
• 2 Disks Jumped Out While Reshaping RAID5
  • From: "Majed B." <majedb@xxxxxxxxx>
• What's in async_tx.git/next for 2.6.32?
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Western Digital RE3: Raid Failure
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: Western Digital RE3: Raid Failure
  • From: Alex Butcher <linraid@xxxxxxxxxxxxxx>
• Re: Western Digital RE3: Raid Failure
  • From: Thomas Fjellstrom <tfjellstrom@xxxxxxx>
• Re: Advice on reassembling after hard crash
  • From: "NeilBrown" <neilb@xxxxxxx>
• Advice on reassembling after hard crash
  • From: Erich Newell <erich.newell@xxxxxxxxx>
• Re: [PATCH 24/29] fsldma: implement a private tx_list
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Software Raid 5 work on ROOT ?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Software Raid 5 work on ROOT ?
  • From: Alex Butcher <linraid@xxxxxxxxxxxxxx>
• Software Raid 5 work on ROOT ?
  • From: lfmarante@xxxxxxx
• [PATCH 08/18] ioat: add 'ioat' sysfs attributes
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 03/18] dmaengine: cleanup unused transaction types
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 15/18] ioat3: ioat3.2 pci ids for Jasper Forest
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 16/18] ioat3: segregate raid engines
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 06/18] ioat3: hardware version 3.2 register / descriptor definitions
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 04/18] dmaengine, async_tx: support alignment checks
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 07/18] ioat3: split ioat3 support to its own file, add memset
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 10/18] ioat3: xor support
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 17/18] Add MODULE_DEVICE_TABLE() so ioatdma module is autoloaded
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 12/18] ioat3: pq support
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 18/18] I/OAT: Convert to PCI_VDEVICE()
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 11/18] ioat3: xor self test
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 14/18] ioat3: interrupt descriptor support
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 13/18] ioat3: support xor via pq descriptors
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 09/18] ioat3: enable dca for completion writes
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 05/18] ioat2+: add fence support
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 02/18] dmaengine, async_tx: add a "no channel switch" allocator
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 01/18] dmaengine: add fence support
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 00/18] ioatdma: raid5/raid6 offload support
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 00/29] ioatdma: towards raid support
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 01/29] ioat: move to drivers/dma/ioat/
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 02/29] ioat: move definitions to dma.h
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 03/29] ioat: convert ioat_probe to pcim/devm
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 04/29] ioat: cleanup some long deref chains and 80 column collisions
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 06/29] ioat: split ioat_dma_probe into core/version-specific routines
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 07/29] ioat: fix type mismatch for ->dmacount
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 05/29] ioat: kill function prototype ifdef guards
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 15/29] ioat: cleanup completion status reads
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 08/29] ioat: define descriptor control bit-field
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 14/29] ioat: add some dev_dbg() calls
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 17/29] ioat: preserve chanctrl bits when re-arming interrupts
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 19/29] ioat1: trim ioat_dma_desc_sw
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 13/29] ioat1: kill unused unmap parameters
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 18/29] ioat: ___devinit annotate the initialization paths
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 22/29] net_dma: poll for a descriptor after allocation failure
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 23/29] dw_dmac: implement a private tx_list
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 25/29] iop-adma: implement a private tx_list
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 20/29] ioat: switch watchdog and reset handler from workqueue to timer
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 21/29] ioat2,3: dynamically resize descriptor ring
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 24/29] fsldma: implement a private tx_list
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 26/29] ioat: implement a private tx_list
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 28/29] dmaengine: kill tx_list
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 29/29] ioat2, 3: cacheline align software descriptor allocations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 27/29] mv_xor: implement a private tx_list
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 16/29] ioat: ignore reserved bits for chancnt and xfercap
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 12/29] ioat2,3: convert to a true ring buffer
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 11/29] ioat: prepare the code for ioat[12]_dma_chan split
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 09/29] ioat1: move descriptor allocation from submit to prep
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 10/29] ioat: fix self test interrupts
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: NEWBIE Q: expanding hardware RAID
  • From: Ryan Wagoner <rswagoner@xxxxxxxxx>
• Re: Converting ext3 to RAID1 ...
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Western Digital RE3: Raid Failure
  • From: Zdenek Kaspar <zkaspar82@xxxxxxxxx>
• Re: Western Digital RE3: Raid Failure
  • From: Alex Butcher <linraid@xxxxxxxxxxxxxx>
• Re: Western Digital RE3: Raid Failure
  • From: Gabor Gombas <gombasg@xxxxxxxxx>
• Re: Western Digital RE3: Raid Failure
  • From: "MOgWai46[Saurceful of Secrets]" <street41@xxxxxxxxx>
• Re: Unbalanced reads of RAID10
  • From: Keld Jørn Simonsen <keld@xxxxxxxx>
• [no subject]
  • From: "me at tmr.com" <tmrbill@xxxxxxx>
• [no subject]
  • From: "me at tmr.com" <tmrbill@xxxxxxx>
• Re: NEWBIE Q: expanding hardware RAID
  • From: Ryan Wagoner <rswagoner@xxxxxxxxx>
• Re: NEWBIE Q: expanding hardware RAID
  • From: Ryan Wagoner <rswagoner@xxxxxxxxx>
• Re: Converting ext3 to RAID1 ...
  • From: Clinton Lee Taylor <clintonlee.taylor@xxxxxxxxx>
• Re: NEWBIE Q: expanding hardware RAID
  • From: Anil Raj <anil.calvin@xxxxxxxxx>
• Re: Write intent bitmaps.
  • From: Ryan Wagoner <rswagoner@xxxxxxxxx>
• Re: Write intent bitmaps.
  • From: Paul Clements <paul.clements@xxxxxxxxxxxx>
• Re: Converting ext3 to RAID1 ...
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Unbalanced reads of RAID10
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Write intent bitmaps.
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: NEWBIE Q: expanding hardware RAID
  • From: Ryan Wagoner <rswagoner@xxxxxxxxx>
• Re: NEWBIE Q: expanding hardware RAID
  • From: Anil Raj <anil.calvin@xxxxxxxxx>
• Re: NEWBIE Q: expanding hardware RAID
  • From: Ryan Wagoner <rswagoner@xxxxxxxxx>
• Re: NEWBIE Q: expanding hardware RAID
  • From: Alex Butcher <linraid@xxxxxxxxxxxxxx>
• Re: NEWBIE Q: expanding hardware RAID
  • From: David Lethe <david@xxxxxxxxxxxx>
• Re: [PATCH v2 0/9] Asynchronous raid6 acceleration (part 3 of 3)
  • From: kwick <kwick@xxxxxxxxxxxxx>
• NEWBIE Q: expanding hardware RAID
  • From: Anil Raj <anil.calvin@xxxxxxxxx>
• Re: Western Digital RE3: Raid Failure
  • From: Zdenek Kaspar <zkaspar82@xxxxxxxxx>
• Re: Western Digital RE3: Raid Failure
  • From: Richard Scobie <richard@xxxxxxxxxxx>
• [PATCH v2 9/9] md/raid456: distribute raid processing over multiple cores
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 8/9] md/raid6: remove synchronous infrastructure
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 7/9] md/raid6: asynchronous handle_stripe6
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 6/9] md/raid6: asynchronous handle_parity_check6
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 5/9] md/raid6: asynchronous handle_stripe_dirtying6
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 4/9] md/raid6: asynchronous handle_stripe_fill6
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 3/9] md/raid5, 6: common schedule_reconstruction for raid5/6
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 2/9] md/raid6: asynchronous raid6 operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 1/9] md/raid5: factor out mark_uptodate from ops_complete_compute5
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 0/9] Asynchronous raid6 acceleration (part 3 of 3)
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 4/4] iop-adma: P+Q self test
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 3/4] iop-adma: P+Q support for iop13xx adma engines
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 2/4] iop-adma: fix lockdep false positive
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 1/4] iop-adma: cleanup iop_adma_run_tx_complete_actions
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v2 0/4] Asynchronous raid6 acceleration (part 2 of 3)
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Western Digital RE3: Raid Failure
  • From: "MOgWai46[Saurceful of Secrets]" <street41@xxxxxxxxx>
• [PATCH v3 05/14] md/raid6: release spare page at ->stop()
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v3 03/14] async_tx: structify submission arguments, add scribble
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>