Linux RAID Storage Date Index

• Thread Index

• 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>
• 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: Phil Turmel <philip@xxxxxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Dave Gomboc <dave_gomboc@xxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Dave Gomboc <dave_gomboc@xxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID5+spare volume gone - mdadm sees RAID1 only?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• 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: Desperate: mdadm fails to assemble raid saying devices are busy.
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [PATCH] Problems with RAID 4/5/6 and kmem_cache
  • From: Christoph Lameter <cl@xxxxxxxxx>
• Re: Desperate: mdadm fails to assemble raid saying devices are busy.
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Desperate: mdadm fails to assemble raid saying devices are busy.
  • From: Sachin Garg <sgarg.bugreporter@xxxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Why hardware RAID controllers when talking about mdadm?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Testing /proc/mdstat parsing
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Why hardware RAID controllers when talking about mdadm?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• 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: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Question on DDF degraded array
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Question on DDF degraded array
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Anomaly with 2 x 840Pro SSDs in software raid 1
  • From: Andrei Banu <andrei.banu@xxxxxxxxxx>
• Anomaly with 2 x 840Pro SSDs in software raid 1
  • From: Andrei Banu <andrei.banu@xxxxxxxxxx>
• Raid 5 Array 3/4 Drives non-fresh
  • From: John <linux_mailing@xxxxxxxxxxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Dave Gomboc <dave_gomboc@xxxxxxx>
• Unable to start RAID5 array
  • From: Sachin Garg <sgarg.bugreporter@xxxxxxxxx>
• [PATCH] RAID5: Change kmem_cache name string of RAID 4/5/6 stripe cache
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH] Problems with RAID 4/5/6 and kmem_cache
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• 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: RAID 5 3-drive array failed 2 disks at once - can anything be saved?
  • From: Robert Schultz <rob@xxxxxxxxxxxxxxxx>
• Re: Best configuration for bcache/md cache or other cache using ssd
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• 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: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: Best configuration for bcache/md cache or other cache using ssd
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Moving drives around for a new one
  • From: Jonathan Wilson <piercing_male@xxxxxxxxxxx>
• Re: Moving drives around for a new one
  • From: "Timothy D. Lenz" <tlenz@xxxxxxxxxx>
• Re: Best configuration for bcache/md cache or other cache using ssd
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID 5 3-drive array failed 2 disks at once - can anything be saved?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: raid10 recovery assistance requested
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• 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: RAID 5 3-drive array failed 2 disks at once - can anything be saved?
  • From: Robert Schultz <rob@xxxxxxxxxxxxxxxx>
• 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: Drew <drew.kay@xxxxxxxxx>
• 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: Tommy Apel <tommyapeldk@xxxxxxxxx>
• Re: Best configuration for bcache/md cache or other cache using ssd
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Fwd: Best configuration for bcache/md cache or other cache using ssd
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Fwd: Best configuration for bcache/md cache or other cache using ssd
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: Best configuration for bcache/md cache or other cache using ssd
  • From: Drew <drew.kay@xxxxxxxxx>
• Best configuration for bcache/md cache or other cache using ssd
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Remove bashism from Makefile
  • From: NeilBrown <neilb@xxxxxxx>
• Fwd: Mdadm 3.3 reshape issue
  • From: Justin Maggard <jmaggard10@xxxxxxxxx>
• Re: Mdadm 3.3 reshape issue
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Mdadm 3.3 reshape issue
  • From: Justin Maggard <jmaggard10@xxxxxxxxx>
• Remove bashism from Makefile
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: LSI 9211 (SAS2008) BIOS problems, invalid PCI slot
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• Re: LSI 9211 (SAS2008) BIOS problems, invalid PCI slot
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: LSI 9211 (SAS2008) BIOS problems, invalid PCI slot
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• Re: LSI 9211 (SAS2008) BIOS problems, invalid PCI slot
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 3/3] DDF: compare_super_ddf: fix sequence number check
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Moving drives around for a new one
  • From: "Timothy D. Lenz" <tlenz@xxxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Weirdness with DDF arrays (mdadm 3.3)
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Weirdness with DDF arrays (mdadm 3.3)
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Weirdness with DDF arrays (mdadm 3.3)
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• raid10 recovery assistance requested
  • From: Dave Gomboc <dave_gomboc@xxxxxxx>
