Linux RAID Storage Date Index

• Thread Index

• Re: Mounting array at boot - works with some kernels but not others
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Mounting array at boot - works with some kernels but not others
  • From: Dennis Grant <reccedg@xxxxxxxxx>
• Re: Mounting array at boot - works with some kernels but not others
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Raid 5 Array
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Mounting array at boot - works with some kernels but not others
  • From: Dennis Grant <reccedg@xxxxxxxxx>
• Re: Raid Checks
  • From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
• Re: Raid 5 Array
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Raid 5 Array
  • From: Marcus <nexuslite@xxxxxxxxx>
• Re: Mounting array at boot - works with some kernels but not others
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mounting array at boot - works with some kernels but not others
  • From: Dennis Grant <reccedg@xxxxxxxxx>
• Re: Mounting array at boot - works with some kernels but not others
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mounting array at boot - works with some kernels but not others
  • From: Dennis Grant <reccedg@xxxxxxxxx>
• Re: Mounting array at boot - works with some kernels but not others
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Mounting array at boot - works with some kernels but not others
  • From: Dennis Grant <reccedg@xxxxxxxxx>
• Mdadm, udev and fakeraid?
  • From: Seblu <seblu@xxxxxxxxx>
• Re: What the heck happened to my array? (No apparent data loss).
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• What the heck happened to my array? (No apparent data loss).
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Raid Checks
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Raid Checks
  • From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
• Re: Raid Checks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid Checks
  • From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
• Re: Raid Checks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid 5 Array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid Checks
  • From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
• Raid Checks
  • From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
• Re: Raid 5 Array
  • From: Marcus <nexuslite@xxxxxxxxx>
• Re: Raid 5 Array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid 5 Array
  • From: Marcus <nexuslite@xxxxxxxxx>
• Re: Raid 5 Array
  • From: Marcus <nexuslite@xxxxxxxxx>
• Re: Raid 5 Array
  • From: Marcus <nexuslite@xxxxxxxxx>
• Re: Raid 5 Array
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Raid 5 Array
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Raid 5 Array
  • From: Simon Mcnair <simonmcnair@xxxxxxxxx>
• Re: Raid 5 Array
  • From: Simon Mcnair <simonmcnair@xxxxxxxxx>
• Re: Raid 5 Array
  • From: Simon McNair <simonmcnair@xxxxxxxxx>
• Re: Raid 5 Array
  • From: Simon McNair <simonmcnair@xxxxxxxxx>
• Raid 5 Array
  • From: Marcus <nexuslite@xxxxxxxxx>
• mdadm 3.2.1: Segfaulting with -p
  • From: Eugene <hdejin@xxxxxxxxx>
• Re: [PATCH] RAID-6 check standalone md device
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: [PATCH] RAID-6 check standalone md device
  • From: Bas van Schaik <bas@xxxxxxxx>
• Re: Doing 'echo repair > /sys/devices/virtual/block/md?/md/sync_action' does not result in mismatch_cnt of 0 on RAID-6?
  • From: Rory Jaffe <rsjaffe@xxxxxxxxx>
• Re: Doing 'echo repair > /sys/devices/virtual/block/md?/md/sync_action' does not result in mismatch_cnt of 0 on RAID-6?
  • From: Bas van Schaik <bas@xxxxxxxx>
• Re: strange problem with my raid5
  • From: Simon McNair <simonmcnair@xxxxxxxxx>
• Re: strange problem with my raid5
  • From: Simon McNair <simonmcnair@xxxxxxxxx>
• Re: strange problem with my raid5
  • From: hank peng <pengxihan@xxxxxxxxx>
• Re: Extendible RAID10
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• [PATCH] RAID-6 check standalone md device
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Extendible RAID10
  • From: Keld Jørn Simonsen <keld@xxxxxxxxxx>
• Re: strange problem with my raid5
  • From: Simon McNair <simonmcnair@xxxxxxxxx>
• Re: raid6 + caviar black + mpt2sas horrific performance
  • From: Louis-David Mitterrand <vindex+lists-linux-raid@xxxxxxxxxxx>
• Re: raid6 + caviar black + mpt2sas horrific performance
  • From: Louis-David Mitterrand <vindex+lists-linux-raid@xxxxxxxxxxx>
• Re: looking for advice on raid drives upgrade
  • From: Vincent Schut <schut@xxxxxxxxxxxx>
• Re: Network-based RAID6
  • From: hansbkk@xxxxxxxxx
• Re: raid6 + caviar black + mpt2sas horrific performance
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: looking for advice on raid drives upgrade
  • From: hansbkk@xxxxxxxxx
• Re: Network-based RAID6
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Network-based RAID6
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Network-based RAID6
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid6 + caviar black + mpt2sas horrific performance
  • From: Iordan Iordanov <iordan@xxxxxxxxxxxxxxx>
• Re: Network-based RAID6
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Network-based RAID6
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: raid6 + caviar black + mpt2sas horrific performance
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: raid6 + caviar black + mpt2sas horrific performance
  • From: Louis-David Mitterrand <vindex+lists-linux-raid@xxxxxxxxxxx>
• md lzo
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Network-based RAID6
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Network-based RAID6
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: Network-based RAID6
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: looking for advice on raid drives upgrade
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: looking for advice on raid drives upgrade
  • From: Steven Haigh <netwiz@xxxxxxxxx>
• Re: raid6 + caviar black + mpt2sas horrific performance
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: raid6 + caviar black + mpt2sas horrific performance
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Network-based RAID6
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid6 + caviar black + mpt2sas horrific performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: looking for advice on raid drives upgrade
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• strange problem with my raid5
  • From: hank peng <pengxihan@xxxxxxxxx>
