Linux RAID Storage Date Index

• Thread Index

• Re: dm-raid45?
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• Re: dm-raid45?
  • From: Tom Pfeifer <tpfeife1@xxxxxxxxx>
• Re: [BUG,PATCH] raid1 behind write ordering (barrier) protection
  • From: Brett Russ <brett@xxxxxxxxxxxxxxxxxx>
• Re: [BUG,PATCH] raid1 behind write ordering (barrier) protection
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [BUG,PATCH] raid1 behind write ordering (barrier) protection
  • From: Brett Russ <brett@xxxxxxxxxxxxxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Thanks Neil
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: Raid10 multi core scaling
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Creating new raid5 or 6 with --assume-clean
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Raid10 multi core scaling
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Raid10 multi core scaling
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm No md superblock detected
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [BUG]NULL Pointer dereference in rdev_set_badblocks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md raid5 performace 6x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• md raid5 performace 6x SSD RAID5
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Creating new raid5 or 6 with --assume-clean
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: md raid5 random performace 6x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Richard Scobie <r.scobie@xxxxxxxxxxxx>
• md raid5 random performace 6x SSD RAID5
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: 答复：答复：答复：md raid5 random performace 6x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Thanks Neil
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Thanks Neil
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Thanks Neil
  • From: Digimer <lists@xxxxxxxxxx>
• Thanks Neil
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Growing array, duplicating data, shrinking array questions.
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• 答复：答复：答复：md raid5 random performace 6x SSD RAID5
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• mdadm No md superblock detected
  • From: Teitur Ingi Sigurdsson <teitso@xxxxxxxxx>
• Re: /proc/mdstat status documentation and md: export_rdev
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: cgroups-blkio CFQ scheduling does not work well in a RAID5 configuration.
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• cgroups-blkio CFQ scheduling does not work well in a RAID5 configuration.
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• Re: 答复：答复：md raid5 performace 6x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: 答复：答复：md raid5 performace 6x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: /proc/mdstat status documentation and md: export_rdev
  • From: Can Jeuleers <can.jeuleers@xxxxxxxxx>
• Re: /proc/mdstat status documentation and md: export_rdev
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: [BUG]NULL Pointer dereference in rdev_set_badblocks
  • From: Jack Wang <jinpu.wang@xxxxxxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Jimmy Thrasibule <thrasibule.jimmy@xxxxxxxxx>
• 答复：答复：md raid5 performace 6x SSD RAID5
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• 答复：答复：md raid5 performace 6x SSD RAID5
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: 答复：md raid5 performace 6x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: 答复：md raid5 performace 6x SSD RAID5
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: 答复：md raid5 performace 6x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PATCH -next] bcache: fix sparse non static symbol warning
  • From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• 答复：md raid5 performace 6x SSD RAID5
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• md raid5 performace 6x SSD RAID5
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Raid10 multi core scaling
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: ronnie sahlberg <ronniesahlberg@xxxxxxxxx>
• Re: dm-raid45?
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: joystick <joystick@xxxxxxxxxxxxx>
• dm-raid45?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: [PATCH] Revert "raid5: make release_stripe lockless" because it causes test regression
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Raid10 multi core scaling
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Raid10 multi core scaling
  • From: Pedro Teixeira <finas@xxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• RAID Performance - 5x SSD RAID5
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Slow AVX XOR reported
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Pasi Kärkkäinen <pasik@xxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Jimmy Thrasibule <thrasibule.jimmy@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Stuck reshape
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• Re: md/raid5: Use conf->device_lock protect changing of multi-thread resources.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Revert "raid5: make release_stripe lockless" because it causes test regression
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• Re: Stuck reshape
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 0/1] Recent breakage of DM RAID
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Triple parity and beyond
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Stuck reshape
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] Revert "raid5: make release_stripe lockless" because it causes test regression
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• [PATCH] Revert "raid5: make release_stripe lockless" because it causes test regression
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: md/raid5: Use conf->device_lock protect changing of multi-thread resources.
  • From: Ben Hutchings <bhutchings@xxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Taylor <davidt@xxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• ARC-1120 and MD very sloooow
  • From: Jimmy Thrasibule <thrasibule.jimmy@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• mdadm No md superblock detected
  • From: Teitur Ingi Sigurdsson <teitso@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• raid1 behind write ordering (barrier) protection
  • From: Brett Russ <brett@xxxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Growing array, duplicating data, shrinking array questions.
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Goffredo Baroncelli <kreijack@xxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Is there a tool to examine raw metadata?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: unused space before data offset mismatch
  • From: NeilBrown <neilb@xxxxxxx>