• Re: RAID 5 3-drive array failed 2 disks at once - can anything be saved?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• LSI 9211 (SAS2008) BIOS problems, invalid PCI slot
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• Re: Weirdness with DDF arrays (mdadm 3.3)
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: RAID 5 3-drive array failed 2 disks at once - can anything be saved?
  • From: Robert Schultz <rob@xxxxxxxxxxxxxxxx>
• [PATCH] Monitor: don't set arrays dirty after transition to read-only
  • From: mwilck@xxxxxxxx
• Re: "detect reshape on array start" (was Re: Weirdness with DDF arrays (mdadm 3.3))
  • From: Martin Wilck <mwilck@xxxxxxxx>
• "detect reshape on array start" (was Re: Weirdness with DDF arrays (mdadm 3.3))
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 1/3] DDF tests: allow to run on systems without /dev/sda
  • From: mwilck@xxxxxxxx
• [PATCH 3/3] DDF: compare_super_ddf: fix sequence number check
  • From: mwilck@xxxxxxxx
• [PATCH 2/3] DDF test: make sure mdmon isn't started by systemd
  • From: mwilck@xxxxxxxx
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Weirdness with DDF arrays (mdadm 3.3)
  • From: Martin Wilck <mwilck@xxxxxxxx>
• mke2fs with discard option breaks RAID5 array
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Weirdness with DDF arrays (mdadm 3.3)
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Weirdness with DDF arrays (mdadm 3.3)
  • From: Martin Wilck <mwilck@xxxxxxxx>
• 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>
• Re: RAID 5 3-drive array failed 2 disks at once - can anything be saved?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: NeilBrown <neilb@xxxxxxx>
• Re: How-to for enabling TRIM for SSD RAID-1 arrays?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Inoperative array shown as "active"
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: Inoperative array shown as "active"
  • From: NeilBrown <neilb@xxxxxxx>
• Inoperative array shown as "active"
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: How-to for enabling TRIM for SSD RAID-1 arrays?
  • From: Derek Piper <derek.piper@xxxxxxxxx>
• Moving drives around for a new one
  • From: "Timothy D. Lenz" <tlenz@xxxxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: How-to for enabling TRIM for SSD RAID-1 arrays?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: How-to for enabling TRIM for SSD RAID-1 arrays?
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: mdadm 3.3 fails to kick out non fresh disk
  • From: NeilBrown <neilb@xxxxxxx>
• Re: How-to for enabling TRIM for SSD RAID-1 arrays?
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• How-to for enabling TRIM for SSD RAID-1 arrays?
  • From: Derek Piper <derek.piper@xxxxxxxxx>
• Re: Implementing --detail-platform for DDF
  • From: Martin Wilck <mwilck@xxxxxxxx>
• RAID 5 3-drive array failed 2 disks at once - can anything be saved?
  • From: Robert Schultz <rob@xxxxxxxxxxxxxxxx>
• mdadm 3.3 fails to kick out non fresh disk
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Implementing --detail-platform for DDF
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] mdmon: honour --offroot, again
  • From: NeilBrown <neilb@xxxxxxx>
• Installing openSUSE 12.3 on DDF fake RAID with mdadm
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH] mdmon: honour --offroot, again
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Implementing --detail-platform for DDF
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Weirdness with DDF arrays (mdadm 3.3)
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: [BUG] md hang at schedule in md_write_start
  • From: Jack Wang <jinpu.wang@xxxxxxxxxxxxxxxx>
• Re: mdadm 3.3: issue with mdmon --takeover
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: 回复: [RFC PATCH V3] raid1: rewrite the iobarrier ― Linux RAID Storage
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [PATCH v2] md/raid5: avoid deadlock when raid5 array has unack badblocks during md_stop_writes.
  • From: ycbzzjlby <ycbzzjlby@xxxxxxxxx>
• Re: Implementing --detail-platform for DDF
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md/raid5: fresh drive rebuild always requires a fullsync if interrupted
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] DDF: brief_examine_subarrays_ddf: print array name
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] DDF: brief_examine_subarrays_ddf: print array name
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] mdmon: honour --offroot, again
  • From: NeilBrown <neilb@xxxxxxx>