• blk_flush_plug in the MD code, was Re: [xfs-masters] linux-next: manual merge of the xfs tree with Linus' tree
  • From: Christoph Hellwig <hch@xxxxxx>
• Extendible RAID10
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• [PATCH 2/2] Create: fix size after setting default chunk
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• [PATCH 1/2] Create: check for UnSet when looking at chunk
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• Re: looking for advice on raid drives upgrade
  • From: Vincent Schut <schut@xxxxxxxxxxxx>
• Re: looking for advice on raid drives upgrade
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• looking for advice on raid drives upgrade
  • From: Vincent Schut <schut@xxxxxxxxxxxx>
• Re: Network-based RAID6
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• raid6 + caviar black + mpt2sas horrific performance
  • From: Louis-David Mitterrand <vindex+lists-linux-raid@xxxxxxxxxxx>
• Re: Network-based RAID6
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Network-based RAID6
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: raid1 boot regression in 2.6.37 [bisected]
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: raid1 boot regression in 2.6.37 [bisected]
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• Re: raid1 boot regression in 2.6.37 [bisected]
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• Re: raid1 boot regression in 2.6.37 [bisected]
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: raid1 boot regression in 2.6.37 [bisected]
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• Re: raid1 boot regression in 2.6.37 [bisected]
  • From: Tejun Heo <tj@xxxxxxxxxx>
• corrupted 600GiB md device
  • From: Nathan Gamber <ngamber@xxxxxxxxxxxxx>
• Re: raid1 boot regression in 2.6.37 [bisected]
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: raid1 boot regression in 2.6.37 [bisected]
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• Re: Something wrong with __prep_thunderdome in super-intel.c
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: raid1 boot regression in 2.6.37 [bisected]
  • From: Tejun Heo <tj@xxxxxxxxxx>
• [PATCH] FIX: Cleanup after raid45->raid0 takeover
  • From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
• [PATCH] FIX: After discarding array give chance monitor to remove it
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: raid1 boot regression in 2.6.37 [bisected]
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• Re: raid1 boot regression in 2.6.37 [bisected]
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• Re: raid1 boot regression in 2.6.37 [bisected]
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: Something wrong with __prep_thunderdome in super-intel.c
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Something wrong with __prep_thunderdome in super-intel.c
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] imsm: remove OEM table from detection of OROM and EFI.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] tests: use $config to store test config path
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] tests: backup default config before testing
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Disks with 4k sectors
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Disks with 4k sectors
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• raid1 boot regression in 2.6.37 [bisected]
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• Re: Something wrong with __prep_thunderdome in super-intel.c
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Please update mdadm 3.2.1 release
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 2/2] imsm: reading of UEFI variables needs an update
  • From: "Hawrylewicz Czarnowski, Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• [PATCH 1/2] imsm: remove OEM table from detection of OROM and EFI.
  • From: "Hawrylewicz Czarnowski, Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• RE: Something wrong with __prep_thunderdome in super-intel.c
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: grow MULTIPATH RAID
  • From: NeilBrown <neilb@xxxxxxx>
• Re: grow MULTIPATH RAID
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: grow MULTIPATH RAID
  • From: NeilBrown <neilb@xxxxxxx>
• Re: why disk errors are more likely to happen on md super block area?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• grow MULTIPATH RAID
  • From: shamim <shamim_99@xxxxxxxxx>
• Re: Something wrong with __prep_thunderdome in super-intel.c
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: why disk errors are more likely to happen on md super block area?
  • From: hank peng <pengxihan@xxxxxxxxx>
• [PATCH 2/2] tests: backup default config before testing
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• [PATCH 1/2] tests: use $config to store test config path
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• RE: [PATCH] FIX: imsm: Do not change serial if disk failed
  • From: "Wojcik, Krzysztof" <krzysztof.wojcik@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: why disk errors are more likely to happen on md super block area?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• why disk errors are more likely to happen on md super block area?
  • From: hank peng <pengxihan@xxxxxxxxx>
• Re: [PATCH] FIX: Do not count as backup devices, spare disks used for reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] FIX: imsm: Do not change serial if disk failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/2] Fixes for double degraded array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: More ddf container woes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: More ddf container woes
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• [PATCH] FIX: imsm: Do not change serial if disk failed
  • From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• [PATCH 2/2] FIX: Tests: raid0->raid10 without degradation
  • From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
• [PATCH 1/2] FIX: imsm: Rebuild does not start on second failed disk
  • From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
• [PATCH 0/2] Fixes for double degraded array
  • From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
• Re: Convert RAID5 to RAID6 in a live system
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Convert RAID5 to RAID6 in a live system
  • From: Stefan Roese <stefan.roese@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Convert RAID5 to RAID6 in a live system
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Convert RAID5 to RAID6 in a live system
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Convert RAID5 to RAID6 in a live system
  • From: Stefan Roese <stefan.roese@xxxxxxxxx>
• RE: [PATCH] FIX: Do not count as backup devices, spare disks used for reshape
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• ANNOUNCE: mdadm 3.1.5 - A tool for managing Soft RAID under Linux
  • From: NeilBrown <neilb@xxxxxxx>
• Re: cannot examine IMSM metadata on a disk in non-IMSM compliant system
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] man mdadm: Add note about auto-assembly during array reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] man mdadm: add information for MDADM_EXPERIMENTAL flag
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID-5 and mdadm --assemble troubleshooting
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 1/2] examine: allows to examine a disk metadata on non-metadata compliant systems
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• PATCH 2/2] super-intel: enable loading metadata from non-IMSM compliant disks
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• RE: cannot examine IMSM metadata on a disk in non-IMSM compliant system
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• Re: RAID-5 and mdadm --assemble troubleshooting
  • From: A J Wyborny <ajwyborny@xxxxxxxxx>
