Linux RAID Storage Date Index

• Thread Index

• [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>
• Re: off - info about servers and linux mail lists
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• off - info about servers and linux mail lists
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Fix apparent cut-and-paste error in super_90_validate
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Small chunk size read performance penalty
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Fix apparent cut-and-paste error in super_90_validate
  • From: Dave Jones <davej@xxxxxxxxxx>
• [PATCH 3/3] raid1: Rewrite the implementation of iobarrier.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 2/3] radi1: Relace raise_barrier/lower_barrrier with freeze_array/unfreeze_array for reconfigure the array.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 1/3] raid1: Add a filed freeze_array to indicate whether raid in freeze state.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [RFC PATCH 0/3 V2] Rewrite the implementation of iobarrier for raid1.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: Recovery of RAID1 fails (added disks stays as spare)
  • From: NeilBrown <neilb@xxxxxxx>
• RE: Recovery of RAID1 fails (added disks stays as spare)
  • From: <Matthias.Blaesing@xxxxxxxxxx>
• Re: Small chunk size read performance penalty
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: Small chunk size read performance penalty
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Small chunk size read performance penalty
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Does the chunk size of RAID5 really mean the "smallest atomic" mass of data?
  • From: NeilBrown <neilb@xxxxxxx>
• Does the chunk size of RAID5 really mean the "smallest atomic" mass of data?
  • From: taejin1999@xxxxxxxxxxxxxxxxx
• Re: Small chunk size read performance penalty
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Small chunk size read performance penalty
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• raid5: a problem of repeat recovery
  • From: wangkaird <wangkaird@xxxxxxxxx>
• Re: Recovery of RAID1 fails (added disks stays as spare)
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 2/6] DDF: export_examine_super_ddf: print MD_DEVICES
  • From: mwilck@xxxxxxxx
• [PATCH 5/6] in_initrd: fix gcc compiler error
  • From: mwilck@xxxxxxxx
• [PATCH 6/6] mdmon: allow disabling "@dmon" command name at compile time
  • From: mwilck@xxxxxxxx
• [PATCH 4/6] DDF: increase default value for safe_mode_delay to 4000ms
  • From: mwilck@xxxxxxxx
• [PATCH 0/6] Fixes for installation of CentOS 6 on DDF BIOS RAID
  • From: mwilck@xxxxxxxx
• [PATCH 1/6] DDF: ddf_activate_spare: fix gcc -O2 uninitialized warning
  • From: mwilck@xxxxxxxx
• [PATCH 3/6] DDF: container_content_ddf: set safe_mode_delay > 0
  • From: mwilck@xxxxxxxx
• Re: Request for help with "1st time through" RAID array renaming
  • From: ariel.work@xxxxxxxxxx
• Re: Problem with disk replacement
  • From: qindehua <qindehua@xxxxxxx>
• Recovery of RAID1 fails (added disks stays as spare)
  • From: <Matthias.Blaesing@xxxxxxxxxx>
• Re: Request for help with "1st time through" RAID array renaming
  • From: ariel.work@xxxxxxxxxx
• Re: Request for help with "1st time through" RAID array renaming
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID problem
  • From: NeilBrown <neilb@xxxxxxx>
• RAID problem
  • From: fixitdad5@xxxxxxxxxxx
• Re: Request for help with "1st time through" RAID array renaming
  • From: ariel.work@xxxxxxxxxx
• Request for help with "1st time through" RAID array renaming
  • From: ariel.work@xxxxxxxxxx
• Re: [BUG] md hang at schedule in md_write_start
  • From: Jack Wang <jinpu.wang@xxxxxxxxxxxxxxxx>
• Re: [BUG] md hang at schedule in md_write_start
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Ed L Cashin <ecashin@xxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [BUG] md hang at schedule in md_write_start
  • From: Jack Wang <jinpu.wang@xxxxxxxxxxxxxxxx>