• Re: change '%' to condition
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm 3.3: issue with mdmon --takeover
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm 3.3: issue with mdmon --takeover
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm 3.3: issue with mdmon --takeover
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH v2] md/raid5: avoid deadlock when raid5 array has unack badblocks during md_stop_writes.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: change '%' to condition
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• change '%' to condition
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: write-refresh md array (feature request)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [BUG] md hang at schedule in md_write_start
  • From: NeilBrown <neilb@xxxxxxx>
• Implementing --detail-platform for DDF
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: mdadm 3.3: issue with mdmon --takeover
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH] mdmon: honour --offroot, again
  • From: mwilck@xxxxxxxx
• [PATCH 2/2] DDF: brief_examine_subarrays_ddf: print array name
  • From: mwilck@xxxxxxxx
• [PATCH 1/2] DDF: factor out array name generation
  • From: mwilck@xxxxxxxx
• Re: [PATCH 1/2] DDF: brief_examine_subarrays_ddf: print array name
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/2] DDF: brief_examine_subarrays_ddf: print array name
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: write-refresh md array (feature request)
  • From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
• Re: write-refresh md array (feature request)
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• md/raid5: fresh drive rebuild always requires a fullsync if interrupted
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• [PATCH v2] md/raid5: avoid deadlock when raid5 array has unack badblocks during md_stop_writes.
  • From: ycbzzjlby@xxxxxxxxx
• Re: write-refresh md array (feature request)
  • From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
• Re: write-refresh md array (feature request)
  • From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
• Re: Managing mdam
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm 3.3: issue with mdmon --takeover
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: mdadm 3.3: issue with mdmon --takeover
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• RE: Managing mdam
  • From: "Francois Billard" <francois.billard@xxxxxxxxxx>
• Re: [BUG] md hang at schedule in md_write_start
  • From: Jack Wang <xjtuwjp@xxxxxxxxx>
• Re: write-refresh md array (feature request)
  • From: CoolCold <coolthecold@xxxxxxxxx>
• [PATCH] bcache: defensively handle format strings
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH] raid5: Retry R5_ReadNoMerge flag when hit a read error.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: write-refresh md array (feature request)
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [BUG] md hang at schedule in md_write_start
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Managing mdam
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm 3.3: issue with mdmon --takeover
  • From: NeilBrown <neilb@xxxxxxx>
• write-refresh md array (feature request)
  • From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
• [PATCH] raid5: Retry R5_ReadNoMerge flag when hit a read error.
  • From: ycbzzjlby@xxxxxxxxx
• Re: Mixing WD red with older seagates
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: [BUG] md hang at schedule in md_write_start
  • From: Jack Wang <jinpu.wang@xxxxxxxxxxxxxxxx>
• Re: Mixing WD red with older seagates
  • From: Andrew Brooks <arb@xxxxxxxxxxxxxxxx>
• Managing mdam
  • From: Francois Billard <francois.billard@xxxxxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Subject: [PATCH] md: avoid deadlock when raid5 array has unack badblocks during md_stop_writes.
  • From: y b <ycbzzjlby@xxxxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Subject: [PATCH] md: avoid deadlock when raid5 array has unack badblocks during md_stop_writes.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: NeilBrown <neilb@xxxxxxx>
• Subject: [PATCH] md: avoid deadlock when raid5 array has unack badblocks during md_stop_writes.
  • From: y b <ycbzzjlby@xxxxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PULL REQUEST] md update for v3.12
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] DDF: brief_examine_subarrays_ddf: print array name
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] DDF: new algorithm for subarray UUID
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] DDF: handle fake RAIDs with changing subarray UUIDs
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Manage.c: fix small memory leak
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] MAINTAINERS: update email for Dan Williams
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Installing SLES11 on DDF fake RAID with mdadm
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Mixing WD red with older seagates
  • From: "Timothy D. Lenz" <tlenz@xxxxxxxxxx>
• [PATCH 2/2] DDF: handle fake RAIDs with changing subarray UUIDs
  • From: mwilck@xxxxxxxx
• Re: [PATCH 2/2] DDF: new algorithm for subarray UUID
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/2] DDF: brief_examine_subarrays_ddf: print array name
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Mixing WD red with older seagates
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Mixing WD red with older seagates
  • From: Jonathan Wilson <piercing_male@xxxxxxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Mixing WD red with older seagates
  • From: Tudor Holton <tudor@xxxxxxxxxxxxxxxxx>