• Windows LDM status?
  • From: Costin <costinel@xxxxxxxxx>
• Re: [PATCH 1/2] man mdadm: add information for MDADM_EXPERIMENTAL flag
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• [PATCH 2/2] man mdadm: Add note about auto-assembly during array reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/2] man mdadm: add information for MDADM_EXPERIMENTAL flag
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Keld Jørn Simonsen <keld@xxxxxxxxxx>
• Re: high throughput storage server?
  • From: Keld Jørn Simonsen <keld@xxxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Something wrong with __prep_thunderdome in super-intel.c
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] RAID-6 check standalone
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID-5 and mdadm --assemble troubleshooting
  • From: NeilBrown <neilb@xxxxxxx>
• Re: high throughput storage server?
  • From: Keld Jørn Simonsen <keld@xxxxxxxxxx>
• RAID-5 and mdadm --assemble troubleshooting
  • From: A J Wyborny <ajwyborny@xxxxxxxxx>
• RE: Adaptive throttling for RAID1 background resync
  • From: Hari Subramanian <hari@xxxxxxxxxx>
• Re: high throughput storage server?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] RAID-6 check standalone
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: [PATCH] RAID-6 check standalone
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] RAID-6 check standalone
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: high throughput storage server?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: [PATCH] RAID-6 check standalone
  • From: NeilBrown <neilb@xxxxxxx>
• Re: high throughput storage server?
  • From: Keld Jørn Simonsen <keld@xxxxxxxxxx>
• Re: high throughput storage server?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: [PATCH] platform_intel: support EFI SCU OEM variable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: FIX: indicate that metadada has to be written
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] FIX: Add spare throws exception (v2)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] FIX: Do not count as backup devices, spare disks used for reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: high throughput storage server?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MD without LVM : should I reinstall ?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Adaptive throttling for RAID1 background resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: high throughput storage server?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Adaptive throttling for RAID1 background resync
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: MD without LVM : should I reinstall ?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: MD without LVM : should I reinstall ?
  • From: Thomas Carrié <thocar@xxxxxxxxxx>
• RE: Adaptive throttling for RAID1 background resync
  • From: Hari Subramanian <hari@xxxxxxxxxx>
• Re: Adaptive throttling for RAID1 background resync
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• RE: Adaptive throttling for RAID1 background resync
  • From: Hari Subramanian <hari@xxxxxxxxxx>
• Re: Adaptive throttling for RAID1 background resync
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Adaptive throttling for RAID1 background resync
  • From: Hari Subramanian <hari@xxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
• Re: disk order problem in a raid 10 array
  • From: hansbkk@xxxxxxxxx
• Re: high throughput storage server?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• disk order problem in a raid 10 array
  • From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
• [PATCH] platform_intel: support EFI SCU OEM variable
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• Re: i made sh*t can anyone help!?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: i made sh*t can anyone help!?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: i made sh*t can anyone help!?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: i made sh*t can anyone help!?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: i made sh*t can anyone help!?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: i made sh*t can anyone help!?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: i made sh*t can anyone help!?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: i made sh*t can anyone help!?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• i made sh*t can anyone help!?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PATCH] FIX: Do not count as backup devices, spare disks used for reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH] imsm: FIX: indicate that metadada has to be written
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH] FIX: Add spare throws exception (v2)
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH] FIX: Add spare throws exception
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• RE: [PATCH 0/4] Raid0 metadata cannot be recognized
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• [PATCH 13/36] md,rcu: convert call_rcu(free_conf) to kfree_rcu()
  • From: Lai Jiangshan <laijs@xxxxxxxxxxxxxx>
• Re: [PATCH] Update documentation for sync_min and sync_max entries
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/3] UT and error case changes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Retry writing 'inactive' state during stopping array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/4] Raid0 metadata cannot be recognized
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD without LVM : should I reinstall ?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: MD without LVM : should I reinstall ?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• MD without LVM : should I reinstall ?
  • From: Thomas Carrié <thocar@xxxxxxxxxx>
• MD without LVM : should I reinstall ?
  • From: Thomas Carrié <thocar@xxxxxxxxxx>
• MD without LVM : should I reinstall ?
  • From: Thomas Carrié <thocar@xxxxxxxxxx>
• RE: [PATCH] fix: mdadm -Ss for external metadata don't stop container
  • From: "Hawrylewicz Czarnowski, Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• Re: How to implement raid1 repair
  • From: Jan Schmidt <list.btrfs@xxxxxxxxxxxxx>
• Re: How to implement raid1 repair
  • From: Jan Schmidt <list.btrfs@xxxxxxxxxxxxx>
• Re: How to implement raid1 repair
  • From: Andrey Kuzmin <andrey.v.kuzmin@xxxxxxxxx>
• Re: How to implement raid1 repair
  • From: Chris Mason <chris.mason@xxxxxxxxxx>
• Re: How to implement raid1 repair
  • From: Jan Schmidt <list.btrfs@xxxxxxxxxxxxx>
• Re: How to implement raid1 repair
  • From: Chris Mason <chris.mason@xxxxxxxxxx>
