Linux RAID Storage Date Index

• Thread Index

• Re: mdadm expanded 8 disk raid 6 fails in new server, 5 original devices show no md superblock
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: livelock during MD device open
  • From: Nicolas Schichan <nschichan@xxxxxxxxxx>
• Re: mdadm expanded 8 disk raid 6 fails in new server, 5 original devices show no md superblock
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• [GIT PULL REQUEST] last minute md fixes for 3.13
  • From: NeilBrown <neilb@xxxxxxx>
• Re: livelock during MD device open
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm expanded 8 disk raid 6 fails in new server, 5 original devices show no md superblock
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: mdadm expanded 8 disk raid 6 fails in new server, 5 original devices show no md superblock
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• livelock during MD device open
  • From: Nicolas Schichan <nschichan@xxxxxxxxxx>
• Re: After RAID0 grow: inconsistent superblocks and /proc/mdstat
  • From: Richard Michael <rmichael@xxxxxxxxxxxxxxxx>
• Re: [RFC v2 0/2] New RAID library supporting up to six parities
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• AW: mdadm expanded 8 disk raid 6 fails in new server, 5 original devices show no md superblock
  • From: Großkreutz, Julian <Julian.Grosskreutz@xxxxxxxxxxxxxxx>
• Re: mdadm expanded 8 disk raid 6 fails in new server, 5 original devices show no md superblock
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: mdadm expanded 8 disk raid 6 fails in new server, 5 original devices show no md superblock
  • From: Großkreutz, Julian <Julian.Grosskreutz@xxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid5: Add compensation in sysfs for raid456.
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: RAID 10 far and offset on-disk layouts
  • From: keld@xxxxxxxxxx
• Re: RAID 10 far and offset on-disk layouts
  • From: keld@xxxxxxxxxx
• Re: RAID 10 far and offset on-disk layouts
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: [RFC v2 0/2] New RAID library supporting up to six parities
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: RAID 10 far and offset on-disk layouts
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID 10 far and offset on-disk layouts
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Recovering an Array with inconsistent Superblocks
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: After RAID0 grow: inconsistent superblocks and /proc/mdstat
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md/raid5: Add compensation in sysfs for raid456.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: RAID 10 far and offset on-disk layouts
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID 10 far and offset on-disk layouts
  • From: keld@xxxxxxxxxx
• Re: RAID 10 far and offset on-disk layouts
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm expanded 8 disk raid 6 fails in new server, 5 original devices show no md superblock
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: mdadm expanded 8 disk raid 6 fails in new server, 5 original devices show no md superblock
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 10 far and offset on-disk layouts
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: RAID 10 far and offset on-disk layouts
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID 10 far and offset on-disk layouts
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: After RAID0 grow: inconsistent superblocks and /proc/mdstat
  • From: Richard Michael <rmichael@xxxxxxxxxxxxxxxx>
• Re: After RAID0 grow: inconsistent superblocks and /proc/mdstat
  • From: NeilBrown <neilb@xxxxxxx>
• Re: After RAID0 grow: inconsistent superblocks and /proc/mdstat
  • From: Richard Michael <rmichael@xxxxxxxxxxxxxxxx>
• After RAID0 grow: inconsistent superblocks and /proc/mdstat
  • From: Richard Michael <rmichael@xxxxxxxxxxxxxxxx>
• Re: RAID 10 far and offset on-disk layouts
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Why 4k native drives haven't arrived
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Why 4k native drives haven't arrived
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Why 4k native drives haven't arrived
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Why 4k native drives haven't arrived
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Why 4k native drives haven't arrived
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: read errors not corrected when doing check on RAID6
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: read errors not corrected when doing check on RAID6
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: read errors not corrected when doing check on RAID6
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Why 4k native drives haven't arrived
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• read errors not corrected when doing check on RAID6
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Why 4k native drives haven't arrived
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: mdadm expanded 8 disk raid 6 fails in new server, 5 original devices show no md superblock
  • From: Phil Turmel <philip@xxxxxxxxxx>
• mdadm expanded 8 disk raid 6 fails in new server, 5 original devices show no md superblock
  • From: Großkreutz, Julian <Julian.Grosskreutz@xxxxxxxxxxxxxxx>
• Re: MD on raw device, use unallocated space anyway?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: MD on raw device, use unallocated space anyway?
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: MD on raw device, use unallocated space anyway?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: MD on raw device, use unallocated space anyway?
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: MD on raw device, use unallocated space anyway?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: MD on raw device, use unallocated space anyway?
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• MD on raw device, use unallocated space anyway?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• [RFC v3 2/3] fs: btrfs: Extends btrfs/raid56 to support up to six parities
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• [RFC v3 3/3] crypto: async_tx: Extends crypto/async_tx to support up to six parities
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• [RFC v3 0/3] New RAID library supporting up to six parities
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Why 4k native drives haven't arrived
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• [PATCH -next] bcache: Fix sparse non static symbol warning
  • From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