• Re: [BUG] md hang at schedule in md_write_start
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [BUG] md hang at schedule in md_write_start
  • From: Jack Wang <jinpu.wang@xxxxxxxxxxxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Wes <wt75@xxxxxxxxx>
• [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 2/3] wait: add wait_event_cmd()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 1/3] raid5: rename stripe_hash()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 0/3] raid5: relieve lock contention of get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 2/3 v2] raid5: sysfs entry to control worker thread number
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 3/3 v2] raid5: only wakeup necessary threads
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 1/3 v2] raid5: offload stripe handle to workqueue
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 0/3 v2] raid5: make stripe handling multi-threading
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Recovering from two almost simultaneously failed devices in RAID1
  • From: Carsten Aulbert <Carsten.Aulbert@xxxxxxxxxx>
• Re: Recovering from two almost simultaneously failed devices in RAID1
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Recovering from two almost simultaneously failed devices in RAID1
  • From: Carsten Aulbert <Carsten.Aulbert@xxxxxxxxxx>
• Re: Recovering from two almost simultaneously failed devices in RAID1
  • From: Carsten Aulbert <Carsten.Aulbert@xxxxxxxxxx>
• Recovering from two almost simultaneously failed devices in RAID1
  • From: Carsten Aulbert <Carsten.Aulbert@xxxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• Re: [PATCH 18/22] block: Generic bio chaining
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: raid1 read io balancing algorithm
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: raid1 read io balancing algorithm
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• raid1 read io balancing algorithm
  • From: <struhlo@xxxxxxxxxx>
• Re: RFC: handling of missing disks in DDF
  • From: Martin Wilck <martin.wilck@xxxxxxxxxxxxxx>
• Re: [PATCH 9/9] Create: set array status to frozen until monitoring starts
  • From: Martin Wilck <martin.wilck@xxxxxxxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: DDF test fails if default udev rules are active
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 9/9] Create: set array status to frozen until monitoring starts
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] tests/10ddf-fail-two-spares: new unit test
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] RAID: add tilegx SIMD implementation of raid6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RFC: handling of missing disks in DDF
  • From: NeilBrown <neilb@xxxxxxx>
• RFC: handling of missing disks in DDF
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 03/22] bcache: Kill unaligned bvec hack
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 02/22] block: Consolidate duplicated bio_trim() implementations
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 01/22] block: Use rw_copy_check_uvector()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 06/22] block: Convert bio_iovec() to bvec_iter
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 09/22] block: Convert bio_copy_data() to bvec_iter
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 08/22] block: Immutable bio vecs
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 10/22] bio-integrity: Convert to bvec_iter
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 11/22] block: Kill bio_segments()/bi_vcnt usage
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 05/22] dm: Use bvec_iter for dm_bio_record()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 12/22] block: Convert drivers to immutable biovecs
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 15/22] rbd: Refactor bio cloning, don't clone biovecs
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 19/22] block: Rename bio_split() -> bio_pair_split()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 18/22] block: Generic bio chaining
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 17/22] block: Remove bi_idx hacks
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 13/22] ceph: Convert to immutable biovecs
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 20/22] block: Introduce new bio_split()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 21/22] block: Kill bio_pair_split()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 14/22] block: Kill bio_iovec_idx(), __bio_iovec()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 22/22] block: Don't save/copy bvec array anymore, share when cloning
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH] tests/10ddf-fail-two-spares: new unit test
  • From: mwilck@xxxxxxxx
• [PATCH] RAID: add tilegx SIMD implementation of raid6
  • From: Ken Steele <ken@xxxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• Re: DDF: regression caused by 273989b9 / ce45c819
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm --fail on RAID0 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• Re: DDF test fails if default udev rules are active
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 6/9] tests/10ddf-fail-spare: more sophisticated result checks
  • From: mwilck@xxxxxxxx
• [PATCH 9/9] Create: set array status to frozen until monitoring starts
  • From: mwilck@xxxxxxxx