• Re: [dm-devel] [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: How to implement raid1 repair
  • From: Josef Bacik <josef@xxxxxxxxxx>
• RE: [PATCH] fix: mdadm -Ss for external metadata don't stop container
  • From: "Wojcik, Krzysztof" <krzysztof.wojcik@xxxxxxxxx>
• [PATCH] Retry writing 'inactive' state during stopping array
  • From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
• How to implement raid1 repair
  • From: Jan Schmidt <list.btrfs@xxxxxxxxxxxxx>
• Re: [PATCH] fix: mdadm -Ss for external metadata don't stop container
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [dm-devel] [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: NeilBrown <neilb@xxxxxxx>
• RE: [PATCH] fix: mdadm -Ss for external metadata don't stop container
  • From: "Hawrylewicz Czarnowski, Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• inactive raid after kernel 2.6.32 update
  • From: Xavier Brochard <xavier@xxxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• [PATCH 04/13] dm: use list_move() instead of list_del()/list_add() combination
  • From: "Kirill A. Shutemov" <kirill@xxxxxxxxxxxxx>
• Re: More ddf container woes
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• md not flushing some pages
  • From: Alexander Dorokhine <adorokhine@xxxxxxxxxxxxxxx>
• [PATCH 3/4] FIX: Handle has to be closed
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 4/4] FIX: ping_monitor() usage causes memory leaks
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/4] FIX: Write metadata when mdmon is not running
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/4] FIX: Ping monitor when mdmon is running only
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/4] Raid0 metadata cannot be recognized
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: Doing 'echo repair > /sys/devices/virtual/block/md?/md/sync_action' does not result in mismatch_cnt of 0 on RAID-6?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Doing 'echo repair > /sys/devices/virtual/block/md?/md/sync_action' does not result in mismatch_cnt of 0 on RAID-6?
  • From: Bas van Schaik <bas@xxxxxxxx>
• [PATCH] Update documentation for sync_min and sync_max entries
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: Doing 'echo repair > /sys/devices/virtual/block/md?/md/sync_action' does not result in mismatch_cnt of 0 on RAID-6?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Doing 'echo repair > /sys/devices/virtual/block/md?/md/sync_action' does not result in mismatch_cnt of 0 on RAID-6?
  • From: Bas van Schaik <bas@xxxxxxxx>
• RE: [PATCH 0/3] UT and error case changes
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: Periodic RebuildStarted event
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID5 Shrinking array-size nearly killed the system
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID5 Shrinking array-size nearly killed the system
  • From: Rory Jaffe <rsjaffe@xxxxxxxxx>
• Re: RAID5 Shrinking array-size nearly killed the system
  • From: Rory Jaffe <rsjaffe@xxxxxxxxx>
• Re: More ddf container woes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Periodic RebuildStarted event
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: Periodic RebuildStarted event
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Periodic RebuildStarted event
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: Periodic RebuildStarted event
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Periodic RebuildStarted event
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Periodic RebuildStarted event
  • From: CoolCold <coolthecold@xxxxxxxxx>
• RE: Q: imsm rapid recovery volume
  • From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
• Re: [PATCH 0/3] UT and error case changes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Q: imsm rapid recovery volume
  • From: Luca Berra <bluca@xxxxxxxxxx>
• RE: Q: imsm rapid recovery volume
  • From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
• [PATCH 3/3] imsm: Add metadata abort changes handler template
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/3] External metadata has to be restored to initial state in error case
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/3] imsm: FIX: existing backup file fails unit tests
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/3] UT and error case changes
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: Q: imsm rapid recovery volume
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• RE: Removed two drives (still valid and working) from raid-5 and need to add them back in.
  • From: "Matthew Tice" <mjtice@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Q: imsm rapid recovery volume
  • From: Luca Berra <bluca@xxxxxxxxxx>
• Re: More ddf container woes
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: More ddf container woes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Warn the user about too small array size
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] platfrom_intel: find OROM based on Intel AHCI and SAS driver device id
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/2] Checkpointing fixes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Removed two drives (still valid and working) from raid-5 and need to add them back in.
  • From: mtice <mjtice@xxxxxxxxx>
• Raid1 mismatches maybe associated to free space
  • From: Asdo <asdo@xxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Growing a raid array online with different capacity disks
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: RAID5 Shrinking array-size nearly killed the system
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID5 Shrinking array-size nearly killed the system
  • From: Rory Jaffe <rsjaffe@xxxxxxxxx>
• Re: Removed two drives (still valid and working) from raid-5 and need to add them back in.
  • From: mtice <mjtice@xxxxxxxxx>
• Re: Removed two drives (still valid and working) from raid-5 and need to add them back in.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Removed two drives (still valid and working) from raid-5 and need to add them back in.
  • From: mtice <mjtice@xxxxxxxxx>
• Re: high throughput storage server? GPFS w/ 10GB/s throughput to the rescue
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: RAID5 Shrinking array-size nearly killed the system
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Removed two drives (still valid and working) from raid-5 and need to add them back in.
  • From: mtice <mjtice@xxxxxxxxx>
• Re: RAID5 Shrinking array-size nearly killed the system
  • From: Rory Jaffe <rsjaffe@xxxxxxxxx>
• Re: RAID5 Shrinking array-size nearly killed the system
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH] Add more warnings to --grow documentation (was: RAID5 Shrinking array-size nearly killed the system)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID5 Shrinking array-size nearly killed the system
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID5 Shrinking array-size nearly killed the system
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• RAID5 Shrinking array-size nearly killed the system
  • From: Rory Jaffe <rsjaffe@xxxxxxxxx>
• [PATCH] platfrom_intel: find OROM based on Intel AHCI and SAS driver device id
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 2/2] imsm: FIX: Store checkpoint in per disk units
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/2] FIX: Last_checkpoint has to be initialized in per disk units
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/2] Checkpointing fixes
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: More ddf container woes
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• BUG_ON() at shutdown time
  • From: Justin Maggard <jmaggard10@xxxxxxxxx>
• [PATCH] FIX: Last checkpoint is not initialized on reshape restart
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: polishing up mdadm manpages: mdassemble(8), mdmon(8)
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: Growing a raid array online with different capacity disks
  • From: hansbkk@xxxxxxxxx