• Re: unused space before data offset mismatch
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: James Plank <plank@xxxxxxxxxx>
• unused space before data offset mismatch
  • From: kustep <kustep@xxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Is there a tool to examine raw metadata?
  • From: Veedar Hokstadt <veedar@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: James Plank <plank@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• Re: dmaengine 3.13 v2
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: NeilBrown <neilb@xxxxxxx>
• [PULL REQUEST] md updates for 3.13
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Triple parity and beyond
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Is my drive dying ?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Is my drive dying ?
  • From: Guillaume Betous <guillaume.betous@xxxxxxxxx>
• Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Filesystem writes on RAID5 too slow
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• mdadm: "reshape: not enough stripes. Needed 65536"
  • From: "Steven Rose [DATACOM]" <Steven.Rose@xxxxxxxxxxxxx>
• Re: dmaengine 3.13 v2
  • From: Jon Mason <jon.mason@xxxxxxxxx>
• Re: dmaengine 3.13 v2
  • From: Vinod Koul <vinod.koul@xxxxxxxxx>
• multiple device failure of mdadm array
  • From: kustep <kustep@xxxxxx>
• Re: dmaengine 3.13 v2
  • From: Vinod Koul <vinod.koul@xxxxxxxxx>
• dmaengine 3.13 v2
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: mdadm --fail requires writeable drive.
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: [dm-devel] [PATCH -next] dm cache policy mq:: use list_del_init instead of list_del/INIT_LIST_HEAD
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH -next] dm cache policy mq:: use list_del_init instead of list_del/INIT_LIST_HEAD
  • From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
• /proc/mdstat status documentation and md: export_rdev
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: mdadm --fail requires writeable drive.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: mdadm --fail requires writeable drive.
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• RE: 3.12: raid-1 mismatch_cnt question
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: joystick <joystick@xxxxxxxxxxxxx>
• RE: 3.12: raid-1 mismatch_cnt question
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: NeilBrown <neilb@xxxxxxx>
• kernel panic with bitmap_startwrite
  • From: 4363@xxxxxxx
• Re: mdadm --fail requires writeable drive.
  • From: NeilBrown <neilb@xxxxxxx>
• RE: 3.12: raid-1 mismatch_cnt question
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/4] ioatdma: 16-source operation fixes
  • From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
• [PATCH 4/4] raid6test: add new corner case for ioatdma driver
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 3/4] ioatdma: clean up sed pool kmem_cache
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2/4] ioatdma: fix selection of 16 vs 8 source path
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 1/4] ioatdma: fix sed pool selection
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 0/4] ioatdma: 16-source operation fixes
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• mdadm --fail requires writeable drive.
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: [PATCH 0/2] Fix oops when changed group_thread_cnt
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: recommending RAID6 over RAID5 when doing mdadm --create
  • From: Giovanni Tessore <giotex@xxxxxxxxxx>
• Re: [PATCH 2/2] raid5: Using conf->device_lock protect multi-thread resouce when changed.
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 1/2] raid5: Before freeing old multi-thread worker,it should flush them.
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: recommending RAID6 over RAID5 when doing mdadm --create
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• [PATCH 1/2] raid5: Before freeing old multi-thread worker,it should flush them.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 2/2] raid5: Using conf->device_lock protect multi-thread resouce when changed.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 0/2] Fix oops when changed group_thread_cnt
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• RE: 3.12: raid-1 mismatch_cnt question
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: mdadm: sending ioctl [1261|800c0910] to a partition!
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: recommending RAID6 over RAID5 when doing mdadm --create
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: joystick <joystick@xxxxxxxxxxxxx>
• mdadm: sending ioctl [1261|800c0910] to a partition!
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: recommending RAID6 over RAID5 when doing mdadm --create
  • From: Tommy Apel <tommyapeldk@xxxxxxxxx>
• RE: 3.12: raid-1 mismatch_cnt question
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: recommending RAID6 over RAID5 when doing mdadm --create
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: recommending RAID6 over RAID5 when doing mdadm --create
  • From: Tommy Apel <tommyapeldk@xxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• recommending RAID6 over RAID5 when doing mdadm --create
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• stoppind md from kicking out "bad' drives
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Running check and e2fsck simultaneously
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: ISW fakeraid: fail to add back a disk previously removed
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• RE: 3.12: raid-1 mismatch_cnt question
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Seagate black armour recovery
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: ISW fakeraid: fail to add back a disk previously removed
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: ISW fakeraid: fail to add back a disk previously removed
  • From: NeilBrown <neilb@xxxxxxx>