• Mixing WD red with older seagates
  • From: "Timothy D. Lenz" <tlenz@xxxxxxxxxx>
• Re: Update to mdadm V3.2.5 => RAID starts to recover (reproducible)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] DDF: new algorithm for subarray UUID
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] DDF: brief_examine_subarrays_ddf: print array name
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid6 array assembled from 11 drives and 2 spares - not enough to start the array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: raid6 array assembled from 11 drives and 2 spares - not enough to start the array
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: raid6 array assembled from 11 drives and 2 spares - not enough to start the array
  • From: Garðar Arnarsson <gardar@xxxxxxxxxxx>
• Re: raid6 array assembled from 11 drives and 2 spares - not enough to start the array
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: raid6 array assembled from 11 drives and 2 spares - not enough to start the array
  • From: Garðar Arnarsson <gardar@xxxxxxxxxxx>
• raid6 array assembled from 11 drives and 2 spares - not enough to start the array
  • From: Garðar Arnarsson <gardar@xxxxxxxxxxx>
• Re: [PATCH 2/2] DDF: new algorithm for subarray UUID
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Is a raid0 512 byte chunk size possible? Or is it just too small?
  • From: Veedar Hokstadt <veedar@xxxxxxxxx>
• [PATCH 2/2] DDF: new algorithm for subarray UUID
  • From: mwilck@xxxxxxxx
• [PATCH 1/2] DDF: brief_examine_subarrays_ddf: print array name
  • From: mwilck@xxxxxxxx
• Re: Problem halting raid 1
  • From: Tregaron Bayly <tbayly@xxxxxxxxxxxx>
• Re: Problem halting raid 1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problem halting raid 1
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Problem halting raid 1
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Problem halting raid 1
  • From: Miguel Corberán Ruiz <migcorrui@xxxxxxxxx>
• Re: Update to mdadm V3.2.5 => RAID starts to recover (reproducible)
  • From: Andreas Baer <synthetic.gods@xxxxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH] Manage.c: fix small memory leak
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: mdadm 3.3: issue with mdmon --takeover
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: mdadm 3.3: issue with mdmon --takeover
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm 3.3: issue with mdmon --takeover
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [Question] Fail event during reshape raid5 -> raid6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm 3.3: issue with mdmon --takeover
  • From: NeilBrown <neilb@xxxxxxx>
• mdadm 3.3: issue with mdmon --takeover
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• [Question] Fail event during reshape raid5 -> raid6
  • From: "Roland 'ValiDOM' Jungnickel" <vali2013@xxxxxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: NeilBrown <neilb@xxxxxxx>
• Subject: ANNOUNCE: mdadm 3.3 - A tools for managing md Soft RAID under Linux
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 6/6] mdmon: allow disabling "@dmon" command name at compile time
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 6/6] mdmon: allow disabling "@dmon" command name at compile time
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: question about mdmon --takeover
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: question about mdmon --takeover
  • From: NeilBrown <neilb@xxxxxxx>
• Re: question about mdmon --takeover
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: question about mdmon --takeover
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Update to mdadm V3.2.5 => RAID starts to recover (reproducible)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 6/6] mdmon: allow disabling "@dmon" command name at compile time
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch v3 5/5] raid5: only wakeup necessary threads
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 6/6] mdmon: allow disabling "@dmon" command name at compile time
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Failed to find backup of critical section
  • From: Nathan Shearer <mail@xxxxxxxxxxxxxxxx>
• Re: Failed to find backup of critical section
  • From: NeilBrown <neilb@xxxxxxx>
• Failed to find backup of critical section
  • From: Nathan Shearer <mail@xxxxxxxxxxxxxxxx>
• Re: question about mdmon --takeover
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Unmount a raid device during recovery in progress
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Unmount a raid device during recovery in progress
  • From: Zoltán Török <torokze@xxxxxxxxx>
• Re: Is a raid0 512 byte chunk size possible? Or is it just too small?
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Is a raid0 512 byte chunk size possible? Or is it just too small?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Is a raid0 512 byte chunk size possible? Or is it just too small?
  • From: Veedar Hokstadt <veedar@xxxxxxxxx>
• Re: Is a raid0 512 byte chunk size possible? Or is it just too small?
  • From: Marcus Sorensen <shadowsor@xxxxxxxxx>