• Re: Growing a raid array online with different capacity disks
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Growing a raid array online with different capacity disks
  • From: jimbob palmer <jimbobpalmer@xxxxxxxxx>
• Re: Growing a raid array online with different capacity disks
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Growing a raid array online with different capacity disks
  • From: jimbob palmer <jimbobpalmer@xxxxxxxxx>
• RE: [PATCH] Warn the user about too small array size
  • From: "Wojcik, Krzysztof" <krzysztof.wojcik@xxxxxxxxx>
• [PATCH] FIX: Unfreeze array on success only
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• More ddf container woes
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: polishing up mdadm manpages: mdassemble(8), mdmon(8)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 00/14] OROM/EFI support for Intel SAS and AHCI controllers in IMSM
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 9/9] imsm : FIX: Assemble dirty array when reshape is in progress
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 8/9] FIX: Set 'active' array state before array configuration
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 7/9] FIX: Array cannot be opened for writing on restart
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 6/9] FIX: Cannot continue reshape if mdmon is not run
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 5/9] FIX: Unfreeze array on success only during reshape continuation
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 4/9] imsm: FIX: Do not clean checkpoint for active reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/9] FIX: Make expansion counter usable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/9] FIX: Block reshaped array monitoring
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/9] FIX: Load container content for container reshape continuation
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 9/9] imsm : FIX: Assemble dirty array when reshape is in progress
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 8/9] FIX: Set 'active' array state before array configuration
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 7/9] FIX: Array cannot be opened for writing on restart
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 6/9] FIX: Cannot continue reshape if mdmon is not run
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 5/9] FIX: Unfreeze array on success only during reshape continuation
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 4/9] imsm: FIX: Do not clean checkpoint for active reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 3/9] FIX: Make expansion counter usable
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/9] FIX: Block reshaped array monitoring
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/9] FIX: Load container content for container reshape continuation
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/9] Reshape restart from checkpoint
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• RE: [PATCH 0/5] Make OLCE workeable
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• RE: [PATCH 0/5] Make OLCE workeable
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: [PATCH 0/5] Make OLCE workeable
  • From: NeilBrown <neilb@xxxxxxx>
• RE: [PATCH 0/5] Make OLCE workeable
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: [PATCH 3/5] FIX: Allow for takeover
  • From: NeilBrown <neilb@xxxxxxx>
• RE: [PATCH 4/9] imsm: FIX: After checkpoint mark array have to be clean
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: [PATCH 0/5] Make OLCE workeable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 02/14] Platform-intel: support for OROM SAS and AHCI controller
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 4/9] imsm: FIX: After checkpoint mark array have to be clean
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 01/14] probe_roms: allow to probe expansion ROMs using vendor and device id.
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 00/14] OROM/EFI support for Intel SAS and AHCI controllers in IMSM
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 13/14] imsm: introduce SAS controller support in imsm metadata handler
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 12/14] imsm: move code for retrieving HBA to a function
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 08/14] imsm: do not publish OROM/EFI unsupported arrays
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 07/14] imsm: detail_platform_imsm displays AHCI and SAS controller information
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 05/14] read platform capabilities from EFI
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 04/14] Some guid manipulation utilities has been added.
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 03/14] update of imsm_orom structure
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 02/14] Platform-intel: support for OROM SAS and AHCI controller
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 14/14] platform_intel: support for OROM OEM capabilities
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 11/14] imsm: verify that component disks are attached to the same type of HBA
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 10/14] imsm: add maximum number of disk validation in RAID array
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 09/14] imsm: print-out error message when volume validation fails
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 06/14] imsm: remove unused parameters in function attach_hba_to_super
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 5/5] FIX: Compute spares_needed basing on metadata info
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 4/5] FIX: Remove delta_parity concept
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 3/5] FIX: Allow for takeover
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/5] FIX: Set new raid disks when delta_disks is valid
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/5] fix: array is reassembled inactive if stopped during resync
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/5] Make OLCE workeable
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• RE: [PATCH 0/9] Grow_continue() - single array.
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• RE: [PATCH 4/9] imsm: FIX: After checkpoint mark array have to be clean
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• [PATCH 2/2] imsm: FIX: Mark checkpoint and array state clean during reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/2] FIX: During reshape array is in active state
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: [PATCH 0/9] Grow_continue() - single array.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 4/9] imsm: FIX: After checkpoint mark array have to be clean
  • From: NeilBrown <neilb@xxxxxxx>