• RE: ISW fakeraid: fail to add back a disk previously removed
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: ISW fakeraid: fail to add back a disk previously removed
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: [PATCH] raid5: Using slow_path to release stripe when mmdev->threand is null
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] raid0: Set discard_granularity to correct value after reshape.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] raid5: Using slow_path to release stripe when mmdev->threand is null
  • From: majianpeng <majianpeng@xxxxxxxxx>
• RE: ISW fakeraid: fail to add back a disk previously removed
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: ISW fakeraid: fail to add back a disk previously removed
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: Timeout question
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: Seagate black armour recovery
  • From: Kevin Wilson <kevin@xxxxxxxxxxxxxxxxxxxxxxx>
• RE: [PATCH] raid0: Set discard_granularity to correct value after reshape.
  • From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
• Disk failure questions
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [RFC] md raid resync counter
  • From: Jack Wang <xjtuwjp@xxxxxxxxx>
• mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: [RFC] md raid resync counter
  • From: NeilBrown <neilb@xxxxxxx>
• "Found some drive for an array that is already active"
  • From: Arnold Schulz <arnysch@xxxxxxx>
• Re: Timeout question
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Timeout question
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Seagate black armour recovery
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Timeout question
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• high read throughput storage server, take 2
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Seagate black armour recovery
  • From: Kevin Wilson <kevin@xxxxxxxxxxxxxxxxxxxxxxx>
• More distinct events for mdadm - check vs. error case
  • From: Karsten Hohmeier <karsten.hohmeier@xxxxxxxxxxxxx>
• 3.12: raid-1 mismatch_cnt question
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: [RFC] md raid resync counter
  • From: Jack Wang <xjtuwjp@xxxxxxxxx>
• Re: [RFC] md raid resync counter
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid5 raid5d multi-thread
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [RFC] md raid resync counter
  • From: Jack Wang <xjtuwjp@xxxxxxxxx>
• Re: [PATCH 3/3] md/raid5: For stripe with R5_ReadNoMerge, we replace REQ_FLUSH with REQ_NOMERGE.
  • From: axboe <axboe@xxxxxxxxx>
• Re: Re: [PATCH 3/3] md/raid5: For stripe with R5_ReadNoMerge, we replace REQ_FLUSH with REQ_NOMERGE.
  • From: kedacomkernel <kedacomkernel@xxxxxxxxx>
• Re: Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: [PATCH 3/3] md/raid5: For stripe with R5_ReadNoMerge, we replace REQ_FLUSH with REQ_NOMERGE.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: drivers: md: include "linux/vmalloc.h" in "dm-cache-policy-hints.c"
  • From: Chen Gang <gang.chen@xxxxxxxxxxx>
• Re: [PATCH] raid0: Set discard_granularity to correct value after reshape.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: drivers: md: include "linux/vmalloc.h" in "dm-cache-policy-hints.c"
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] raid0: Set discard_granularity to correct value after reshape.
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: [PATCH] UAPI: include <asm/byteorder.h> in linux/raid/md_p.h
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] drivers: md: include "linux/vmalloc.h" in "dm-cache-policy-hints.c"
  • From: Chen Gang <gang.chen@xxxxxxxxxxx>
• Re: [PATCH] UAPI: include <asm/byteorder.h> in linux/raid/md_p.h
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 0/3] handle some bugs for REQ_NOMERGE.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 2/3] block: Check bio can merge before call attempt_plug_merge.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 1/3] block: Add REQ_NOMERGE into REQ_COMMON_MASK
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 3/3] md/raid5: For stripe with R5_ReadNoMerge, we replace REQ_FLUSH with REQ_NOMERGE.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: [PATCH] mdadm.8.in
  • From: John Schmidt <johnschmidt4@xxxxxxxxx>
• Re: [PATCH] mdadm.8.in
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] mdadm.8.in
  • From: Levente Kurusa <levex@xxxxxxxxx>
• [PATCH] mdadm.8.in
  • From: John Schmidt <johnschmidt4@xxxxxxxxx>