• Re: Is a raid0 512 byte chunk size possible? Or is it just too small?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid 5 with 2 failed drives
  • From: "Tsaousis, Costa" <costa@xxxxxxxxxxx>
• Is a raid0 512 byte chunk size possible? Or is it just too small?
  • From: Veedar Hokstadt <veedar@xxxxxxxxx>
• Re: RAID 10 on Fusion IO cards problems
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: RAID 10 on Fusion IO cards problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• raid 5 with 2 failed drives
  • From: "Tsaousis, Costa" <costa@xxxxxxxxxxx>
• Re: RAID 10 on Fusion IO cards problems
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID 10 on Fusion IO cards problems
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID 10 on Fusion IO cards problems
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: RAID 10 on Fusion IO cards problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: RAID 10 on Fusion IO cards problems
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Update to mdadm V3.2.5 => RAID starts to recover (reproducible)
  • From: Andreas Baer <synthetic.gods@xxxxxxxxx>
• RAID 10 on Fusion IO cards problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: [patch v3 5/5] raid5: only wakeup necessary threads
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: question about mdmon --takeover
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: question about mdmon --takeover
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: [patch v3 1/5] raid5: make release_stripe lockless
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [patch v3 1/5] raid5: make release_stripe lockless
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch v3 1/5] raid5: make release_stripe lockless
  • From: Tejun Heo <tj@xxxxxxxxxx>
• [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 3/4] raid1: Add some macros to make code clearly.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 2/4] radi1: Relace raise_barrier/lower_barrrier with freeze_array/unfreeze_array for reconfigure the array.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 1/4] raid1: Add a filed array_frozen to indicate whether raid in freeze state.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: [patch v3 5/5] raid5: only wakeup necessary threads
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch v3 3/5] raid5: offload stripe handle to workqueue
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch v3 2/5] raid5: fix stripe release order
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch v3 5/5] raid5: only wakeup necessary threads
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch v3 3/5] raid5: offload stripe handle to workqueue
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch v3 2/5] raid5: fix stripe release order
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 6/6] mdmon: allow disabling "@dmon" command name at compile time
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 5/6] in_initrd: fix gcc compiler error
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/6] DDF: ddf_activate_spare: fix gcc -O2 uninitialized warning
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch v3 5/5] raid5: only wakeup necessary threads
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch v3 3/5] raid5: offload stripe handle to workqueue
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch v3 2/5] raid5: fix stripe release order
  • From: NeilBrown <neilb@xxxxxxx>
• [patch v3 5/5] raid5: only wakeup necessary threads
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch v3 4/5] raid5: sysfs entry to control worker thread number
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch v3 3/5] raid5: offload stripe handle to workqueue
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch v3 2/5] raid5: fix stripe release order
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch v3 1/5] raid5: make release_stripe lockless
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch v3 0/5] raid5: make stripe handling multi-threading
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Accesses to not yet running array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: [patch 0/3 v2] raid5: make stripe handling multi-threading
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Disk with backup-file died during reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Disk with backup-file died during reshape
  • From: Iruwen <iruwen@xxxxxxx>
• Re: Re: [PATCH 3/3] raid1: Rewrite the implementation of iobarrier.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: Accesses to not yet running array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Accesses to not yet running array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/3] raid1: Rewrite the implementation of iobarrier.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/3] raid1: Rewrite the implementation of iobarrier.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Accesses to not yet running array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Update to mdadm V3.2.5 => RAID starts to recover (reproducible)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Accesses to not yet running array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Accesses to not yet running array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Accesses to not yet running array
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Accesses to not yet running array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Accesses to not yet running array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Installing CentOS 6.4 on DDF fake RAID with mdadm
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Accesses to not yet running array
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Accesses to not yet running array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• [PATCH] When hit a read error, retry request with R5_ReadNoMerge flag.
  • From: y b <ycbzzjlby@xxxxxxxxx>
• Update to mdadm V3.2.5 => RAID starts to recover (reproducible)
  • From: Andreas Baer <synthetic.gods@xxxxxxxxx>
• Re: Accesses to not yet running array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Accesses to not yet running array
  • From: NeilBrown <neilb@xxxxxxx>
• Accesses to not yet running array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• RE: Recovery of RAID1 fails (added disks stays as spare)
  • From: <Matthias.Blaesing@xxxxxxxxxx>