• polishing up mdadm manpages: mdassemble(8), mdmon(8)
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: [dm-devel] [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [dm-devel] [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: James Bottomley <James.Bottomley@xxxxxxx>
• Re: [PATCH] Enable error message in case of lack of spares for grow
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] fix: generated udev rules does not work due to incorrect line format
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [dm-devel] [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] RAID-6 check standalone
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: [dm-devel] [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: James Bottomley <James.Bottomley@xxxxxxx>
• [PATCH] fix: generated udev rules does not work due to incorrect line format
  • From: "Hawrylewicz Czarnowski, Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• RE: Reshape restart questions.
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: Andrew Patterson <andrew.patterson@xxxxxx>
• Re: Reshape restart questions.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: stripe cache question
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: RAID6 seemingly shrunk itself after hard power outage and rebuild with replacement disk
  • From: "Robin H. Johnson" <robbat2@xxxxxxxxxx>
• Re: [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 seemingly shrunk itself after hard power outage and rebuild with replacement disk
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID6 seemingly shrunk itself after hard power outage and rebuild with replacement disk
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Impact of missing parameter during mdadm create
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• RE: Impact of missing parameter during mdadm create
  • From: Mike Viau <viaum@xxxxxxxxxxxxxxx>
• Re: RAID6 seemingly shrunk itself after hard power outage and rebuild with replacement disk
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• RE: Impact of missing parameter during mdadm create
  • From: Ken Drummond <linuxraid@xxxxxxxxxxxxxxx>
• RAID6 seemingly shrunk itself after hard power outage and rebuild with replacement disk
  • From: "Robin H. Johnson" <robbat2@xxxxxxxxxx>
• Re: [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: Andrew Patterson <andrew.patterson@xxxxxx>
• Reshape restart questions.
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: mdadm ddf questions
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• RE: Impact of missing parameter during mdadm create
  • From: Ken Drummond <linuxraid@xxxxxxxxxxxxxxx>
• Re: ideas - raid write
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• RE: Impact of missing parameter during mdadm create
  • From: Mike Viau <viaum@xxxxxxxxxxxxxxx>
• RE: Impact of missing parameter during mdadm create
  • From: Mike Viau <viaum@xxxxxxxxxxxxxxx>
• Re: ideas - raid write
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: ideas - raid write
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: ideas - raid write
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: ideas - raid write
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• ideas - raid write
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• RE: Impact of missing parameter during mdadm create
  • From: Ken Drummond <linuxraid@xxxxxxxxxxxxxxx>
• Re: Assembling RAID 5 array with missing superblock
  • From: Lasse Jensen <fafler@xxxxxxxxx>
• Re: Increasing maxsect of md devices?
  • From: Bart Kus <me@xxxxxxxx>
• Re: Increasing maxsect of md devices?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm ddf questions
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm ddf questions
  • From: NeilBrown <neilb@xxxxxxx>
• Increasing maxsect of md devices?
  • From: Bart Kus <me@xxxxxxxx>
• Re: mdadm ddf questions
  • From: NeilBrown <neilb@xxxxxxx>
• RE: Latency issues with MD-RAID
  • From: "Jansen, Frank" <fjansen@xxxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Drew <drew.kay@xxxxxxxxx>
• [PATCH] Enable error message in case of lack of spares for grow
  • From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
• Re: RAID10 Performance
  • From: "Mario 'BitKoenig' Holbe" <Mario.Holbe@xxxxxxxxxxxxx>
• Re: RAID10 Performance
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: RAID10 Performance
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• [PATCH 9/9] imsm: FIX: Variables declaration cleanup
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 8/9] FIX: Block array monitoring when assembling reshaped array
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 7/9] FIX: Set 'new' geometry when assembling reshaped array
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 6/9] FIX: Verify Backup file name before reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 5/9] FIX: Continue reshape in the background
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/9] FIX: Array during reshape cannot be configured
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 4/9] imsm: FIX: After checkpoint mark array have to be clean
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 3/9] imsm: FIX: Return blocks_per unit for general migration
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/9] FIX: Do not configure and start, already started reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/9] Grow_continue() - single array.
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: RAID10 Performance
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID10 Performance
  • From: Keld Jørn Simonsen <keld@xxxxxxxxxx>
• Re: RAID10 Performance
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• RAID10 Performance
  • From: Aaron Sowry <aaron@xxxxxxxxx>
• RAID10 Performance
  • From: Aaron Sowry <aaron@xxxxxxxxx>
• RE: [PATCH 0/5] Grow_continue() prepare for usage in assembly
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• RE: [PATCH 0/7] Grow_continue, use in assembly (cont.)
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• RE: [PATCH 3/7] FIX: configure disks slot for expansion
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• RE: [PATCH 1/7] FIX: Verify Backup file name before reshape
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• RE: [PATCH 0/5] Grow_continue() prepare for usage in assembly
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Failed RAID 6 array advice
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Failed RAID 6 array advice
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Failed RAID 6 array advice
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: [PATCH 0/7] Grow_continue, use in assembly (cont.)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/7] FIX: configure disks slot for expansion
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/7] FIX: reshape in md should wait for monitoring process (external metadata)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/7] FIX: Verify Backup file name before reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/5] Grow_continue() prepare for usage in assembly
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Latency issues with MD-RAID
  • From: NeilBrown <neilb@xxxxxxx>
• Latency issues with MD-RAID
  • From: "Jansen, Frank" <fjansen@xxxxxxxxxxxxxxxx>
• RE: Impact of missing parameter during mdadm create
  • From: Mike Viau <viaum@xxxxxxxxxxxxxxx>
• [PATCH 7/7] FIX: array is frozen after reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 5/7] FIX: Block monitor when starting array with reshape in progress
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 6/7] Continue reshape after assembling array
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 4/7] Add block_subarray()
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 3/7] FIX: configure disks slot for expansion
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/7] FIX: reshape in md should wait for monitoring process (external metadata)
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/7] FIX: Verify Backup file name before reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/7] Grow_continue, use in assembly (cont.)
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• RE: Impact of missing parameter during mdadm create
  • From: Mike Viau <viaum@xxxxxxxxxxxxxxx>
• Impact of missing parameter during mdadm create
  • From: Mike Viau <viaum@xxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PATCH 5/5] FIX: Do not configure and start, already started reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 4/5] FIX: Continue reshape in the background
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 3/5] FIX: Set readonly state in Grow_continue() when necessary
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/5] FIX: Pass container name to reshape array for external meta data
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/5] FIX: Spelling error in dprintf output
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/5] Grow_continue() prepare for usage in assembly
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• [PATCH] Warn the user about too small array size
  • From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
• RE: [PATCH 0/3] Continue expansion after reboot
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Ed W <lists@xxxxxxxxxxxxxx>
• Re: high throughput storage server? GPFS w/ 10GB/s throughput to the rescue
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: stripe cache question
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: OK, Now this is really weird
  • From: NeilBrown <neilb@xxxxxxx>