• Re: RAID 10 far and offset on-disk layouts
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Can raid1-resync cause a corruption?
  • From: NeilBrown <neilb@xxxxxxx>
• Copying Data off a Failed RAID
  • From: Fred Damstra <fred.damstra@xxxxxxxxx>
• Re: RAID6 reshape integer problem
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: RAID6 reshape integer problem
  • From: Piotr Klimek <piotr@xxxxxxxxxxxxx>
• Re: What can be used instead of /dev/disk/by-path/* symlinks?
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: looking for advice on raid0+raid5 array recovery with mdadm and sector offset
  • From: den Hoog <speedyden@xxxxxxxxx>
• write-mostly
  • From: Marcus Sorensen <shadowsor@xxxxxxxxx>
• Re: Can raid1-resync cause a corruption?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• QNAP 8 port RAID5 md0 unmountable defective md superblocks
  • From: Michael Samer <michael.samer@xxxxxxxxxxx>
• Re: [RFC v2 0/2] New RAID library supporting up to six parities
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: [RFC v2 0/2] New RAID library supporting up to six parities
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: [RFC v2 0/2] New RAID library supporting up to six parities
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: [RFC v2 2/2] fs: btrfs: Extends btrfs/raid56 to support up to six parities
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: [RFC] lib: raid: New RAID library supporting up to six parities
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: [RFC] lib: raid: New RAID library supporting up to six parities
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovering an Array with inconsistent Superblocks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: More 'D' state processes [was: Re: Weird problem: mdadm blocks]
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Can raid1-resync cause a corruption?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Why 4k native drives haven't arrived
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Why 4k native drives haven't arrived
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: raid5: R5_WriteError is not cleared after rdev is marked as Faulty
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC v2 0/2] New RAID library supporting up to six parities
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: [RFC v2 0/2] New RAID library supporting up to six parities
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [RFC v2 0/2] New RAID library supporting up to six parities
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Can raid1-resync cause a corruption?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Looking for some advice on best way to identify drives / recover from issues
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Looking for some advice on best way to identify drives / recover from issues
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [RFC v2 0/2] New RAID library supporting up to six parities
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• Re: [RFC v2 0/2] New RAID library supporting up to six parities
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• Re: [RFC v2 0/2] New RAID library supporting up to six parities
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: raid5: R5_WriteError is not cleared after rdev is marked as Faulty
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [RFC v2 2/2] fs: btrfs: Extends btrfs/raid56 to support up to six parities
  • From: Chris Mason <clm@xxxxxx>
• Re: Recovering an Array with inconsistent Superblocks
  • From: Fabian Knorr <knorrfab@xxxxxxxxxxxxxxxxx>
• Re: [RFC v2 0/2] New RAID library supporting up to six parities
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• Re: [RFC v2 0/2] New RAID library supporting up to six parities
  • From: joystick <joystick@xxxxxxxxxxxxx>
• [RFC v2 2/2] fs: btrfs: Extends btrfs/raid56 to support up to six parities
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• [RFC v2 0/2] New RAID library supporting up to six parities
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: looking for advice on raid0+raid5 array recovery with mdadm and sector offset
  • From: den Hoog <speedyden@xxxxxxxxx>
• Re: [PATCH] policy: NULL path isn't really acceptable - use the devname
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid5: R5_WriteError is not cleared after rdev is marked as Faulty
  • From: NeilBrown <neilb@xxxxxxx>
• Re: looking for advice on raid0+raid5 array recovery with mdadm and sector offset
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovering an Array with inconsistent Superblocks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: More 'D' state processes [was: Re: Weird problem: mdadm blocks]
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Looking for some advice on best way to identify drives / recover from issues
  • From: Krzysztof Adamski <k@xxxxxxxxxxx>
• Re: Why 4k native drives haven't arrived
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Looking for some advice on best way to identify drives / recover from issues
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Recovering an Array with inconsistent Superblocks
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Looking for some advice on best way to identify drives / recover from issues
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Looking for some advice on best way to identify drives / recover from issues
  • From: Dylan Distasio <interzone@xxxxxxxxx>
• Re: Looking for some advice on best way to identify drives / recover from issues
  • From: Dylan Distasio <interzone@xxxxxxxxx>
• Re: Looking for some advice on best way to identify drives / recover from issues
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Looking for some advice on best way to identify drives / recover from issues
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Looking for some advice on best way to identify drives / recover from issues
  • From: Dylan Distasio <interzone@xxxxxxxxx>
• Re: Recovering an Array with inconsistent Superblocks
  • From: Fabian Knorr <knorrfab@xxxxxxxxxxxxxxxxx>
• Re: Recovering an Array with inconsistent Superblocks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovering an Array with inconsistent Superblocks
  • From: Fabian Knorr <knorrfab@xxxxxxxxxxxxxxxxx>
• Re: Recovering an Array with inconsistent Superblocks
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Recovering an Array with inconsistent Superblocks
  • From: Fabian Knorr <knorrfab@xxxxxxxxxxxxxxxxx>
• Re: Recovering an Array with inconsistent Superblocks
  • From: Fabian Knorr <knorrfab@xxxxxxxxxxxxxxxxx>
• Re: Recovering an Array with inconsistent Superblocks
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Why 4k native drives haven't arrived
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Recovering an Array with inconsistent Superblocks
  • From: Can Jeuleers <can.jeuleers@xxxxxxxxx>
• Re: 'resync=PENDING', 'auto-read-only' on raid1 creation
  • From: Ron Leach <ronleach@xxxxxxxxx>
• Re: 'resync=PENDING', 'auto-read-only' on raid1 creation
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: 'resync=PENDING', 'auto-read-only' on raid1 creation
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Recovering an Array with inconsistent Superblocks
  • From: Phil Turmel <philip@xxxxxxxxxx>
• 'resync=PENDING', 'auto-read-only' on raid1 creation
  • From: Ron Leach <ronleach@xxxxxxxxx>
• Recovering an Array with inconsistent Superblocks
  • From: Fabian Knorr <knorrfab@xxxxxxxxxxxxxxxxx>
• Re: Why 4k native drives haven't arrived
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: RAID6 reshape integer problem
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: The chunk size paradox
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: RAID6 reshape integer problem
  • From: Piotr Klimek <piotr@xxxxxxxxxxxxx>
• Re: RAID6 reshape integer problem
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Why 4k native drives haven't arrived
  • From: Dimitri John Ledkov <xnox@xxxxxxxxxx>
• Re: Why 4k native drives haven't arrived
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• RAID6 reshape integer problem
  • From: Piotr Klimek <piotr@xxxxxxxxxxxxx>
• Re: The chunk size paradox
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: The chunk size paradox
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: The chunk size paradox
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: The chunk size paradox
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: The chunk size paradox
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Why 4k native drives haven't arrived
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: The chunk size paradox
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: The chunk size paradox
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: The chunk size paradox
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: The chunk size paradox
  • From: pg@xxxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: The chunk size paradox
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: The chunk size paradox
  • From: Carsten Aulbert <Carsten.Aulbert@xxxxxxxxxx>
• Re: The chunk size paradox
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: The chunk size paradox
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: The chunk size paradox
  • From: Wolfgang Denk <wd@xxxxxxx>
• [RFC PATCHv3 04/11] dm: Use VMALLOC_TOTAL instead of VMALLCO_END - VMALLOC_START
  • From: Laura Abbott <lauraa@xxxxxxxxxxxxxx>
• Re: The chunk size paradox
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Is partition alignment needed for RAID partitions ?
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• looking for advice on raid0+raid5 array recovery with mdadm and sector offset
  • From: den Hoog <speedyden@xxxxxxxxx>
• Re: The chunk size paradox
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: The chunk size paradox
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: The chunk size paradox
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Can raid1-resync cause a corruption?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: The chunk size paradox
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• raid5: R5_WriteError is not cleared after rdev is marked as Faulty
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: The chunk size paradox
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: The chunk size paradox
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re:: Can raid1-resync cause a corruption?
  • From: Jack Wang <xjtuwjp@xxxxxxxxx>
• Re: The chunk size paradox
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: How to prefer some devices over others in raid
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Looking for help how to migrate 2disk RAID1 to 3 disk RAID6
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• Re: How to prefer some devices over others in raid
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: How to prefer some devices over others in raid
  • From: Tomas M <tomas@xxxxxxxx>
• Re: How to prefer some devices over others in raid
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Looking for help how to migrate 2disk RAID1 to 3 disk RAID6
  • From: Krzysztof Adamski <k-list@xxxxxxxxxxx>
• Re: Looking for help how to migrate 2disk RAID1 to 3 disk RAID6
  • From: Krzysztof Adamski <k-list@xxxxxxxxxxx>
• Re: Looking for help how to migrate 2disk RAID1 to 3 disk RAID6
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• Re: Looking for help how to migrate 2disk RAID1 to 3 disk RAID6
  • From: Tomas M <tomas@xxxxxxxx>
• Re: How to prefer some devices over others in raid
  • From: NeilBrown <neilb@xxxxxxx>
• Re: How to prefer some devices over others in raid
  • From: Tomas M <tomas@xxxxxxxx>
• Re: Looking for help how to migrate 2disk RAID1 to 3 disk RAID6
  • From: Krzysztof Adamski <k-list@xxxxxxxxxxx>
• Re: Looking for help how to migrate 2disk RAID1 to 3 disk RAID6
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• Looking for help how to migrate 2disk RAID1 to 3 disk RAID6
  • From: Krzysztof Adamski <k-list@xxxxxxxxxxx>
• Re: How to prefer some devices over others in raid
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• How to prefer some devices over others in raid
  • From: Tomas M <tomas@xxxxxxxx>
• Re: Is partition alignment needed for RAID partitions ?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Is partition alignment needed for RAID partitions ?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: The chunk size paradox
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Is partition alignment needed for RAID partitions ?
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• Re: The chunk size paradox
  • From: Wolfgang Denk <wd@xxxxxxx>
• Re: The chunk size paradox
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• The chunk size paradox
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Is partition alignment needed for RAID partitions ?
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• Re: Is partition alignment needed for RAID partitions ?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Doesn't "writes" do what resync does ?
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• Re: Is partition alignment needed for RAID partitions ?
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• Re: Doesn't "writes" do what resync does ?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Is partition alignment needed for RAID partitions ?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Intel Matrix raid recovery with 2 raid volumes in the array
  • From: den Hoog <speedyden@xxxxxxxxx>
• Re: Doesn't "writes" do what resync does ?
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• Re: Is partition alignment needed for RAID partitions ?
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• Re: Doesn't "writes" do what resync does ?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Is partition alignment needed for RAID partitions ?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Doesn't "writes" do what resync does ?
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• Re: Can raid1-resync cause a corruption?
  • From: NeilBrown <neilb@xxxxxxx>
• Is partition alignment needed for RAID partitions ?
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• Re: raid 6 4 disk failure, improper --create leads to bad superblock
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Can raid1-resync cause a corruption?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• raid 6 4 disk failure, improper --create leads to bad superblock
  • From: Cooper tron <cooper@xxxxxxxx>
• Re: RAID 10 far and offset on-disk layouts
  • From: keld@xxxxxxxxxx
• Re: RAID 10 far and offset on-disk layouts
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: RAID 10 far and offset on-disk layouts
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: RAID 10 far and offset on-disk layouts
  • From: keld@xxxxxxxxxx
• Re: RAID 10 far and offset on-disk layouts
  • From: keld@xxxxxxxxxx
• Re: RAID 10 far and offset on-disk layouts
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: RAID 10 far and offset on-disk layouts
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: RAID 10 far and offset on-disk layouts
  • From: pg@xxxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• RAID 10 far and offset on-disk layouts
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Low resync throughput
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: raid10 offset distance
  • From: pg@xxxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Low resync throughput
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• raid10 offset distance
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• thank you!
  • From: "N Laszlo Frazer" <laszlo@xxxxxxxxxxxxxxxx>
• Re: md-RAID5/6 stripe_cache_size default value vs performance vs memory footprint
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md-RAID5/6 stripe_cache_size default value vs performance vs memory footprint
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: md-RAID5/6 stripe_cache_size default value vs performance vs memory footprint
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• More 'D' state processes [was: Re: Weird problem: mdadm blocks]
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: Weird problem: mdadm blocks
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: Weird problem: mdadm blocks
  • From: NeilBrown <neilb@xxxxxxx>
• Weird problem: mdadm blocks
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: md-RAID5/6 stripe_cache_size default value vs performance vs memory footprint
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: md-RAID5/6 stripe_cache_size default value vs performance vs memory footprint
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• md-RAID5/6 stripe_cache_size default value vs performance vs memory footprint
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: mdadm, spin down never happens, do spare work the same?
  • From: NeilBrown <neilb@xxxxxxx>
• mdadm, spin down never happens, do spare work the same?
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: Is it possible to create a raid from/over other raids?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Is it possible to create a raid from/over other raids?
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• RE: [PATCH] policy: NULL path isn't really acceptable - use the devname
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• [PATCH] policy: NULL path isn't really acceptable - use the devname
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: Is it possible to create a raid from/over other raids?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Is it possible to create a raid from/over other raids?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Is it possible to create a raid from/over other raids?
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Is it possible to create a raid from/over other raids?
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: Chunk size change stop/restart
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Help with degraded array
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: request help with RAID1 array that endlessly attempts to sync
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Fwd: raid5 + dm-crypt WRITE perf., higher rrqm/s - kernel 3.10.16
  • From: Redwood Hyd <redwoodhyd@xxxxxxxxx>
• Re: request help with RAID1 array that endlessly attempts to sync
  • From: Julie Ashworth <ashworth@xxxxxxxxxxxx>
• Re: request help with RAID1 array that endlessly attempts to sync
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: mdadm error
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Chunk size change stop/restart
  • From: NeilBrown <neilb@xxxxxxx>
• Re: request help with RAID1 array that endlessly attempts to sync
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: request help with RAID1 array that endlessly attempts to sync
  • From: Julie Ashworth <ashworth@xxxxxxxxxxxx>
• Chunk size change stop/restart
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: request help with RAID1 array that endlessly attempts to sync
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: request help with RAID1 array that endlessly attempts to sync
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: request help with RAID1 array that endlessly attempts to sync
  • From: Julie Ashworth <ashworth@xxxxxxxxxxxx>
• Re: RAID 6 reads all remaining chunks in a stripe when a single chunk is rewritten
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: RAID 6 reads all remaining chunks in a stripe when a single chunk is rewritten
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 6 reads all remaining chunks in a stripe when a single chunk is rewritten
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: What can be used instead of /dev/disk/by-path/* symlinks?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• RAID 6 reads all remaining chunks in a stripe when a single chunk is rewritten
  • From: Nikolaus Jeremic <jeremic@xxxxxxxxxxxxxxxxxxxxxxxxx>
• RE: What can be used instead of /dev/disk/by-path/* symlinks?
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• RE: What can be used instead of /dev/disk/by-path/* symlinks?
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: What can be used instead of /dev/disk/by-path/* symlinks?
  • From: Dimitri John Ledkov <xnox@xxxxxxxxxx>
• Re: What can be used instead of /dev/disk/by-path/* symlinks?
  • From: NeilBrown <neilb@xxxxxxx>
• What can be used instead of /dev/disk/by-path/* symlinks?
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• raid5 + dm-crypt WRITE perf., higher rrqm/s - kernel 3.10.16
  • From: Redwood Hyd <redwoodhyd@xxxxxxxxx>
• request help with RAID1 array that endlessly attempts to sync
  • From: Julie Ashworth <ashworth@xxxxxxxxxxxx>
• Re: 答复：答复：two raid5 performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Help with degraded array
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• mdadm error
  • From: Michael Samer <michael.samer@xxxxxxxxxxx>
• Re: 答复：答复：two raid5 performance
  • From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
• Re: Using Video cards (CUDA) for RAID parity
  • From: Wolfgang Denk <wd@xxxxxxx>
• 答复：答复：答复：two raid5 performance
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: 答复：答复：two raid5 performance
  • From: Tommy Apel <tommyapeldk@xxxxxxxxx>
• 答复：答复：two raid5 performance
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: 答复：two raid5 performance
  • From: Tommy Apel <tommyapeldk@xxxxxxxxx>
• Re: 答复：two raid5 performance
  • From: Dag Nygren <dag@xxxxxxxxxx>
• 答复：答复：two raid5 performance
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: 答复：答复：答复：two raid5 performance
  • From: Tommy Apel <tommyapeldk@xxxxxxxxx>
• 答复：答复：答复：two raid5 performance
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: 答复：答复：two raid5 performance
  • From: Tommy Apel <tommyapeldk@xxxxxxxxx>
• 答复：答复：two raid5 performance
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: udev rule and systemd unit files and mdadm - cross distro.
  • From: Peter Rajnoha <prajnoha@xxxxxxxxxx>
• 答复：two raid5 performance
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: two raid5 performance
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• two raid5 performance
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• RAID 6 performs unnecessary reads when updating single chunk in a stripe
  • From: Nikolaus Jeremic <jeremic@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Help with degraded array
  • From: Ken Drummond <linuxraid@xxxxxxxxxxxxxxx>
• Re: Help with degraded array
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: [PATCH] drivers: md: Mark the function btree_insert_fn() as static in btree.c
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: Help with degraded array
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: Help with degraded array
  • From: Alex <mysqlstudent@xxxxxxxxx>
• [PATCH] drivers: md: Mark the function btree_insert_fn() as static in btree.c
  • From: Rashika Kheria <rashika.kheria@xxxxxxxxx>
• Re: Help with degraded array
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Help with degraded array
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: Using Video cards (CUDA) for RAID parity
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: Using Video cards (CUDA) for RAID parity
  • From: joystick <joystick@xxxxxxxxxxxxx>
• RE: Using Video cards (CUDA) for RAID parity
  • From: Chris Green <cgreen@xxxxxxxxxxxxxxxxx>
• Re: Using Video cards (CUDA) for RAID parity
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: Using Video cards (CUDA) for RAID parity
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• Re: [BUG,PATCH] raid1 behind write ordering (barrier) protection
  • From: Brett Russ <brett@xxxxxxxxxxxxxxxxxx>
• Re: Using Video cards (CUDA) for RAID parity
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Using Video cards (CUDA) for RAID parity
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Using Video cards (CUDA) for RAID parity
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• Re: VM virtual hard drive with build and debug all ready to go?
  • From: NeilBrown <neilb@xxxxxxx>
• VM virtual hard drive with build and debug all ready to go?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: [PATCH mdadm 1/1] Clarify scope of Rebuild events in mdadm manpage
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Ben Myers <bpm@xxxxxxx>
• Re: udev rule and systemd unit files and mdadm - cross distro.
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Rebuild events while scrubbing - problems or just informational?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Rebuild events while scrubbing - problems or just informational?
  • From: Can Jeuleers <can.jeuleers@xxxxxxxxx>
• udev rule and systemd unit files and mdadm - cross distro.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Rebuild events while scrubbing - problems or just informational?
  • From: NeilBrown <neilb@xxxxxxx>
• mdadm and the list appreciation
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: adding a missing drive(s), which drives get written to? a thank you.
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Rebuild events while scrubbing - problems or just informational?
  • From: Can Jeuleers <can.jeuleers@xxxxxxxxx>
• Re: adding a missing drive(s), which drives get written to?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Rebuild events while scrubbing - problems or just informational?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Rebuild events while scrubbing - problems or just informational?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: mdadm rebuild
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [SOLVED] Re: Raid1 where Event Count off my 1 cannot assemble --force
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: cgroups-blkio CFQ scheduling does not work well in a RAID5 configuration.
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: mdadm rebuild
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• replaced disk raid 5 array, after sync, missing file system and/or superblock
  • From: Niels Wassenberg <nielswassenberg@xxxxxx>
• Is mdadm guaranteed consistent after a sync/xfs_freeze?
  • From: Jon Eisenstein <eisenstein@xxxxxxxxx>
• adding a missing drive(s), which drives get written to?
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: How to assemble 4-disk raid5 with one broken disk and one marked as spare by operator error?
  • From: Tomas Agartz <tlund@xxxxxx>
• Re: cgroups-blkio CFQ scheduling does not work well in a RAID5 configuration.
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• Re: [SOLVED] Re: Raid1 where Event Count off my 1 cannot assemble --force
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [SOLVED] Re: Raid1 where Event Count off my 1 cannot assemble --force
  • From: NeilBrown <neilb@xxxxxxx>
• [SOLVED] Re: Raid1 where Event Count off my 1 cannot assemble --force
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: Raid1 where Event Count off my 1 cannot assemble --force
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid1 where Event Count off my 1 cannot assemble --force
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: How to assemble 4-disk raid5 with one broken disk and one marked as spare by operator error?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: unable to assemble (mostly?) clean array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid1 where Event Count off my 1 cannot assemble --force
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: Raid1 where Event Count off my 1 cannot assemble --force
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: unable to assemble (mostly?) clean array
  • From: Christopher Hoover <ch@xxxxxxxxxxxxxx>
• Re: Raid1 where Event Count off my 1 cannot assemble --force
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: unable to assemble (mostly?) clean array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: unable to assemble (mostly?) clean array
  • From: Christopher Hoover <ch@xxxxxxxxxxxxxx>
• Re: unable to assemble (mostly?) clean array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid1 where Event Count off my 1 cannot assemble --force
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid1 where Event Count off my 1 cannot assemble --force
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Raid1 where Event Count off my 1 cannot assemble --force
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: unable to assemble (mostly?) clean array
  • From: Christopher Hoover <ch@xxxxxxxxxxxxxx>
• Re: mdadm rebuild
  • From: NeilBrown <neilb@xxxxxxx>
• Re: unable to assemble (mostly?) clean array
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Re: mdadm rebuild
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: unable to assemble (mostly?) clean array
  • From: NeilBrown <neilb@xxxxxxx>
• unable to assemble (mostly?) clean array
  • From: Christopher Hoover <ch@xxxxxxxxxxxxxx>
• Re: mdadm rebuild
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm rebuild
  • From: Hai Wu <haiwu.us@xxxxxxxxx>
• Re: mdadm rebuild
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm rebuild
  • From: NeilBrown <neilb@xxxxxxx>
• How to assemble 4-disk raid5 with one broken disk and one marked as spare by operator error?
  • From: Tomas Agartz <tlund@xxxxxx>
• Re: Raid1 where Event Count off my 1 cannot assemble --force
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• mdadm rebuild
  • From: Hai Wu <haiwu.us@xxxxxxxxx>
• Re: Raid1 where Event Count off my 1 cannot assemble --force
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Raid1 where Event Count off my 1 cannot assemble --force
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: mdadm fails to recognise DDF partitions from Marvell MV64460 controller
  • From: Patrick Smears <patrick@xxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: RAID-0/5/6 performances
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Creating new raid5 or 6 with --assume-clean
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: RAID-0/5/6 performances
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: mdadm fails to recognise DDF partitions from Marvell MV64460 controller
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID-0/5/6 performances
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• mdadm fails to recognise DDF partitions from Marvell MV64460 controller
  • From: Patrick Smears <patrick@xxxxxxxxxx>
• Idea: reduce SCST processes per LUN
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: Degraded array but drive healthy
  • From: Phill Watkins <phill.watkins@xxxxxxxxx>
• Re: RAID-0/5/6 performances
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: RAID-0/5/6 performances
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: RAID-0/5/6 performances
  • From: NeilBrown <neilb@xxxxxxx>
• RAID-0/5/6 performances
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• [PATCH] lib/raid6: fix preprocessor warning
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: accidently pulled to many devices, raid6 wont start.
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: accidently pulled to many devices, raid6 wont start.
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
• Re: accidently pulled to many devices, raid6 wont start.
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: accidently pulled to many devices, raid6 wont start.
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
• Re: accidently pulled to many devices, raid6 wont start.
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: accidently pulled to many devices, raid6 wont start.
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: accidently pulled to many devices, raid6 wont start.
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
• Re: accidently pulled to many devices, raid6 wont start.
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: accidently pulled to many devices, raid6 wont start.
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
• Re: accidently pulled to many devices, raid6 wont start.
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• accidently pulled to many devices, raid6 wont start.
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: Degraded array but drive healthy
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Degraded array but drive healthy
  • From: Phill Watkins <phill.watkins@xxxxxxxxx>
• Re: raid5 rmmod bug oops
  • From: NeilBrown <neilb@xxxxxxx>
• raid5 rmmod bug oops
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: Growing array, duplicating data, shrinking array questions.
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Growing array, duplicating data, shrinking array questions.
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: dm-raid45?
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• Re: dm-raid45?
  • From: Tom Pfeifer <tpfeife1@xxxxxxxxx>
• Re: [BUG,PATCH] raid1 behind write ordering (barrier) protection
  • From: Brett Russ <brett@xxxxxxxxxxxxxxxxxx>
• Re: [BUG,PATCH] raid1 behind write ordering (barrier) protection
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [BUG,PATCH] raid1 behind write ordering (barrier) protection
  • From: Brett Russ <brett@xxxxxxxxxxxxxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Thanks Neil
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: Raid10 multi core scaling
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Creating new raid5 or 6 with --assume-clean
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Raid10 multi core scaling
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Raid10 multi core scaling
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm No md superblock detected
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [BUG]NULL Pointer dereference in rdev_set_badblocks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md raid5 performace 6x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• md raid5 performace 6x SSD RAID5
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Creating new raid5 or 6 with --assume-clean
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: md raid5 random performace 6x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Richard Scobie <r.scobie@xxxxxxxxxxxx>
• md raid5 random performace 6x SSD RAID5
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: 答复：答复：答复：md raid5 random performace 6x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Thanks Neil
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Thanks Neil
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Thanks Neil
  • From: Digimer <lists@xxxxxxxxxx>
• Thanks Neil
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Growing array, duplicating data, shrinking array questions.
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• 答复：答复：答复：md raid5 random performace 6x SSD RAID5
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• mdadm No md superblock detected
  • From: Teitur Ingi Sigurdsson <teitso@xxxxxxxxx>
• Re: /proc/mdstat status documentation and md: export_rdev
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: cgroups-blkio CFQ scheduling does not work well in a RAID5 configuration.
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• cgroups-blkio CFQ scheduling does not work well in a RAID5 configuration.
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• Re: 答复：答复：md raid5 performace 6x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: 答复：答复：md raid5 performace 6x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: /proc/mdstat status documentation and md: export_rdev
  • From: Can Jeuleers <can.jeuleers@xxxxxxxxx>
• Re: /proc/mdstat status documentation and md: export_rdev
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: [BUG]NULL Pointer dereference in rdev_set_badblocks
  • From: Jack Wang <jinpu.wang@xxxxxxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Jimmy Thrasibule <thrasibule.jimmy@xxxxxxxxx>
• 答复：答复：md raid5 performace 6x SSD RAID5
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• 答复：答复：md raid5 performace 6x SSD RAID5
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: 答复：md raid5 performace 6x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: 答复：md raid5 performace 6x SSD RAID5
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: 答复：md raid5 performace 6x SSD RAID5
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PATCH -next] bcache: fix sparse non static symbol warning
  • From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• 答复：md raid5 performace 6x SSD RAID5
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• md raid5 performace 6x SSD RAID5
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Raid10 multi core scaling
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: ronnie sahlberg <ronniesahlberg@xxxxxxxxx>
• Re: dm-raid45?
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: joystick <joystick@xxxxxxxxxxxxx>
• dm-raid45?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: [PATCH] Revert "raid5: make release_stripe lockless" because it causes test regression
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Raid10 multi core scaling
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Raid10 multi core scaling
  • From: Pedro Teixeira <finas@xxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• RAID Performance - 5x SSD RAID5
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Slow AVX XOR reported
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Pasi Kärkkäinen <pasik@xxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Jimmy Thrasibule <thrasibule.jimmy@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Stuck reshape
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• Re: md/raid5: Use conf->device_lock protect changing of multi-thread resources.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Revert "raid5: make release_stripe lockless" because it causes test regression
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Alex Elsayed <eternaleye@xxxxxxxxx>
• Re: Stuck reshape
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 1/1] MD/DM RAID: Fix hang due to recent RAID5 locking changes
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 0/1] Recent breakage of DM RAID
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Triple parity and beyond
  • From: Duncan <1i5t5.duncan@xxxxxxx>
• Stuck reshape
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] Revert "raid5: make release_stripe lockless" because it causes test regression
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• [PATCH] Revert "raid5: make release_stripe lockless" because it causes test regression
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: md/raid5: Use conf->device_lock protect changing of multi-thread resources.
  • From: Ben Hutchings <bhutchings@xxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Taylor <davidt@xxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: ARC-1120 and MD very sloooow
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• ARC-1120 and MD very sloooow
  • From: Jimmy Thrasibule <thrasibule.jimmy@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Russell Coker <russell@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• mdadm No md superblock detected
  • From: Teitur Ingi Sigurdsson <teitso@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• raid1 behind write ordering (barrier) protection
  • From: Brett Russ <brett@xxxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Growing array, duplicating data, shrinking array questions.
  • From: Wilson Jonathan <piercing_male@xxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Goffredo Baroncelli <kreijack@xxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Is there a tool to examine raw metadata?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: unused space before data offset mismatch
  • From: NeilBrown <neilb@xxxxxxx>
• Re: unused space before data offset mismatch
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: James Plank <plank@xxxxxxxxxx>
• unused space before data offset mismatch
  • From: kustep <kustep@xxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Is there a tool to examine raw metadata?
  • From: Veedar Hokstadt <veedar@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: James Plank <plank@xxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: John Williams <jwilliams4200@xxxxxxxxx>
• Re: dmaengine 3.13 v2
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: NeilBrown <neilb@xxxxxxx>
• [PULL REQUEST] md updates for 3.13
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Triple parity and beyond
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Triple parity and beyond
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Is my drive dying ?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Is my drive dying ?
  • From: Guillaume Betous <guillaume.betous@xxxxxxxxx>
• Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: Triple parity and beyond
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Triple parity and beyond
  • From: Andrea Mazzoleni <amadvance@xxxxxxxxx>
• Re: MDADM 3.3 broken?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Filesystem writes on RAID5 too slow
  • From: Eric Sandeen <sandeen@xxxxxxxxxx>
• MDADM 3.3 broken?
  • From: "David F." <df7729@xxxxxxxxx>
• Filesystem writes on RAID5 too slow
  • From: Martin Boutin <martboutin@xxxxxxxxx>
• mdadm: "reshape: not enough stripes. Needed 65536"
  • From: "Steven Rose [DATACOM]" <Steven.Rose@xxxxxxxxxxxxx>
• Re: dmaengine 3.13 v2
  • From: Jon Mason <jon.mason@xxxxxxxxx>
• Re: dmaengine 3.13 v2
  • From: Vinod Koul <vinod.koul@xxxxxxxxx>
• multiple device failure of mdadm array
  • From: kustep <kustep@xxxxxx>
• Re: dmaengine 3.13 v2
  • From: Vinod Koul <vinod.koul@xxxxxxxxx>
• dmaengine 3.13 v2
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: mdadm --fail requires writeable drive.
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: [dm-devel] [PATCH -next] dm cache policy mq:: use list_del_init instead of list_del/INIT_LIST_HEAD
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH -next] dm cache policy mq:: use list_del_init instead of list_del/INIT_LIST_HEAD
  • From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
• /proc/mdstat status documentation and md: export_rdev
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: mdadm --fail requires writeable drive.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: mdadm --fail requires writeable drive.
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• RE: 3.12: raid-1 mismatch_cnt question
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: joystick <joystick@xxxxxxxxxxxxx>
• RE: 3.12: raid-1 mismatch_cnt question
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: [PATCH 4/4] raid1: Rewrite the implementation of iobarrier.
  • From: NeilBrown <neilb@xxxxxxx>
• kernel panic with bitmap_startwrite
  • From: 4363@xxxxxxx
• Re: mdadm --fail requires writeable drive.
  • From: NeilBrown <neilb@xxxxxxx>
• RE: 3.12: raid-1 mismatch_cnt question
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/4] ioatdma: 16-source operation fixes
  • From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
• [PATCH 4/4] raid6test: add new corner case for ioatdma driver
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 3/4] ioatdma: clean up sed pool kmem_cache
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2/4] ioatdma: fix selection of 16 vs 8 source path
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 1/4] ioatdma: fix sed pool selection
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 0/4] ioatdma: 16-source operation fixes
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• mdadm --fail requires writeable drive.
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: [PATCH 0/2] Fix oops when changed group_thread_cnt
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: recommending RAID6 over RAID5 when doing mdadm --create
  • From: Giovanni Tessore <giotex@xxxxxxxxxx>
• Re: [PATCH 2/2] raid5: Using conf->device_lock protect multi-thread resouce when changed.
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 1/2] raid5: Before freeing old multi-thread worker,it should flush them.
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: recommending RAID6 over RAID5 when doing mdadm --create
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• [PATCH 1/2] raid5: Before freeing old multi-thread worker,it should flush them.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 2/2] raid5: Using conf->device_lock protect multi-thread resouce when changed.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 0/2] Fix oops when changed group_thread_cnt
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• RE: 3.12: raid-1 mismatch_cnt question
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: mdadm: sending ioctl [1261|800c0910] to a partition!
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: recommending RAID6 over RAID5 when doing mdadm --create
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: 3.12: raid-1 mismatch_cnt question
  • From: joystick <joystick@xxxxxxxxxxxxx>
• mdadm: sending ioctl [1261|800c0910] to a partition!
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: recommending RAID6 over RAID5 when doing mdadm --create
  • From: Tommy Apel <tommyapeldk@xxxxxxxxx>
• RE: 3.12: raid-1 mismatch_cnt question
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: recommending RAID6 over RAID5 when doing mdadm --create
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: recommending RAID6 over RAID5 when doing mdadm --create
  • From: Tommy Apel <tommyapeldk@xxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• recommending RAID6 over RAID5 when doing mdadm --create
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: stoppind md from kicking out "bad' drives
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• stoppind md from kicking out "bad' drives
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Running check and e2fsck simultaneously
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: mdadm: /dev/md0 has been started with 1 drive (out of 2).
  • From: Ivan Lezhnjov IV <ivan.lezhnjov.iv@xxxxxxxxx>