• [PATCH 8/9] DDF: ddf_open_new: check device status for new subarray
  • From: mwilck@xxxxxxxx
• [PATCH 7/9] tests/10ddf-fail-create-race: test handling of fail/create race
  • From: mwilck@xxxxxxxx
• Patches related to current discussion
  • From: mwilck@xxxxxxxx
• mdadm --fail on RAID0 array
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• DDF: regression caused by 273989b9 / ce45c819
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: when md raid1 superblock is bad block, what happens
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• Re: when md raid1 superblock is bad block, what happens
  • From: NeilBrown <neilb@xxxxxxx>
• when md raid1 superblock is bad block, what happens
  • From: Dong Wu <archer.wudong@xxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 5/5] test: allow LVM volumes or RAM disks as test devices
  • From: mwilck@xxxxxxxx
• [PATCH 4/5] DDF: get_extents: don't allocate space on failed disks
  • From: mwilck@xxxxxxxx
• [PATCH 3/5] tests/10ddf-fail-spare: new unit test
  • From: mwilck@xxxxxxxx
• [PATCH 2/5] tests/10ddf-fail-twice: remove hard-coded assumptions
  • From: mwilck@xxxxxxxx
• [PATCH 1/5] tests/env-ddf-template: some helper functions
  • From: mwilck@xxxxxxxx
• Re: Bugreport ddf rebuild problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• when md raid1 superblock is bad block, what happens
  • From: "archer.wudong" <archer.wudong@xxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: question about mdmon --takeover
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bugreport: mdmon will not start with latest git version when using ddf container
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: fix checking completion of RAID10 resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] mdmon: let mdmon know the layout
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/4] DDF: ddf_process_update: delete removed disks from dlist
  • From: NeilBrown <neilb@xxxxxxx>
• Re: help needed restoring data
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Advice for recovering array containing LUKS encrypted LVM volumes
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• help needed restoring data
  • From: Uwe Wächter <uwe.waechter@xxxxxxxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Sam Bingner <sam@xxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Keld Jørn Simonsen <keld@xxxxxxxxxx>
• Re: [PATCH 3/4] DDF: ddf_process_update: delete removed disks from dlist
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: RFC swap over raid1
  • From: keld@xxxxxxxxxx
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• [PATCH] mdmon: let mdmon know the layout
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: RFC swap over raid1
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 4/4] tests/10ddf-fail-twice: New unit test
  • From: mwilck@xxxxxxxx
• [PATCH 3/4] DDF: ddf_process_update: delete removed disks from dlist
  • From: mwilck@xxxxxxxx
• [PATCH 2/4] DDF: no need for GET_LAYOUT any more
  • From: mwilck@xxxxxxxx
• [PATCH 1/4] mdmon: always get layout from sysfs
  • From: mwilck@xxxxxxxx
• Re: Bugreport ddf rebuild problems
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: RFC swap over raid1
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Martin Wilck <mwilck@xxxxxxxx>
• RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Bugreport ddf rebuild problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• RE: [PATCH] imsm: fix checking completion of RAID10 resync
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Tejun Heo <tj@xxxxxxxxxx>
• RE: [PATCH] imsm: fix checking completion of RAID10 resync
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: Bugreport: mdmon will not start with latest git version when using ddf container
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bugreport: mdmon will not start with latest git version when using ddf container
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Bugreport: mdmon will not start with latest git version when using ddf container
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Bugreport: mdmon will not start with latest git version when using ddf container
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• question about mdmon --takeover
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: Reshape/Grow to fewer but bigger devices
  • From: Christian Nilsson <nikize@xxxxxxxxx>
• Re: Reshape/Grow to fewer but bigger devices
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] tests/env-ddf-template: helper for new unit test
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] tests/env-ddf-template: helper for new unit test
  • From: mwilck@xxxxxxxx