• RE: OK, Now this is really weird
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• RE: OK, Now this is really weird
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: [PATCH 0/3] Continue expansion after reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: stripe cache question
  • From: NeilBrown <neilb@xxxxxxx>
• RE: Removed drive from mdadm raid 5 array after reboot
  • From: Mike Viau <viaum@xxxxxxxxxxxxxxx>
• Re: high throughput storage server? GPFS w/ 10GB/s throughput to the rescue
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: high throughput storage server? GPFS w/ 10GB/s throughput to the rescue
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: OK, Now this is really weird
  • From: NeilBrown <neilb@xxxxxxx>
• Re: OK, Now this is really weird
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• RE: OK, Now this is really weird
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: stripe cache question
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: OK, Now this is really weird
  • From: Jeff Woods <jeff@xxxxxxxxxxxx>
• OK, Now this is really weird
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: mdadm ddf questions
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: auto-read-only question
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• [PATCH] Partitions could be meaningful on single-drive RAID0
  • From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
• auto-read-only question
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• RE: [PATCH 0/3] Continue expansion after reboot
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• [PATCH] FIX: imsm: OROM does not recognize degraded arrays (V2)
  • From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
• RE: [PATCH] FIX: imsm: OROM does not recognize degraded arrays
  • From: "Wojcik, Krzysztof" <krzysztof.wojcik@xxxxxxxxx>
• Re: [PULL REQUEST] md and related patches for 2.6.38
  • From: NeilBrown <neilb@xxxxxxx>
• Re: high throughput storage server?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: stripe cache question
  • From: NeilBrown <neilb@xxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: failed drive in raid 1 array
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: failed drive in raid 1 array
  • From: Roberto Nunnari <roberto.nunnari@xxxxxxxx>
• Re: failed drive in raid 1 array
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: failed drive in raid 1 array
  • From: Iordan Iordanov <iordan@xxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: [BUG 2.6.32] md/raid1: barrier disabling does not work correctly in all cases
  • From: Paul Clements <paul.clements@xxxxxxxxxxx>
• stripe cache question
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: high throughput storage server?
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Zdenek Kaspar <zkaspar82@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: high throughput storage server?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: [PULL REQUEST] md and related patches for 2.6.38
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: failed drive in raid 1 array
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: [PATCH] FIX: imsm: OROM does not recognize degraded arrays
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Assembling RAID 5 array with missing superblock
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• [PATCH] FIX: imsm: OROM does not recognize degraded arrays
  • From: Krzysztof Wojcik <krzysztof.wojcik@xxxxxxxxx>
• Re: Assembling RAID 5 array with missing superblock
  • From: Iordan Iordanov <iordan@xxxxxxxxxxxxxxx>
• Re: failed drive in raid 1 array
  • From: Iordan Iordanov <iordan@xxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• -Y option patch
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: high throughput storage server?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Assembling RAID 5 array with missing superblock
  • From: Lasse Jensen <fafler@xxxxxxxxx>
• Re: [PULL REQUEST] md and related patches for 2.6.38
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PULL REQUEST] md and related patches for 2.6.38
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: Likely forced assemby with wrong disk during raid5 grow. Recoverable?
  • From: Claude Nobs <claudenobs@xxxxxxxxx>
• Re: high throughput storage server?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: failing a drive while RAID5 is initializing
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: failed drive in raid 1 array
  • From: Roberto Nunnari <roberto.nunnari@xxxxxxxx>
• Re: failing a drive while RAID5 is initializing
  • From: Iordan Iordanov <iordan@xxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: failed drive in raid 1 array
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: failed drive in raid 1 array
  • From: Roberto Nunnari <roberto.nunnari@xxxxxxxx>
• Re: failed drive in raid 1 array
  • From: Roberto Nunnari <roberto.nunnari@xxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Assembling RAID 5 array with missing superblock
  • From: Jaap Crezee <jaap@xxxxxx>
• Re: failed drive in raid 1 array
  • From: Albert Pauw <albert.pauw@xxxxxxxx>
• Re: failed drive in raid 1 array
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: failed drive in raid 1 array
  • From: Roberto Nunnari <roberto.nunnari@xxxxxxxx>
• Re: failed drive in raid 1 array
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• failed drive in raid 1 array
  • From: Roberto Nunnari <roberto.nunnari@xxxxxxxx>
• Re: failing a drive while RAID5 is initializing
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: removing AHCI SATA devices
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• failing a drive while RAID5 is initializing
  • From: Iordan Iordanov <iordan@xxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• [PATCH 4/4] TBD: continue reshape after assembling array
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 3/4] FIX: Block monitor when starting array with reshape in progress
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/4] FIX: Prevent reshape auto start during assembly for external metadata
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/4] FIX: disks added beyond array should be counted during reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/4] Prepare assembled array for reshape (expansion)
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: high throughput storage server?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Assembling RAID 5 array with missing superblock
  • From: Lasse Jensen <fafler@xxxxxxxxx>
• Re: high throughput storage server?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: removing AHCI SATA devices
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: removing AHCI SATA devices
  • From: hansbkk@xxxxxxxxx