• Re: aac_write: aac_fib_send failed with status: -12
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• [PATCH] UAPI: include <asm/byteorder.h> in linux/raid/md_p.h
  • From: Aurelien Jarno <aurelien@xxxxxxxxxxx>
• Re: Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: ISW fakeraid: fail to add back a disk previously removed
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: changing parameters of a running array?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: changing parameters of a running array?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: assembling array after disk failure
  • From: Dan Knight <dknight1989@xxxxxxxxxx>
• Re: assembling array after disk failure
  • From: Phil Turmel <philip@xxxxxxxxxx>
• assembling array after disk failure
  • From: Dan Knight <dknight1989@xxxxxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• aac_write: aac_fib_send failed with status: -12
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• Re: re-assembling arrays after severe controller hardware issues...
  • From: Phil Turmel <philip@xxxxxxxxxx>
• re-assembling arrays after severe controller hardware issues...
  • From: Maarten <maarten@xxxxxxxxxxxx>
• Re: Enable SCTERC in the kernel?
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Help raid10 recovery from 2 disks removed
  • From: Dag Nygren <dag@xxxxxxxxxx>
• Re: Enable SCTERC in the kernel?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Help raid10 recovery from 2 disks removed
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Help raid10 recovery from 2 disks removed
  • From: Phil Turmel <philip@xxxxxxxxxx>
• RE: Help raid10 recovery from 2 disks removed
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: raid5 trim OOPS / use after free?
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Enable SCTERC in the kernel?
  • From: Dag Nygren <dag@xxxxxxxxxx>
• Re: Enable SCTERC in the kernel?
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Enable SCTERC in the kernel?
  • From: Dag Nygren <dag@xxxxxxxxxx>
• Re: Enable SCTERC in the kernel?
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• RE: Help raid10 recovery from 2 disks removed
  • From: <yuji_touya@xxxxxxxxxxxxxxxxxxxx>
• Re: Enable SCTERC in the kernel?
  • From: NeilBrown <neilb@xxxxxxx>
• RE: Help raid10 recovery from 2 disks removed
  • From: <yuji_touya@xxxxxxxxxxxxxxxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: changing parameters of a running array?
  • From: Lars Täuber <taeuber@xxxxxxx>
• Enable SCTERC in the kernel?
  • From: Dag Nygren <dag@xxxxxxxxxx>
• Re: Help raid10 recovery from 2 disks removed
  • From: Dag Nygren <dag@xxxxxxxxxx>
• Re: Help raid10 recovery from 2 disks removed
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Can a running MD array name change?
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• changing parameters of a running array?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Can a running MD array name change?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help raid10 recovery from 2 disks removed
  • From: Dag Nygren <dag@xxxxxxxxxx>
• Can a running MD array name change?
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: C600 raid
  • From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
• Re: C600 raid
  • From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
• RE: Help raid10 recovery from 2 disks removed
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Help raid10 recovery from 2 disks removed
  • From: Phil Turmel <philip@xxxxxxxxxx>
• RE: Help raid10 recovery from 2 disks removed
  • From: <yuji_touya@xxxxxxxxxxxxxxxxxxxx>
• Re: raid1 repair does not repair errors?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Help raid10 recovery from 2 disks removed
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Help raid10 recovery from 2 disks removed
  • From: <yuji_touya@xxxxxxxxxxxxxxxxxxxx>
• C600 raid
  • From: Marcus Sorensen <shadowsor@xxxxxxxxx>
• Re: [patch 1/2]raid5: set bio bi_vcnt 0 for discard request
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: Drew <drew.kay@xxxxxxxxx>
• ISW fakeraid: fail to add back a disk previously removed
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: [patch 1/2]raid5: set bio bi_vcnt 0 for discard request
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: [PATCH 08/24] md: Convert use of typedef ctl_table to struct ctl_table
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 00/24] treewide: Convert use of typedef ctl_table to struct ctl_table
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH 00/24] treewide: Convert use of typedef ctl_table to struct ctl_table
  • From: David Daney <ddaney.cavm@xxxxxxxxx>
• [PATCH 00/24] treewide: Convert use of typedef ctl_table to struct ctl_table
  • From: Joe Perches <joe@xxxxxxxxxxx>
• [PATCH 08/24] md: Convert use of typedef ctl_table to struct ctl_table
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [Question] how to proceed after bad raid5 reshape
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• [Question] how to proceed after bad raid5 reshape
  • From: Dan Knight <dknight1989@xxxxxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: keld@xxxxxxxxxx