• Re: [PATCH 06/10] monitor: read_and_act: log status when called
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Reshape/Grow to fewer but bigger devices
  • From: NeilBrown <neilb@xxxxxxx>
• Re: ddf: remove failed devices that are no longer in use ?!?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 00/10] Two bug fixes and a lot of debug code
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 06/10] monitor: read_and_act: log status when called
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Reshape/Grow to fewer but bigger devices
  • From: Christian Nilsson <nikize@xxxxxxxxx>
• Re: [PATCH] imsm: fix checking completion of RAID10 resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Avoid double close()
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 09/10] mdmon: manage_member: fix race condition during slow meta data writes
  • From: mwilck@xxxxxxxx
• [PATCH 10/10] tests/10ddf-create-fail-rebuild: new unit test for DDF
  • From: mwilck@xxxxxxxx
• [PATCH 07/10] mdmon: wait_and_act: fix debug message for SIGUSR1
  • From: mwilck@xxxxxxxx
• [PATCH 05/10] DDF: ddf_set_disk: add some debug messages
  • From: mwilck@xxxxxxxx
• [PATCH 06/10] monitor: read_and_act: log status when called
  • From: mwilck@xxxxxxxx
• [PATCH 08/10] mdmon: manage_member: debug messages for array state
  • From: mwilck@xxxxxxxx
• [PATCH 03/10] DDF: ddf_process_update: log offsets for conf changes
  • From: mwilck@xxxxxxxx
• [PATCH 04/10] DDF: load_ddf_header: more error logging
  • From: mwilck@xxxxxxxx
• [PATCH 01/10] DDF: ddf_activate_spare: bugfix for 62ff3c40
  • From: mwilck@xxxxxxxx
• [PATCH 02/10] DDF: log disk status changes more nicely
  • From: mwilck@xxxxxxxx
• [PATCH 00/10] Two bug fixes and a lot of debug code
  • From: mwilck@xxxxxxxx
• Re: Suspicious test failure - mdmon misses recovery events on loop devices
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: ddf: remove failed devices that are no longer in use ?!?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH] Avoid double close()
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: [patch 3/3] raid5: only wakeup necessary threads
  • From: Tejun Heo <tj@xxxxxxxxxx>
• [PATCH] imsm: fix checking completion of RAID10 resync
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [patch 3/3] raid5: only wakeup necessary threads
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [patch 3/3] raid5: only wakeup necessary threads
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Tejun Heo <tj@xxxxxxxxxx>
• [patch 3/3] raid5: only wakeup necessary threads
  • From: shli@xxxxxxxxxx
• [patch 2/3] raid5: sysfs entry to control worker thread number
  • From: shli@xxxxxxxxxx
• [patch 1/3] raid5: offload stripe handle to workqueue
  • From: shli@xxxxxxxxxx
• [patch 0/3] raid5: make stripe handling multi-threading
  • From: shli@xxxxxxxxxx
• Re: Recovery possible after partial reshape failure?
  • From: Veedar Hokstadt <veedar@xxxxxxxxx>
• Re: ddf: remove failed devices that are no longer in use ?!?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/4] Basic hotspare handling for RAID10
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Suspicious test failure - mdmon misses recovery events on loop devices
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Mdadm server eating drives
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Suspicious test failure - mdmon misses recovery events on loop devices
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Suspicious test failure - mdmon misses recovery events on loop devices
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• RE: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Suspicious test failure - mdmon misses recovery events on loop devices
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch]raid5: fix stripe release order
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md/raid5: raid5d livelocks after drive failure during resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: md/raid5: raid5d livelocks after drive failure during resync
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Marcus Sorensen <shadowsor@xxxxxxxxx>
• Re: Recovery help? 4-disk RAID5 double-failure, but good disks have event count mismatch.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Wes <wt75@xxxxxxxxx>
• Recovery help? 4-disk RAID5 double-failure, but good disks have event count mismatch.
  • From: Richard Michael <rmichael@xxxxxxxxxxxxxxxx>