• Re: [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: NeilBrown <neilb@xxxxxxx>
• RE: [PATCH 0/3] Continue expansion after reboot
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• RE: [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: removing AHCI SATA devices
  • From: Simon McNair <simonmcnair@xxxxxxxxx>
• Re: mdadm ddf questions
  • From: NeilBrown <neilb@xxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: md road-map: 2011
  • From: Daniel Reurich <daniel@xxxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] Continue expansion after reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Single-drive RAID0
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Likely forced assemby with wrong disk during raid5 grow. Recoverable?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Likely forced assemby with wrong disk during raid5 grow. Recoverable?
  • From: Claude Nobs <claudenobs@xxxxxxxxx>
• Re: Two questions about stripe_cache_size
  • From: "Patrick J. LoPresti" <lopresti@xxxxxxxxx>
• Re: Two questions about stripe_cache_size
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Two questions about stripe_cache_size
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Two questions about stripe_cache_size
  • From: "Patrick J. LoPresti" <lopresti@xxxxxxxxx>
• Re: Two questions about stripe_cache_size
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Two questions about stripe_cache_size
  • From: NeilBrown <neilb@xxxxxxx>
• Two questions about stripe_cache_size
  • From: "Patrick J. LoPresti" <lopresti@xxxxxxxxx>
• Re: removing AHCI SATA devices
  • From: Jeff Garzik <jeff@xxxxxxxxxx>
• Re: raid10 - without stripe
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: raid10 - without stripe
  • From: NeilBrown <neilb@xxxxxxx>
• raid10 - without stripe
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Linux software RAID assistance
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Linux software RAID assistance
  • From: Simon McNair <simonmcnair@xxxxxxxxx>
• Re: Linux software RAID assistance
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Linux software RAID assistance
  • From: Simon Mcnair <simonmcnair@xxxxxxxxx>
• Re: Linux software RAID assistance
  • From: Simon Mcnair <simonmcnair@xxxxxxxxx>
• Re: Single-drive RAID0
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• removing AHCI SATA devices
  • From: Simon Mcnair <simonmcnair@xxxxxxxxx>
• Combining RAID6 and mdadm RAID10?
  • From: hansbkk@xxxxxxxxx
• [PATCH 3/3] FIX: Assemble device in reshape state with new disks number
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/3] imsm: FIX: Report correct array size during reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/3] imsm: FIX: initalize reshape progress as it is stored in metatdata
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/3] Continue expansion after reboot
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: Possible availability improvement
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Possible availability improvement
  • From: Michał Sawicz <michal@xxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: high throughput storage server?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• RE: Single-drive RAID0
  • From: "Wojcik, Krzysztof" <krzysztof.wojcik@xxxxxxxxx>
• Re: high throughput storage server?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: high throughput storage server?
  • From: Mattias Wadenstein <maswan@xxxxxxxxxx>
• Re: high throughput storage server?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: mdadm ddf questions
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: SSD - TRIM command
  • From: NeilBrown <neilb@xxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• RE: SSD - TRIM command
  • From: "Guy Watkins" <linux-raid@xxxxxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: SSD - TRIM command
  • From: "Eric D. Mudama" <edmudama@xxxxxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Single-drive RAID0
  • From: NeilBrown <neilb@xxxxxxx>
• Re: SSD - TRIM command
  • From: "Eric D. Mudama" <edmudama@xxxxxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: "Eric D. Mudama" <edmudama@xxxxxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Brendan Conoboy <blc@xxxxxxxxxx>
• Re: [PATCH] set default chunk in validate_geometry
  • From: NeilBrown <neilb@xxxxxxx>
• Re: SSD - TRIM command
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: SSD - TRIM command
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: New machine, new RAID, wrong device name...
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: New machine, new RAID, wrong device name...
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: SSD - TRIM command
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: SSD - TRIM command
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• [PATCH] RAID-6 check standalone
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: SSD - TRIM command
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• New machine, new RAID, wrong device name...
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: [PATCH] Fix over-zealous flush_disk when changing device size.
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: SSD - TRIM command
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: SSD - TRIM command
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• RE: Single-drive RAID0
  • From: "Wojcik, Krzysztof" <krzysztof.wojcik@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Mattias Wadenstein <maswan@xxxxxxxxxx>
• [PATCH] set default chunk in validate_geometry
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• Re: high throughput storage server?
  • From: Mattias Wadenstein <maswan@xxxxxxxxxx>
• Re: [PATCH 1/2] modified message on failure to read metadata in Manage
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Single-drive RAID0
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Likely forced assemby with wrong disk during raid5 grow. Recoverable?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Likely forced assemby with wrong disk during raid5 grow. Recoverable?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Linux software RAID assistance
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Linux software RAID assistance
  • From: Simon Mcnair <simonmcnair@xxxxxxxxx>
• Re: Linux software RAID assistance
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Linux software RAID assistance
  • From: Simon Mcnair <simonmcnair@xxxxxxxxx>
• Re: Linux software RAID assistance
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Likely forced assemby with wrong disk during raid5 grow. Recoverable?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Likely forced assemby with wrong disk during raid5 grow. Recoverable?
  • From: Claude Nobs <claudenobs@xxxxxxxxx>
• Re: Raid selection questions (10 vs 6, n2 vs f2) on an 8 drive array
  • From: Simon Mcnair <simonmcnair@xxxxxxxxx>
• Re: Linux software RAID assistance
  • From: Simon Mcnair <simonmcnair@xxxxxxxxx>
• Re: Possible HDD error, how do I find which HDD it is?
  • From: Simon Mcnair <simonmcnair@xxxxxxxxx>
• Re: Likely forced assemby with wrong disk during raid5 grow. Recoverable?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Possible HDD error, how do I find which HDD it is?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Likely forced assemby with wrong disk during raid5 grow. Recoverable?
  • From: Claude Nobs <claudenobs@xxxxxxxxx>
• Re: Possible HDD error, how do I find which HDD it is?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Possible HDD error, how do I find which HDD it is?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Possible HDD error, how do I find which HDD it is?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Possible HDD error, how do I find which HDD it is?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Possible HDD error, how do I find which HDD it is?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Possible HDD error, how do I find which HDD it is?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Possible HDD error, how do I find which HDD it is?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Possible HDD error, how do I find which HDD it is?
  • From: Phil Turmel <philip@xxxxxxxxxx>