• Re: raid5 trim OOPS / use after free?
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: raid1 repair does not repair errors?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: Steve Bergman <sbergman27@xxxxxxxxx>
• Re: [PATCH] md: avoid deadlock when md_set_badblocks.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Advice recovering from interrupted grow on RAID5 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Advice recovering from interrupted grow on RAID5 array
  • From: John Yates <jyates65@xxxxxxxxx>
• RE: raid5 trim OOPS / use after free?
  • From: "DeGon, Michael J" <michael.j.degon@xxxxxxxxx>
• Using array without initializing
  • From: Hans-Joachim Baader <hjb@xxxxxxxxxxxx>
• [PATCH] md: avoid deadlock when md_set_badblocks.
  • From: ycbzzjlby@xxxxxxxxx
• Re: Advice recovering from interrupted grow on RAID5 array
  • From: John Yates <jyates65@xxxxxxxxx>
• raid1 repair does not repair errors?
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: raid5 trim OOPS / use after free?
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: failed raid5
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Advice recovering from interrupted grow on RAID5 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RFC: incremental container assembly when sequence numbers don't match
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH next] md: bcache: Add missing newlines to logging messages, & misc neatening
  • From: Joe Perches <joe@xxxxxxxxxxx>
• failed raid5
  • From: <i.mikic@xxxxxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Linux MD? Or an H710p?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Linux MD? Or an H710p?
  • From: Steve Bergman <sbergman27@xxxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: raid5 trim OOPS / use after free?
  • From: Shaohua Li <ShLi@xxxxxxxxxxxx>
• [patch 2/2]raid5: avoid find discard stripe
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 1/2]raid5: set bio bi_vcnt 0 for discard request
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: raid5 trim OOPS / use after free?
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: raid5 trim OOPS / use after free?
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Problem diagnosing rebuilding raid5 array
  • From: peter@xxxxxxxxxxxx
• Re: raid5 trim OOPS / use after free?
  • From: Shaohua Li <ShLi@xxxxxxxxxxxx>
• Re: raid5 trim OOPS / use after free?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• raid5 trim OOPS / use after free?
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: NeilBrown <neilb@xxxxxxx>
• ANNOUNCE: Einarc 2.0 - hardware RAID management frontend CLI/API
  • From: Mikhail Yakshin <greycat.na.kor@xxxxxxxxx>
• Re: Advice recovering from interrupted grow on RAID5 array
  • From: John Yates <jyates65@xxxxxxxxx>
• Re: Problem diagnosing rebuilding raid5 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problem diagnosing rebuilding raid5 array
  • From: peter@xxxxxxxxxxxx
• MD RAID5 / XFS filesystem creation error
  • From: m d <mikeintel8@xxxxxxxxx>
• Re: Advice recovering from interrupted grow on RAID5 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Advice recovering from interrupted grow on RAID5 array
  • From: John Yates <jyates65@xxxxxxxxx>
• RE: [PATCH] md: Fix skipping recovery for read-only arrays.
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: crypto/xor.c and lib/raid6 to improve raid5/6 performance?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problem diagnosing rebuilding raid5 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Advice recovering from interrupted grow on RAID5 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md: Fix skipping recovery for read-only arrays.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/1] consistent return types from byteswap macros
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] drivers: md: bcache: Fix wrong check on can_attach_cache
  • From: Felipe Pena <felipensp@xxxxxxxxx>
• Re: Removable mirror disks?
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: Problem diagnosing rebuilding raid5 array
  • From: Brian Candler <b.candler@xxxxxxxxx>
• Re: Problem diagnosing rebuilding raid5 array
  • From: peter@xxxxxxxxxxxx
• Re: Problem diagnosing rebuilding raid5 array
  • From: Brian Candler <b.candler@xxxxxxxxx>
• Re: Problem diagnosing rebuilding raid5 array
  • From: peter@xxxxxxxxxxxx
• Re: Problem diagnosing rebuilding raid5 array
  • From: peter@xxxxxxxxxxxx
• Re: Problem diagnosing rebuilding raid5 array
  • From: Brian Candler <b.candler@xxxxxxxxx>
• Re: Problem diagnosing rebuilding raid5 array
  • From: Brian Candler <b.candler@xxxxxxxxx>
• Re: Problem diagnosing rebuilding raid5 array
  • From: peter@xxxxxxxxxxxx
• Advice recovering from interrupted grow on RAID5 array
  • From: John Yates <jyates65@xxxxxxxxx>