• ddf: remove failed devices that are no longer in use ?!?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Suspicious test failure - mdmon misses recovery events on loop devices
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: mdadm -Db switches array to write-pending?!
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm -Db switches array to write-pending?!
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• RE: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PULL REQUEST] 2 more bug fixes for md in 3.11
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• RE: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 1/4] DDF: find_vdcr: fix minor bug in debug message
  • From: mwilck@xxxxxxxx
• [PATCH 4/4] DDF: ddf_activate_spare: fix metadata update for SVDs
  • From: mwilck@xxxxxxxx
• [PATCH 3/4] DDF: ddf_activate_spare: only activate good drives
  • From: mwilck@xxxxxxxx
• [PATCH 2/4] DDF: ddf_activate_spare: Add RAID10 code
  • From: mwilck@xxxxxxxx
• [PATCH 0/4] Basic hotspare handling for RAID10
  • From: mwilck@xxxxxxxx
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Wes <wt75@xxxxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Wes <wt75@xxxxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• raid10 centos5 vs. centos6 300% worse random write performance
  • From: Wes <wt75@xxxxxxxxx>
• [patch]raid5: fix stripe release order
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Preparing for mdadm-3.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problem with disk replacement
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problem with disk replacement
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Problem with disk replacement
  • From: qindehua <qindehua@xxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Help creating filesystem (xfs) and partitioning
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: shown disk sizes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: shown disk sizes
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: shown disk sizes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: shown disk sizes
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: Should "mdadm --add" complain if the new device appears to have a filesystem on it?
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: shown disk sizes
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: shown disk sizes
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Should "mdadm --add" complain if the new device appears to have a filesystem on it?
  • From: Christian Iversen <chrivers@xxxxxxxxxxxxxx>
• MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Should "mdadm --add" complain if the new device appears to have a filesystem on it?
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: [PATCH 2/2 v2] md: set write-intent bit first in sync-bitmap for rwm in non-insync region.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2 v2] md: add sync-bitmap to only resync WRITTEN data when adding new disk in raid array.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC/PATCH 0/6] DDF: safe big-endian types
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problem with disk replacement
  • From: NeilBrown <neilb@xxxxxxx>
• Should "mdadm --add" complain if the new device appears to have a filesystem on it?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problem with disk replacement
  • From: qindehua <qindehua@xxxxxxx>
• [PATCH v2] mdadm: add sync-bitmap to only resync WRITTEN data when adding new disk in raid array.
  • From: Robin Dong <robin.k.dong@xxxxxxxxx>
• [PATCH 2/2 v2] md: set write-intent bit first in sync-bitmap for rwm in non-insync region.
  • From: Robin Dong <robin.k.dong@xxxxxxxxx>
• [PATCH 1/2 v2] md: add sync-bitmap to only resync WRITTEN data when adding new disk in raid array.
  • From: Robin Dong <robin.k.dong@xxxxxxxxx>
• Re: Problem with disk replacement
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 1/6] DDF: add endian-safe typedefs
  • From: mwilck@xxxxxxxx
• [PATCH 2/6] DDF: convert big endian to be32 type
  • From: mwilck@xxxxxxxx
• [PATCH 4/6] DDF: convert big-endian __u16 to be16 type
  • From: mwilck@xxxxxxxx
• [PATCH 5/6] DDF: add_other_bvd: fix endianness bug
  • From: mwilck@xxxxxxxx
• [PATCH 3/6] DDF: convert big-endian __u64 to be64 type
  • From: mwilck@xxxxxxxx
• [PATCH 6/6] DDF: ddf_set_disk: fix minor endianness bug
  • From: mwilck@xxxxxxxx
• [RFC/PATCH 0/6] DDF: safe big-endian types
  • From: mwilck@xxxxxxxx
• Re: How does md(adm) work with fake-raid ?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: How does md(adm) work with fake-raid ?
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>