• Re: Problem diagnosing rebuilding raid5 array
  • From: Brian Candler <b.candler@xxxxxxxxx>
• Problem diagnosing rebuilding raid5 array
  • From: peter@xxxxxxxxxxxx
• Re: Removable mirror disks?
  • From: Ethan Tira-Thompson <ethan@xxxxxxxxxxxxxxxxx>
• Re: Using mdadm instead of dmraid for BIOS-RAID root volume
  • From: Brian Candler <b.candler@xxxxxxxxx>
• Re: Using mdadm instead of dmraid for BIOS-RAID root volume
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Removable mirror disks?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Removable mirror disks?
  • From: Ethan Tira-Thompson <ethan@xxxxxxxxxxxxxxxxx>
• Re: 4 drive raid 5 array with 2 drives down
  • From: Eric Smith <eric.d.bald.smith@xxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• crypto/xor.c and lib/raid6 to improve raid5/6 performance?
  • From: xxiao <xiaoxianghua@xxxxxxxxx>
• Re: Using mdadm instead of dmraid for BIOS-RAID root volume
  • From: Brian Candler <b.candler@xxxxxxxxx>
• Re: Using mdadm instead of dmraid for BIOS-RAID root volume
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Best practice for setting up "ordinary" RAID
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Using mdadm instead of dmraid for BIOS-RAID root volume
  • From: Brian Candler <b.candler@xxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: Art -kwaak- van Breemen <ard@xxxxxxxxxxxxxxx>
• Re: Best practice for setting up "ordinary" RAID
  • From: Guillaume Betous <guillaume.betous@xxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Best practice for setting up "ordinary" RAID
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Best practice for setting up "ordinary" RAID
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Best practice for setting up "ordinary" RAID
  • From: Guillaume Betous <guillaume.betous@xxxxxxxxx>
• Re: Best practice for setting up "ordinary" RAID
  • From: Guillaume Betous <guillaume.betous@xxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Best practice for setting up "ordinary" RAID
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Best practice for setting up "ordinary" RAID
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Best practice for setting up "ordinary" RAID
  • From: Guillaume Betous <guillaume.betous@xxxxxxxxx>
• Re: Best practice for setting up "ordinary" RAID
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Best practice for setting up "ordinary" RAID
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Best practice for setting up "ordinary" RAID
  • From: Guillaume Betous <guillaume.betous@xxxxxxxxx>
• Re: Best practice for setting up "ordinary" RAID
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Best practice for setting up "ordinary" RAID
  • From: Guillaume Betous <guillaume.betous@xxxxxxxxx>
• Re: 4 drive raid 5 array with 2 drives down
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Can running array device name change? - Was: Detecting that an array has been stopped
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH] RAID5: Change kmem_cache name string of RAID 4/5/6 stripe cache
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• 4 drive raid 5 array with 2 drives down
  • From: Eric Smith <eric.d.bald.smith@xxxxxxxxx>
• Re: [PATCH] RAID5: Change kmem_cache name string of RAID 4/5/6 stripe cache
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Broken array, trying to assemble enough to copy data off
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Broken array, trying to assemble enough to copy data off
  • From: Digimer <lists@xxxxxxxxxx>
• Re: Broken array, trying to assemble enough to copy data off
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: Art -kwaak- van Breemen <ard@xxxxxxxxxxxxxxx>
• Re: Broken array, trying to assemble enough to copy data off
  • From: Digimer <lists@xxxxxxxxxx>
• mdadm monitor processes soaking up CPU
  • From: Brian Candler <brian@xxxxxxxxxxxxxx>
• Re: Broken array, trying to assemble enough to copy data off
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Using mdadm instead of dmraid for BIOS-RAID root volume
  • From: Brian Candler <b.candler@xxxxxxxxx>
• [PATCH 1/1] Be consistent in return types from byteswap macros
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/1] consistent return types from byteswap macros
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Broken array, trying to assemble enough to copy data off
  • From: Digimer <lists@xxxxxxxxxx>
• Broken array, trying to assemble enough to copy data off
  • From: Digimer <lists@xxxxxxxxxx>
• Re: SSD reliability; was: Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: Brian Candler <b.candler@xxxxxxxxx>
• Re: SSD reliability; was: Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• SSD reliability; was: Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Multiple SSDs - RAID-1, -10, or stacked? TRIM?
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: RAID 5 : recovery after failure
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: mdadm >= 3.0 - udev test rule
  • From: Hristo Chonov <hristochonov@xxxxxxxxx>
• Re: RAID 5 : recovery after failure
  • From: Guillaume Betous <guillaume.betous@xxxxxxxxx>
• Re: RAID 5 : recovery after failure
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: RAID 5 : recovery after failure
  • From: Guillaume Betous <guillaume.betous@xxxxxxxxx>
• Re: RAID 5 : recovery after failure
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: RAID 5 : recovery after failure
  • From: Guillaume Betous <guillaume.betous@xxxxxxxxx>
• Re: imsm identification problem. mdadm 3.3
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: RAID 5 : recovery after failure
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Problem with Dualboot on a LSI 9271-8i Controller
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: mdadm >= 3.0 - udev test rule
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Using mdadm instead of dmraid for BIOS-RAID root volume
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: imsm identification problem. mdadm 3.3
  • From: Martin Wilck <mwilck@xxxxxxxx>
• RAID 5 : recovery after failure
  • From: Guillaume Betous <guillaume.betous@xxxxxxxxx>
• Re: Using mdadm instead of dmraid for BIOS-RAID root volume
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Using mdadm instead of dmraid for BIOS-RAID root volume
  • From: Brian Candler <b.candler@xxxxxxxxx>
• Using mdadm instead of dmraid for BIOS-RAID root volume
  • From: Brian Candler <b.candler@xxxxxxxxx>
• mdadm >= 3.0 - udev test rule
  • From: Hristo Chonov <chonov@xxxxxxxxxxxxxxxxxxx>
• Re: Problem with Dualboot on a LSI 9271-8i Controller
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• Re: Problem with Dualboot on a LSI 9271-8i Controller
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PATCH] md: Fix skipping recovery for read-only arrays.
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Problem with Dualboot on a LSI 9271-8i Controller
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Help with data recovery - RAID6 with 2 failed drives and another with broken sectors
  • From: Michał Sawicz <michal@xxxxxxxxxx>
• Re: Help with data recovery - RAID6 with 2 failed drives and another with broken sectors
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Help with data recovery - RAID6 with 2 failed drives and another with broken sectors
  • From: Michał Sawicz <michal@xxxxxxxxxx>
• Re: Help with data recovery - RAID6 with 2 failed drives and another with broken sectors
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• imsm identification problem. mdadm 3.3
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: RAID10 scrub
  • From: Mark <grimm26@xxxxxxxxx>
• Re: [PATCH] Problems with RAID 4/5/6 and kmem_cache
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: RAID10 scrub
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: RAID10 scrub
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• RAID10 scrub
  • From: Mark Keisler <mark@xxxxxxxxxxx>
• Re: Help with data recovery - RAID6 with 2 failed drives and another with broken sectors
  • From: Michał Sawicz <michal@xxxxxxxxxx>
• Help with data recovery - RAID6 with 2 failed drives and another with broken sectors
  • From: Michał Sawicz <michal@xxxxxxxxxx>
• Re: Which filesystem for a hybris raid1?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Growing Array (More Devices) - new devices are slightly smaller than the existing drives, unable to shrink array
  • From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
• exclude assembling arrays with other homehost
  • From: Emilio Hodge <whiz@xxxxxxx>
• Re: Which filesystem for a hybris raid1?
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Which filesystem for a hybris raid1?
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Dave Gomboc <dave_gomboc@xxxxxxx>
• Re: Growing Array (More Devices) - new devices are slightly smaller than the existing drives, unable to shrink array
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Which filesystem for a hybris raid1?
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Growing Array (More Devices) - new devices are slightly smaller than the existing drives, unable to shrink array
  • From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
• Which filesystem for a hybris raid1?
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: [PATCH] Problems with RAID 4/5/6 and kmem_cache
  • From: Pekka Enberg <penberg@xxxxxxxxxx>
• Re: [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Detecting that an array has been stopped
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: Detecting that an array has been stopped
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• [PATCH] bcache: using for_each_clear_bit to simplify the code
  • From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
• Re: RFC: incremental container assembly when sequence numbers don't match
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 5/6] tests/10ddf-assemble-missing: new unit test
  • From: mwilck@xxxxxxxx
• [PATCH 6/6] tests/10ddf-incremental-wrong-order: new unit test
  • From: mwilck@xxxxxxxx
• [PATCH 4/6] tests/env-ddf-template: add helper function for checksums
  • From: mwilck@xxxxxxxx
• Re: [Recovery] RAID10 hdd failureS help requested
  • From: Karel Walters <karel.walters@xxxxxxxxx>
• Re: Best configuration for bcache/md cache or other cache using ssd
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Best configuration for bcache/md cache or other cache using ssd
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Best configuration for bcache/md cache or other cache using ssd
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Best configuration for bcache/md cache or other cache using ssd
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [Recovery] RAID10 hdd failureS help requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH 3/3] tests/10ddf-fail-readd-readonly: new unit test.
  • From: mwilck@xxxxxxxx
• [PATCH 2/3] tests/env-ddf-template: fix container name
  • From: mwilck@xxxxxxxx
• Detecting that an array has been stopped
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• [PATCH] Monitor: write meta data in readonly state, sometimes
  • From: mwilck@xxxxxxxx
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] *DO NOT APPLY* DDF: add_to_super_ddf: leave invalid secondary_lba untouched
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [Recovery] RAID10 hdd failureS help requested
  • From: Karel Walters <karel.walters@xxxxxxxxx>
• Re: [Recovery] RAID10 hdd failureS help requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 2/2] DDF: add_to_super_ddf: be careful with workspace_lba
  • From: mwilck@xxxxxxxx
• [PATCH 1/2] DDF: add_to_super_ddf: leave invalid secondary_lba untouched
  • From: mwilck@xxxxxxxx
• [PATCH 0/2] Fix mdadm --add for LSI fake RAID
  • From: mwilck@xxxxxxxx
• Re: [Recovery] RAID10 hdd failureS help requested
  • From: Karel Walters <karel.walters@xxxxxxxxx>
• Re: [Recovery] RAID10 hdd failureS help requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [Recovery] RAID10 hdd failureS help requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [Recovery] RAID10 hdd failureS help requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [Recovery] RAID10 hdd failureS help requested
  • From: Karel Walters <karel.walters@xxxxxxxxx>
• Re: Best configuration for bcache/md cache or other cache using ssd
  • From: "Bradley D. Thornton" <Bradley@xxxxxxxxxxxx>
• Strange RAID 1 rebuild problem
  • From: Andreas Heinlein <aheinlein@xxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Best configuration for bcache/md cache or other cache using ssd
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Best configuration for bcache/md cache or other cache using ssd
  • From: Tommy Apel <tommyapeldk@xxxxxxxxx>
• Re: Best configuration for bcache/md cache or other cache using ssd
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Dave Gomboc <dave_gomboc@xxxxxxx>
• Re: Best configuration for bcache/md cache or other cache using ssd
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: (Solved) Desperate: mdadm fails to assemble raid saying devices are busy.
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RFC: incremental container assembly when sequence numbers don't match
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 1/2] tests/10ddf-fail-readd: New DDF unit test
  • From: mwilck@xxxxxxxx
• [PATCH 2/2] tests/10ddf-fail-stop-readd: New DDF unit test
  • From: mwilck@xxxxxxxx
• Re: (Solved) Desperate: mdadm fails to assemble raid saying devices are busy.
  • From: Sachin Garg <sgarg.bugreporter@xxxxxxxxx>
• Re: mke2fs with discard option breaks RAID5 array
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• reboot during raid1 resync considered harmful?
  • From: Karl Kiniger <karl.kiniger@xxxxxxxxxx>
• Re: Array member "role numbers" in /proc/mdstat
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Array member "role numbers" in /proc/mdstat
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Array member "role numbers" in /proc/mdstat
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: Desperate: mdadm fails to assemble raid saying devices are busy.
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Desperate: mdadm fails to assemble raid saying devices are busy.
  • From: Sachin Garg <sgarg.bugreporter@xxxxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Dave Gomboc <dave_gomboc@xxxxxxx>
• Re: RAID5+spare volume gone - mdadm sees RAID1 only?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [BUG]NULL Pointer dereference in rdev_set_badblocks
  • From: Jack Wang <jinpu.wang@xxxxxxxxxxxxxxxx>
• Re: RFC: incremental container assembly when sequence numbers don't match
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID5+spare volume gone - mdadm sees RAID1 only?
  • From: P Agenbag <internet@xxxxxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Dave Gomboc <dave_gomboc@xxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Dave Gomboc <dave_gomboc@xxxxxxx>
• How to create a near-far array
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Dave Gomboc <dave_gomboc@xxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Dave Gomboc <dave_gomboc@xxxxxxx>