Linux RAID Storage Date Index

• Thread Index

• [PATCH] imsm: FIX: Limit migration record operation by disk slot not by index
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: Raid10 and page cache
  • From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
• Re: [PATCH] md: Add ability for disable bad block management
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/9] Array degradation during reshape and rebuild (cont.)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid10 and page cache
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 4 out of 16 drives show up as 'removed'
  • From: Eli Morris <ermorris@xxxxxxxx>
• Re: Raid10 and page cache
  • From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
• Re: system startup hangs
  • From: "Richard B. Pyne" <rpyne@xxxxxxxxxxx>
• Re: system startup hangs
  • From: "Richard B. Pyne" <rpyne@xxxxxxxxxxx>
• Re: system startup hangs
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: system startup hangs
  • From: NeilBrown <neilb@xxxxxxx>
• system startup hangs
  • From: "Richard B. Pyne" <rpyne@xxxxxxxxxxx>
• Re: 4 out of 16 drives show up as 'removed'
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 4 out of 16 drives show up as 'removed'
  • From: Eli Morris <ermorris@xxxxxxxx>
• Fwd: 4 out of 16 drives show up as 'removed'
  • From: Eli Morris <ermorris@xxxxxxxx>
• Re: 4 out of 16 drives show up as 'removed'
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 4 out of 16 drives show up as 'removed'
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• 4 out of 16 drives show up as 'removed'
  • From: Eli Morris <ermorris@xxxxxxxx>
• [PATCH 9/9] imsm: FIX: Use defines for device map access
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 8/9] imsm: FIX: Check correct slots on disk failure
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 7/9] imsm: FIX: Finish rebuild and initialization when missing drive is handled
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 6/9] imsm: FIX: Mark failure for rebuild
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 5/9] imsm: FIX: Add array map state transition for failures during initialization
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 4/9] imsm: FIX: Do not allow spare activation during rebuild
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 3/9] imsm: Function imsm_set_disk() rework
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 2/9] imsm: FIX: Correct ords merging in end_migration()
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/9] imsm: FIX: Remove longer map request
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 0/9] Array degradation during reshape and rebuild (cont.)
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• RE: [PATCH] md: Add ability for disable bad block management
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: Raid10 and page cache
  • From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
• Re: Raid10 and page cache
  • From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
• Re: Raid10 and page cache
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid10 and page cache
  • From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
• Re: meta: should i chase this down?
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Raid10 and page cache
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid10 and page cache
  • From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
• Re: [PATCH] md: Add ability for disable bad block management
  • From: NeilBrown <neilb@xxxxxxx>
• Re: need a little help rebuilding a raid 10
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: [PATCH] imsm: fix: does not allow to use invalid chunk size
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid10 and page cache
  • From: NeilBrown <neilb@xxxxxxx>
• Re: meta: should i chase this down?
  • From: NeilBrown <neilb@xxxxxxx>
• meta: should i chase this down?
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Raid10 and page cache
  • From: Marcus Sorensen <shadowsor@xxxxxxxxx>
• Re: Raid10 and page cache
  • From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
• Re: Raid10 and page cache
  • From: NeilBrown <neilb@xxxxxxx>
• Raid10 and page cache
  • From: Yucong Sun (叶雨飞) <sunyucong@xxxxxxxxx>
• Re: RAID5: failing an active component during spare rebuild - arrays hangs
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID5: failing an active component during spare rebuild - arrays hangs
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• RE: [PATCH] imsm: fix: does not allow to use invalid chunk size
  • From: "Hawrylewicz Czarnowski, Przemyslaw" <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• Re: need a little help rebuilding a raid 10
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: need a little help rebuilding a raid 10
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: need a little help rebuilding a raid 10
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• RE: [PATCH] md: Add ability for disable bad block management
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• RE: [PATCH] imsm: do not fail load_container when first 2 disks are missing
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• Re: Spin down
  • From: Vincent Pelletier <plr.vincent@xxxxxxxxx>
• RE: [PATCH 00/11] Degradation during reshape
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: [PATCH] md: Add ability for disable bad block management
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Possible changes to bio cloning and some related stuff
  • From: NeilBrown <neilb@xxxxxxx>
• Possible changes to bio cloning and some related stuff
  • From: Kent Overstreet <koverstreet@xxxxxxxxxx>
• Re: mdadm, bitmap and split-brain
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Spin down
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID5: failing an active component during spare rebuild - arrays hangs
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: fix: correct checking newly missing disks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: fix: correct checking newly missing disks
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• need a little help rebuilding a raid 10
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: [PATCH] imsm: fix: correct checking newly missing disks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] FIX: resolve make everything compilation error
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: FIX: Just created redundant array is not in uninitialized state
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: fix: does not allow to use invalid chunk size
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 00/11] Degradation during reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: do not fail load_container when first 2 disks are missing
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] FIX: resolve make everything compilation error
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: RAID1 round robin read support in md?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• [PATCH] imsm: FIX: Just created redundant array is not in uninitialized state
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• RE: Is this stupid?
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: Spin down
  • From: Vincent Pelletier <plr.vincent@xxxxxxxxx>
• RE: Is this stupid?
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: Is this stupid?
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: RAID6 - repeated hot-pulls issue
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Spin down
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Is this stupid?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID1 round robin read support in md?
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: RAID1 round robin read support in md?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID1 round robin read support in md?
  • From: Borg Onion <borg.onion@xxxxxxxxx>
• Re: md metadata nightmare
  • From: Kenneth Emerson <kenneth.emerson@xxxxxxxxx>
• Re: RAID1 round robin read support in md?
  • From: Marcus Sorensen <shadowsor@xxxxxxxxx>
• RAID1 round robin read support in md?
  • From: Borg Onion <borg.onion@xxxxxxxxx>
• Is this stupid?
  • From: "Leslie Rhorer" <lrhorer@xxxxxxxxxxx>
• Re: md metadata nightmare
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md metadata nightmare
  • From: wilsonjonathan <piercing_male@xxxxxxxxxxx>
• Re: md metadata nightmare
  • From: Kenneth Emerson <kenneth.emerson@xxxxxxxxx>
• md metadata nightmare
  • From: Kenneth Emerson <kenneth.emerson@xxxxxxxxx>
• Spin down
  • From: Vincent Pelletier <plr.vincent@xxxxxxxxx>
• RAID6 - repeated hot-pulls issue
  • From: John Gehring <john.gehring@xxxxxxxxx>
• RE: [PATCH] imsm: fix: correct checking newly missing disks
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• RE: [PATCH] imsm: fix: correct checking newly missing disks
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• RE: [PATCH 01/11] imsm: FIX: Return longer map for failure setting
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: quick question about write-intent bitmap
  • From: NeilBrown <neilb@xxxxxxx>
• quick question about write-intent bitmap
  • From: Marcus Sorensen <shadowsor@xxxxxxxxx>
• Re: [PATCH 01/11] imsm: FIX: Return longer map for failure setting
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: mdadm 3.2.2: Behavioral change when adding back a previously faulted device
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• mdadm 3.2.2: Behavioral change when adding back a previously faulted device
  • From: Martin Steigerwald <ms@xxxxxxxxx>
• RE: [PATCH] md: Add ability for disable bad block management
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• RE: [PATCH 01/11] imsm: FIX: Return longer map for failure setting
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: [PATCH] imsm: fix: correct checking newly missing disks
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 01/11] imsm: FIX: Return longer map for failure setting
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] md: Add ability for disable bad block management
  • From: NeilBrown <neilb@xxxxxxx>
• Re: linear raid, is partial recovery possible?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: linear raid, is partial recovery possible?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: linear raid, is partial recovery possible?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: linear raid, is partial recovery possible?
  • From: NeilBrown <neilb@xxxxxxx>
• linear raid, is partial recovery possible?
  • From: wilsonjonathan <piercing_male@xxxxxxxxxxx>
• Re: Ubuntu mdadm Raid and EFI
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Ubuntu mdadm Raid and EFI
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• [UPDATED PATCH 57/62] dm: remove the second argument of k[un]map_atomic()
  • From: Cong Wang <amwang@xxxxxxxxxx>
• [UPDATED PATCH 17/62] md: remove the second argument of k[un]map_atomic()
  • From: Cong Wang <amwang@xxxxxxxxxx>
• Re: [dm-devel] [PATCH 17/62] md: remove the second argument of k[un]map_atomic()
  • From: Cong Wang <amwang@xxxxxxxxxx>
• Re: [dm-devel] [PATCH 17/62] md: remove the second argument of k[un]map_atomic()
  • From: Milan Broz <mbroz@xxxxxxxxxx>
• Re: RAID5: failing an active component during spare rebuild - arrays hangs
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [PATCH 17/62] md: remove the second argument of k[un]map_atomic()
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 57/62] md: remove the second argument of k[un]map_atomic()
  • From: Cong Wang <amwang@xxxxxxxxxx>
• [PATCH 17/62] md: remove the second argument of k[un]map_atomic()
  • From: Cong Wang <amwang@xxxxxxxxxx>
• mdadm, bitmap and split-brain
  • From: Ronal Andadinata <randadinata@xxxxxxxxx>
• Online RAID1 -> RAID10 migration?
  • From: Bart Kus <me@xxxxxxxx>
• [PATCH] imsm: fix: does not allow to use invalid chunk size
  • From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• Re: Ubuntu mdadm Raid and EFI
  • From: Dominique <dcouot@xxxxxxxxxxx>
• Re: Is it possible to change the wait time before a drive is concidered failed?
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Ubuntu mdadm Raid and EFI
  • From: Dominique <dcouot@xxxxxxxxxxx>
• Re: partition based raid1 and multi boot Ubuntu/Xubuntu
  • From: Gavin Whitehead <gavin@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• RE: [PATCH] md: Add ability for disable bad block management
  • From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
• RE: [PATCH] md: Add ability for disable bad block management
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: [PATCH] md: Add ability for disable bad block management
  • From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
• [PATCH] md: Add ability for disable bad block management
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 11/11] Disable BBM when it is not supported
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 10/11] imsm: FIX: Check maximum allowed degradation level in recover_backup_imsm()
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 09/11] imsm: FIX: Check maximum allowed degradation level in open_backup_targets()
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 08/11] imsm: FIX: Function rework - imsm_count_failed()
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 07/11] imsm: FIX: Manage second map state on array degradation
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 06/11] imsm: FIX: Restore critical section on degraded array
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 05/11] imsm: FIX: Remove single map state limitation in getinfo
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 04/11] imsm: FIX: Finalize degraded migration
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 03/11] imsm: FIX: Do not end migration when missing drive is handled
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 02/11] imsm: FIX: Mark both maps on degradation while migrating
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 01/11] imsm: FIX: Return longer map for failure setting
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 00/11] Degradation during reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: partition based raid1 and multi boot Ubuntu/Xubuntu
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• [PATCH] imsm: do not fail load_container when first 2 disks are missing
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• Re: [PATCH] imsm: fix, check all volumes state in Grow_continue function
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: incorrect incremental behavior because of wrong index used
  • From: NeilBrown <neilb@xxxxxxx>
• md metadata nightmare
  • From: Kenneth Emerson <kenneth.emerson@xxxxxxxxx>
• Re: md metadata nightmare
  • From: NeilBrown <neilb@xxxxxxx>
• Re: partition based raid1 and multi boot Ubuntu/Xubuntu
  • From: Gavin Whitehead <gavin@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: md device io request split
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: incorrect incremental behavior because of wrong index used
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• [PATCH] imsm: incorrect incremental behavior because of wrong index used
  • From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• Re: md metadata nightmare
  • From: CoolCold <coolthecold@xxxxxxxxx>
• [PATCH] imsm: fix, check all volumes state in Grow_continue function
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• Re: md device io request split
  • From: "Ramon Schönborn" <RSchoenborn@xxxxxxx>
• Re: [OT] Re: Disk identity crisis on RAID10 recovery (3.1.0)
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: [OT] Re: Disk identity crisis on RAID10 recovery (3.1.0)
  • From: NeilBrown <neilb@xxxxxxx>
• [OT] Re: Disk identity crisis on RAID10 recovery (3.1.0)
  • From: Konrad Rzepecki <krzepecki@xxxxxxxxxxx>
• Re: md metadata nightmare
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: md device io request split
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md metadata nightmare
  • From: NeilBrown <neilb@xxxxxxx>
• md metadata nightmare
  • From: Kenneth Emerson <kenneth.emerson@xxxxxxxxx>
• Re: partition based raid1 and multi boot Ubuntu/Xubuntu
  • From: NeilBrown <neilb@xxxxxxx>
• partition based raid1 and multi boot Ubuntu/Xubuntu
  • From: Gavin Whitehead <gavin@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Disk identity crisis on RAID10 recovery (3.1.0)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Is it possible to change the wait time before a drive is concidered failed?
  • From: wilsonjonathan <piercing_male@xxxxxxxxxxx>
• Re: Disk identity crisis on RAID10 recovery (3.1.0)
  • From: Konrad Rzepecki <krzepecki@xxxxxxxxxxx>
• Re: Disk identity crisis on RAID10 recovery (3.1.0)
  • From: Konrad Rzepecki <krzepecki@xxxxxxxxxxx>
• Re: raid1d crash at boot
  • From: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
• Re: raid1d crash at boot
  • From: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
• Re: Disk identity crisis on RAID10 recovery (3.1.0)
  • From: NeilBrown <neilb@xxxxxxx>
• Disk identity crisis on RAID10 recovery (3.1.0)
  • From: Konrad Rzepecki <krzepecki@xxxxxxxxxxx>
• Re: raid1d crash at boot
  • From: NeilBrown <neilb@xxxxxxx>
• md device io request split
  • From: "Ramon Schönborn" <RSchoenborn@xxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Question about raid 10 and raid 1+0 setup
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: raid1d crash at boot
  • From: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
• Re: possible bug - bitmap dirty pages status
  • From: linbloke <linbloke@xxxxxxxxxxx>
• Question about raid 10 and raid 1+0 setup
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• RE: BUG_ON triggered in worker_enter_idle, after power failure caused potential RAID corruption (kernel 2.6.39.4)
  • From: Bruce Stenning <b.stenning@xxxxxxxxxxxxxxxx>
• Re: raid1d crash at boot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1d crash at boot
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] fix: correct metadata's update communication
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Is it possible to change the wait time before a drive is concidered failed?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1d crash at boot
  • From: NeilBrown <neilb@xxxxxxx>
• Is it possible to change the wait time before a drive is concidered failed?
  • From: wilsonjonathan <piercing_male@xxxxxxxxxxx>
• [PATCH] fix: correct metadata's update communication
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• [PATCH] imsm: fix: correct printing value of blocks per migration unit
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: MD RAID1 weirdness *SOLVED*
  • From: Danilo Godec <danilo.godec@xxxxxxxxx>
• MD RAID1 weirdness
  • From: Danilo Godec <danilo.godec@xxxxxxxxx>
• Re: Reshape 3-drive RAID1 into 3-drive RAID-5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Reshape 3-drive RAID1 into 3-drive RAID-5
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Idea: Dynamic growth of the md array
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Idea: Dynamic growth of the md array
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Idea: Dynamic growth of the md array
  • From: Terrance Hutchinson <Terrance.Hutchinson@xxxxxxxxxxx>
• BUG_ON triggered in worker_enter_idle, after power failure caused potential RAID corruption (kernel 2.6.39.4)
  • From: Bruce Stenning <b.stenning@xxxxxxxxxxxxxxxx>
• [PATCH] mdadm trivial: Print more detailed error messages on re-add failure
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [PATCH] imsm: platform capabilities are not validated during level migration
  • From: NeilBrown <neilb@xxxxxxx>
• Re: possible bug - bitmap dirty pages status
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: raid startup on a live CD?
  • From: Hank Barta <hbarta@xxxxxxxxx>
• Re: possible bug - bitmap dirty pages status
  • From: NeilBrown <neilb@xxxxxxx>
• Re: possible bug - bitmap dirty pages status
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Reshape 3-drive RAID1 into 3-drive RAID-5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid startup on a live CD?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Reshape 3-drive RAID1 into 3-drive RAID-5
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: raid startup on a live CD?
  • From: Hank Barta <hbarta@xxxxxxxxx>
• Rebuilding Raid 1 set up
  • From: William Colls <william.colls@xxxxxxxxxx>
• Reshape 3-drive RAID1 into 3-drive RAID-5
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• [PATCH] imsm: platform capabilities are not validated during level migration
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• Re: md/raid10: handle recovery of replacement devices.
  • From: NeilBrown <neilb@xxxxxxx>
• re: md/raid10: handle recovery of replacement devices.
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: raid startup on a live CD?
  • From: NeilBrown <neilb@xxxxxxx>
• raid startup on a live CD?
  • From: Hank Barta <hbarta@xxxxxxxxx>
• Re: [PATCH] imsm: fix: correct checking newly missing disks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: possible bug - bitmap dirty pages status
  • From: linbloke <linbloke@xxxxxxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: William Colls <william.colls@xxxxxxxxxx>
• [PATCH] imsm: fix: correct checking newly missing disks
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: raid 5 to raid 6 reshape gone bad
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: fix: Allowed to create 2 volumes with total size less then maximum.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid 5 to raid 6 reshape gone bad
  • From: Travis Brown <teb@xxxxxxxxxx>
• Re: raid 5 to raid 6 reshape gone bad
  • From: Travis Brown <teb@xxxxxxxxxx>
• Re: raid 5 to raid 6 reshape gone bad
  • From: Travis Brown <teb@xxxxxxxxxx>
• Re: raid 5 to raid 6 reshape gone bad
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: raid 5 to raid 6 reshape gone bad
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid 5 to raid 6 reshape gone bad
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: raid 5 to raid 6 reshape gone bad
  • From: NeilBrown <neilb@xxxxxxx>
• raid 5 to raid 6 reshape gone bad
  • From: Travis Brown <teb@xxxxxxxxxx>
• Re: unable to recover RAID 5 due to bad block [solved]
  • From: Chris Purves <chris@xxxxxxxxxxxx>
• Re: unable to recover RAID 5 due to bad block
  • From: NeilBrown <neilb@xxxxxxx>
• Re: unable to recover RAID 5 due to bad block
  • From: NeilBrown <neilb@xxxxxxx>
• Re: unable to recover RAID 5 due to bad block
  • From: Chris Purves <chris@xxxxxxxxxxxx>
• Re: unable to recover RAID 5 due to bad block
  • From: Chris Purves <chris@xxxxxxxxxxxx>
• Re: unable to recover RAID 5 due to bad block
  • From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
• Re: unable to recover RAID 5 due to bad block
  • From: Chris Purves <chris@xxxxxxxxxxxx>
• Re: unable to recover RAID 5 due to bad block
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: unable to recover RAID 5 due to bad block
  • From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: John Robinson <john.robinson@xxxxxxxxxxx>
• Re: unable to recover RAID 5 due to bad block
  • From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
• unable to recover RAID 5 due to bad block
  • From: Chris Purves <chris@xxxxxxxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: William Colls <william.colls@xxxxxxxxxx>
• RE: [PATCH] imsm: fix: Allowed to create 2 volumes with total size less then maximum.
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• Re: [PATCH] imsm: control number of active imsm volumes in the system
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH] imsm: fix: Allowed to create 2 volumes with total size less then maximum.
  • From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
• Re: Intel RAID problems
  • From: NeilBrown <neilb@xxxxxxx>
• RE: [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: William Colls <william.colls@xxxxxxxxxx>
• Intel RAID problems
  • From: Blair Strater <me@xxxxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: mini change of raid5.c
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: control number of active imsm volumes in the system
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdraid write performance in different kernels up to 3.0, 3.0 shows huge improvement
  • From: NeilBrown <neilb@xxxxxxx>
• Re: All kinds of things on RAID/mdadm
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: William Colls <william.colls@xxxxxxxxxx>
• Re: All kinds of things on RAID/mdadm
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: William Colls <william.colls@xxxxxxxxxx>
• Re: Raid Problem - Unknown File System Type
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Raid Problem - Unknown File System Type
  • From: William Colls <william.colls@xxxxxxxxxx>
• [PATCH] imsm: control number of active imsm volumes in the system
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• mini change of raid5.c
  • From: "Hardy Flor" <Flor@xxxxxxxxxxxx>
• PULL REQUEST - md bugfixes for 3.2-rc
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: Auto-assembling RAID6 over RAID0?
  • From: Michał Sawicz <michal@xxxxxxxxxx>
• mdraid write performance in different kernels up to 3.0, 3.0 shows huge improvement
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: Impending failure?
  • From: Peter Zieba <pzieba@xxxxxxxxxxxxxxxxx>
• Re: Impending failure?
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
  • From: Witold Baryluk <baryluk@xxxxxxxxxxxxxxxx>
• Re: Working TRIM for md RAID
  • From: Alex Besogonov <alex.besogonov@xxxxxxxxx>
• Re: Working TRIM for md RAID
  • From: David Rees <drees76@xxxxxxxxx>
• Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: Special drives for Linux Raid?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Special drives for Linux Raid?
  • From: Beolach <beolach@xxxxxxxxx>
• Re: documentation for echo check > /dev/mdX, etc.
  • From: Beolach <beolach@xxxxxxxxx>
• Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
  • From: Witold Baryluk <baryluk@xxxxxxxxxxxxxxxx>
• Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
  • From: Witold Baryluk <baryluk@xxxxxxxxxxxxxxxx>
• Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Special drives for Linux Raid?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Special drives for Linux Raid?
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: [dm-devel] Error when compiling drivers/md/dm-bufio.c
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Special drives for Linux Raid?
  • From: Danilo Godec <danilo.godec@xxxxxxxxx>
• Re: All kinds of things on RAID/mdadm
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• All kinds of things on RAID/mdadm
  • From: Martijn <mailinglist@xxxxxxxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• RE: [PATCH] fix: Allowed to assemble 2 volumes with the same names from config file.
  • From: "Orlowski, Lukasz" <lukasz.orlowski@xxxxxxxxx>
• Error when compiling drivers/md/dm-bufio.c
  • From: Witold Baryluk <baryluk@xxxxxxxxxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md/raid5: STRIPE_ACTIVE has lock semantics, add barriers
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: fix: add support for OLCE and migration to imsm_count_failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] fix: Allowed to assemble 2 volumes with the same names from config file.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] FIX: Do not continue container reshape when mdmon is absent
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] FIX: mdmon doesn't start
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] dm-ioctl: Don't leak memory in target_message() if 'argc' is NULL
  • From: Jesper Juhl <jj@xxxxxxxxxxxxx>
• Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
  • From: NeilBrown <neilb@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: NeilBrown <neilb@xxxxxxx>
• Re: potentially lost largeish raid5 array..
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Impending failure?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• documentation for echo check > /dev/mdX, etc.
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Impending failure?
  • From: Peter Zieba <pzieba@xxxxxxxxxxxxxxxxx>
• Re: Impending failure?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Impending failure?
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: Impending failure?
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Impending failure?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Impending failure?
  • From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
• Re: Impending failure?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• [PATCH] imsm: fix: add support for OLCE and migration to imsm_count_failed
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: Impending failure?
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Impending failure?
  • From: Alex <mysqlstudent@xxxxxxxxx>
• [PATCH] fix: Allowed to assemble 2 volumes with the same names from config file.
  • From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
• RE: [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 2/2] FIX: Do not continue container reshape when mdmon is absent
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 1/2] FIX: mdmon doesn't start
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: [PATCH 00/12] More leak and NULL pointer dereference fixes
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 00/19] More fixes for resource leaks and warnings
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: [PATCH 00/12] More leak and NULL pointer dereference fixes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• [PATCH 12/12] match_metadata_desc(): Fix memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 11/12] fd2devname(): Don't dereference NULL pointer
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 10/12] Manage_ro(): Check pointer rather than dereferencing it
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 07/12] close_aa(): Verify file descriptors are valid before trying to close them
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 09/12] unblock_monitor(): Check sra is valid before dereferencing
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 08/12] ahci_enumerate_ports(): Don't close fd that failed to open
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 06/12] disk_init_and_add(): Fail if opening sysfs file descriptors fail
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 05/12] array_try_spare(): open_dev() returns -1 on error, not zero
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 04/12] get_component_size(): Check read() return value for error before using it
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 03/12] mdstat_read(): Check return value of dup() before using file descriptor
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 02/12] ping_monitor(): check file descriptor is valid before using and closing it
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 01/12] mdadm: add missing break for UpdateSubarray
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 00/12] More leak and NULL pointer dereference fixes
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: [PATCH 00/19] More fixes for resource leaks and warnings
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Kay Sievers <kay.sievers@xxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: keld@xxxxxxxxxx
• Re: possibly silly question (raid failover)
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [md PATCH 17/17] md/raid1: Mark device replaceable when we see a write error.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 16/17] md/raid1: If there is a spare and a replaceable device, start replacement.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 15/17] md/raid1: recognise replacements when assembling arrays.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 14/17] md/raid1: handle activation of replacement device when recovery completes.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 13/17] md/raid1: Allow a failed replacement device to be removed.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 12/17] md/raid1: Allocate spare to store replacement devices and their bios.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 11/17] md/raid1: Replace use of mddev->raid_disks with conf->raid_disks.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 10/17] md/raid10: If there is a spare and a replaceable device, start replacement.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 09/17] md/raid10: recognise replacements when assembling array.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 08/17] md/raid10: Allow replacement device to be replace old drive.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 07/17] md/raid10: handle recovery of replacement devices.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 06/17] md/raid10: Handle replacement devices during resync.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 05/17] md/raid10: writes should get directed to replacement as well as original.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 04/17] md/raid10: allow removal of failed replacement devices.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 03/17] md/raid10: preferentially read from replacement device if possible.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 02/17] md/raid10: change read_balance to return an rdev
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 01/17] md/raid10: prepare data structures for handling replacement.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 00/17] hot-replace support for RAID1 and RAID10
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: NeilBrown <neilb@xxxxxxx>
• Re: possibly silly question (raid failover)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: possibly silly question (raid failover)
  • From: keld@xxxxxxxxxx
• Re: possibly silly question (raid failover)
  • From: keld@xxxxxxxxxx
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 00/19] More fixes for resource leaks and warnings
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [md PATCH 1/1] add display of hours remaining to finish resync
  • From: Paul Menzel <pm.debian@xxxxxxxxxxxxxx>
• Re: [md PATCH 1/1] add display of hours remaining to finish resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: with raid-6 any writes access all disks
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: keld@xxxxxxxxxx
• Re: possibly silly question (raid failover)
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• [md PATCH 1/1] add display of hours remaining to finish resync
  • From: Krzysztof Adamski <k@xxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: [PATCH 19/19] make_parts(): Avoid false positive security warning
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• [PATCH 09/19] Detail(): Remember to free 'avail'
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 14/19] Managa_ro(): free() mdi before exiting
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 12/19] Manage_subdevs(): avoid leaking super
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 19/19] make_parts(): Avoid false positive security warning
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 18/19] validate_geometry_imsm_volume(): Avoid NULL pointer dereference
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 17/19] bitmap_fd_read(): fix memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 15/19] Manage_runstop(): Avoid memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 16/19] Monitor(): free allocated memory on exit
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 10/19] Grow_reshape(): Fix another 'sra' leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 06/19] assemble_container_content(): fix memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 13/19] IncrementalScan(): Fix memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 11/19] enough_fd(): remember to free buffer for avail array
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 03/19] Incremental(): Check return value of dev_open() before trying to use it
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 07/19] Grow_restart(): free() offsets after use
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 08/19] Assemble(): don't dup_super() before we need it.
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 02/19] Grow_addbitmap(): don't try to close a file descriptor which failed to open
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 05/19] remove_devices(): readlink returns -1 on error
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 04/19] sysfs_unique_holder(): Check read() return value before using as buffer index
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 00/19] More fixes for resource leaks and warnings
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 01/19] Grow_Add_device(): dev_open() return a negative fd on error
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: possibly silly question (raid failover)
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
• Re: possibly silly question (raid failover)
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/3] conf_match(): Remove dead code
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 00/11] Memory/resource leaks and unchecked return fixes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/3] conf_match(): Remove dead code
  • From: NeilBrown <neilb@xxxxxxx>
• possibly silly question (raid failover)
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• [PANIC] : kernel BUG at drivers/md/raid5.c:2756!
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: raid(1) and block caching
  • From: CoolCold <coolthecold@xxxxxxxxx>
• RE: [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH 11/11] mdmon(): Error out if failing to connect to victim monitor
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 10/11] Write_rules(): Avoid stack corruption if using extremely long udev pathname
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 09/11] policy_add(): Add missing va_end()
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 08/11] Avoid memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 07/11] Add missing return in case of trying to grow sub-array
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 06/11] Fix memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 05/11] partition_try_spare() use closedir() to release DIR * returned by opendir()
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 04/11] Fix memory leak of 'st3' in array_try_spare()
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 03/11] Fix memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 02/11] Fix memory leak
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 01/11] Fix memory leaks in reshape_array()
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 00/11] Memory/resource leaks and unchecked return fixes
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 3/3] Kill(): Remove redundant check and dead code
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 1/3] conf_match(): Remove dead code
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 2/3] conf_watch(): More dead code removal
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/3] Remove dead code
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [PATCH 1/2] Avoid use after free
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• PULL REQUEST - serious md/RAID10 bug in 3.1 when activating a hot-spare.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] Avoid use after free
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Unable to restart reshape
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Unable to restart reshape
  • From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
• Re: Unable to restart reshape
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Unable to restart reshape
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Unable to restart reshape
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Unable to restart reshape
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Unable to restart reshape
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: raid(1) and block caching
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: raid(1) and block caching
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: raid(1) and block caching
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid(1) and block caching
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• raid(1) and block caching
  • From: CoolCold <coolthecold@xxxxxxxxx>
• [PATCH 2/2] Avoid stack overflow if GPT partition entries on disk are > 128 bytes
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 1/2] Avoid use after free
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/2] Misc fixes
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• Re: Lost mdadm RAID6 array and tried everything, hoping for any other suggestions you may have
  • From: Ryan Castellucci <ryan.castellucci+linux-raid@xxxxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: "Peter W. Morreale" <morreale@xxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Auto-assembling RAID6 over RAID0?
  • From: Michał Sawicz <michal@xxxxxxxxxx>
• Auto-assembling RAID6 over RAID0?
  • From: Michał Sawicz <michal@xxxxxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: "Peter W. Morreale" <morreale@xxxxxxx>
• Re: with raid-6 any writes access all disks
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: with raid-6 any writes access all disks
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: with raid-6 any writes access all disks
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [PATCH] GCC compile fix: remove calculation of unused variable 'reservation'
  • From: NeilBrown <neilb@xxxxxxx>
• RE: [PATCH] GCC compile fix: remove calculation of unused variable 'reservation'
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• Re: [PATCH 00/13] Add missing handling of malloc() failure
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH] FIX: Close unused handle in child process during reshape restart
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 00/13] Add missing handling of malloc() failure
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] GCC compile fix: remove calculation of unused variable 'reservation'
  • From: NeilBrown <neilb@xxxxxxx>
• Re: with raid-6 any writes access all disks
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: with raid-6 any writes access all disks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: with raid-6 any writes access all disks
  • From: "Peter W. Morreale" <morreale@xxxxxxx>
• with raid-6 any writes access all disks
  • From: Chris Pearson <kermit4@xxxxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Question about mdadm commit d6508f0cfb60edf07b36f1532eae4d9cddf7178b "be more careful about add attempts"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• [PATCH 07/13] Fix malloc() failure handling in Monitor.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 05/13] Handle malloc() failure in Examine.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 13/13] Catch malloc() failure
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 10/13] Handle malloc() failure in Grow.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 12/13] Handle malloc() failure in mdstat.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 11/13] Handle malloc() failure in mdopen.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 09/13] Fix malloc handling in dlink.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 08/13] Handle malloc() failures in devline()
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 06/13] Handle malloc() errors in Manage.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 04/13] Attempt to catch malloc() failure in Detail.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 03/13] Try to catch malloc() failures in Assemble.c
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 02/13] Catch malloc() failures
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 01/13] count_active() catch malloc() failure
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 00/13] Add missing handling of malloc() failure
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH] FIX: Close unused handle in child process during reshape restart
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: "Peter W. Morreale" <morreale@xxxxxxx>
• Re: [PATCH] GCC compile fix: remove calculation of unused variable 'reservation'
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• [md PATCH 16/16] md/raid5: Mark device replaceable when we see a write error.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 15/16] md/raid5: If there is a spare and a replaceable device, start replacement.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 14/16] md/raid5: recognise replacements when assembling array.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 13/16] md/raid5: handle activation of replacement device when recovery completes.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 12/16] md/raid5: detect and handle replacements during recovery.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 11/16] md/raid5: writes should get directed to replacement as well as original.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 10/16] md/raid5: allow removal for failed replacement devices.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 09/16] md/raid5: preferentially read from replacement device if possible.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 08/16] md/raid5: remove redundant bio initialisations.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 07/16] md/raid5: raid5.h cleanup
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 06/16] md/raid5: allow each slot to have an extra replacement device
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 05/16] md: create externally visible flags for supporting hot-replace.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 04/16] md: change hot_remove_disk to take an rdev rather than a number.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 03/16] md: remove test for duplicate device when setting slot number.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 02/16] md: take after reference to mddev during sysfs access.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 01/16] md: refine interpretation of "hold_active == UNTIL_IOCTL".
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 00/16] hot-replace support for RAID4/5/6
  • From: NeilBrown <neilb@xxxxxxx>
• PULL REQUEST md updates for 3.2
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] util.c: two typos fixed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Rotating RAID 1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm r/w operations without TEMP_FAILURE_RETRY()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm r/w operations without TEMP_FAILURE_RETRY()
  • From: Michal Soltys <soltys@xxxxxxxx>
• [PATCH] util.c: two typos fixed
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: Rotating RAID 1
  • From: linbloke <linbloke@xxxxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bad block management - which mdadm?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: NeilBrown <neilb@xxxxxxx>
• Bad block management - which mdadm?
  • From: Arkadiusz Miśkiewicz <a.miskiewicz@xxxxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: Converting from Raid 5 to 6
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Converting from Raid 5 to 6
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [systemd-devel] systemd kills mdmon if it was started manually by user
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Advice on build a RAID6
  • From: Krzysztof Adamski <k@xxxxxxxxxxx>
• Re: Advice on build a RAID6
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [PATCH 1/3] Remove race for starting container devices.
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 0/2] Fixes metadata while migrating from Raid 0 to Raid 10
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/3] Remove race for starting container devices.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: How to free devices held captive by failed arrays
  • From: Harry Mangalam <hjm@xxxxxxxxxxxxxxx>
• Re: How to free devices held captive by failed arrays
  • From: NeilBrown <neilb@xxxxxxx>
• Re: How to free devices held captive by failed arrays
  • From: Harry Mangalam <hjm@xxxxxxxxxxxxxxx>
• Re: How to free devices held captive by failed arrays
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm "Used Dev Size" on 3TB drives
  • From: NeilBrown <neilb@xxxxxxx>
• Advice on build a RAID6
  • From: Krzysztof Adamski <k@xxxxxxxxxxx>
• How to free devices held captive by failed arrays
  • From: Harry Mangalam <hjm@xxxxxxxxxxxxxxx>
• [PATCH 1/1] Incremental() lock error handling
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/1] Incremental() additional locking fixes
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 1/2] Create() don't leave the lock hanging on error
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 2/2] Create() check malloc() return value
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH] array_try_spare(): missing map_unlock()
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 3/3] Hold the map lock while performing Assemble to avoid races with udev
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 2/3] Don't tell sysfs to launch the container as we are doing it ourselves
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 1/3] Remove race for starting container devices.
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH v2 0/3] Fix mdadm vs udev race in Incremental and Assemble
  • From: Jes.Sorensen@xxxxxxxxxx
• mdadm "Used Dev Size" on 3TB drives
  • From: Andrew <andyukguy@xxxxxxxxx>
• [PATCH 2/2] imsm: fix: Fixes metadata after migration from Raid 0 to Raid 10
  • From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
• [PATCH 1/2] imsm: Moves metadata update code for spare activation to separate function
  • From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
• [PATCH 0/2] Fixes metadata while migrating from Raid 0 to Raid 10
  • From: Lukasz Orlowski <lukasz.orlowski@xxxxxxxxx>
• [PATCH 1/3] Remove race for starting container devices.
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 3/3] Hold the map lock while performing Assemble to avoid races with udev
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/3] Fix mdadm vs udev race in Incremental and Assemble
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 2/3] Don't tell sysfs to launch the container as we are doing it ourselves
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: mdadm help
  • From: Yathindra <ydev@xxxxxxxxxxx>
• Re: mdadm help
  • From: NeilBrown <neilb@xxxxxxx>
• mdadm help
  • From: Yathindra <ydev@xxxxxxxxxxx>
• Re: [PATCH] imsm: fix: prevent segfault in mark_failure
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] lib/raid6: Fix filename emitted in generated code
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] imsm: fix: correct debug printing of the volume's name
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• [PATCH] imsm: fix: prevent segfault in mark_failure
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: [PATCH] md.c: trivial comment fix
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md.c: trivial comment fix
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• Re: [PATCH] MD: Allow restarting an interrupted incremental recovery.
  • From: Andrei Warkentin <awarkentin@xxxxxxxxxx>
• Re: [PATCH] MD: Allow restarting an interrupted incremental recovery.
  • From: NeilBrown <neilb@xxxxxxx>
• Working TRIM for md RAID
  • From: Alex Besogonov <alex.besogonov@xxxxxxxxx>
• Re: [PATCH] MD: Allow restarting an interrupted incremental recovery.
  • From: Andrei Warkentin <awarkentin@xxxxxxxxxx>
• Re: [PATCH] MD: Allow restarting an interrupted incremental recovery.
  • From: Andrei Warkentin <awarkentin@xxxxxxxxxx>
• Re: [PATCH] MD: Allow restarting an interrupted incremental recovery.
  • From: Andrei Warkentin <awarkentin@xxxxxxxxxx>
• RE: [PATCH] fix: imsm: prevent segfault in mark_failure
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: mdadm r/w operations without TEMP_FAILURE_RETRY()
  • From: NeilBrown <neilb@xxxxxxx>
• FW: mdadm r/w operations without TEMP_FAILURE_RETRY()
  • From: "Orlowski, Lukasz" <lukasz.orlowski@xxxxxxxxx>
• [PATCH] fix: imsm: prevent segfault in mark_failure
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: [PATCH 0/1] IMSM do not assume prev + current map in same state means reshape
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• RE: [PATCH 0/1] IMSM do not assume prev + current map in same state means reshape
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Re: [PATCH] MD: Allow restarting an interrupted incremental recovery.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] MD: Allow restarting an interrupted incremental recovery.
  • From: Andrei Warkentin <andreiw@xxxxxxxxxx>
• Re: [RFC] MD: Allow restarting an interrupted incremental recovery.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 1/1] IMSM only run reshape if number of disks has changed
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/1] IMSM do not assume prev + current map in same state means reshape
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH] lib/raid6: Fix filename emitted in generated code
  • From: Dan McGee <dpmcgee@xxxxxxxxx>
• Re: [RFC] MD: Allow restarting an interrupted incremental recovery.
  • From: Andrei Warkentin <awarkentin@xxxxxxxxxx>
• Potential data rollback/corruption after drive failure and re-appearance
  • From: "Moshe Melnikov" <moshe@xxxxxxxxxxxxxxxxx>
• Re: [RFC] MD: Allow restarting an interrupted incremental recovery.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [mdadm PATCH 2/2] Fix unterminated buffer after readlink() call
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Data recovery from linear array (Intel SS4000-E)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Data recovery from linear array (Intel SS4000-E)
  • From: Johannes Moos <jmoos@xxxxxx>
• Re: Data recovery from linear array (Intel SS4000-E)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Data recovery from linear array (Intel SS4000-E)
  • From: Johannes Moos <jmoos@xxxxxx>
• Re: Data recovery from linear array (Intel SS4000-E)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Data recovery from linear array (Intel SS4000-E)
  • From: Johannes Moos <jmoos@xxxxxx>
• 2 drive RAID10 rebuild issue
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: [RFC] MD: Allow restarting an interrupted incremental recovery.
  • From: "Andrei E. Warkentin" <andrey.warkentin@xxxxxxxxx>
• Re: [RFC] MD: Restart an interrupted incremental recovery.
  • From: "Andrei E. Warkentin" <andrey.warkentin@xxxxxxxxx>
• Re: Data recovery from linear array (Intel SS4000-E)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Data recovery from linear array (Intel SS4000-E)
  • From: Johannes Moos <jmoos@xxxxxx>
• [mdadm PATCH 2/2] Fix unterminated buffer after readlink() call
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• [mdadm PATCH 1/2] Fix off-by-one in readlink() buffer size handling
  • From: Thomas Jarosch <thomas.jarosch@xxxxxxxxxxxxx>
• mdadm --grow on raid1 returns nonzero
  • From: Kevin W Monroe <kwmonroe@xxxxxxxxxxxxxxxxxx>
• [RFC] MD: Allow restarting an interrupted incremental recovery.
  • From: Andrei Warkentin <andreiw@xxxxxxxxxx>
• Re: [RFC] MD: Restart an interrupted incremental recovery.
  • From: "Andrei E. Warkentin" <andrey.warkentin@xxxxxxxxx>
• Re: Odd booting problem
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: Odd booting problem
  • From: maurice <mhilarius@xxxxxxxxx>
• [RFC] MD: Restart an interrupted incremental recovery.
  • From: Andrei Warkentin <andreiw@xxxxxxxxxx>
• Re: some general md raid questions
  • From: "Peter W. Morreale" <morreale@xxxxxxx>
• Re: some general md raid questions
  • From: Keith Keller <kkeller-usenet@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: 1.X metadata: Resuming an interrupted incremental recovery for RAID1.
  • From: "Andrei E. Warkentin" <andrey.warkentin@xxxxxxxxx>
• Re: Raid5 to another raid level??
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• some general md raid questions
  • From: "Peter W. Morreale" <morreale@xxxxxxx>
• Re: Raid5 to another raid level??
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 to another raid level??
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• Re: 1.X metadata: Resuming an interrupted incremental recovery for RAID1.
  • From: "Andrei E. Warkentin" <andrey.warkentin@xxxxxxxxx>
• Re: Raid5 to another raid level??
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 1.X metadata: Resuming an interrupted incremental recovery for RAID1.
  • From: NeilBrown <neilb@xxxxxxx>
• 1.X metadata: Resuming an interrupted incremental recovery for RAID1.
  • From: "Andrei E. Warkentin" <andrey.warkentin@xxxxxxxxx>
• Re: MD devnode still present after 'remove' udev event, and mdadm reports 'does not appear to be active'
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Odd booting problem
  • From: maurice <mhilarius@xxxxxxxxx>
• Re: md RAID10 questions
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: md RAID10 questions
  • From: keld@xxxxxxxxxx
• Re: Raid5 to another raid level??
  • From: Michael Busby <michael.a.busby@xxxxxxxxx>
• md RAID10 questions
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: Odd booting problem
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: Odd booting problem
  • From: Jim Schatzman <james.schatzman@xxxxxxxxxxxxxxxx>
• Re: Odd booting problem
  • From: maurice <mhilarius@xxxxxxxxx>
• configuration questions & advice
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: Thought about delayed sync
  • From: NeilBrown <neilb@xxxxxxx>
• BUG: spinlock lockup while performing FS operations and detected stalls on CPUs / tasks.
  • From: Валерий <paramonov@xxxxxxxxx>
• Re: Thought about delayed sync
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: Thought about delayed sync
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Thought about delayed sync
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: Thought about delayed sync
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: Thought about delayed sync
  • From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
• Re: Thought about delayed sync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Thought about delayed sync
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Thought about delayed sync
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: Gordon Henderson <gordon@xxxxxxxxxx>
• Re: BUG: spinlock lockup while performing FS operations and detected stalls on CPUs / tasks.
  • From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
• BUG: spinlock lockup while performing FS operations and detected stalls on CPUs / tasks.
  • From: Валерий <paramonov@xxxxxxxxx>
• Odd booting problem
  • From: maurice <mhilarius@xxxxxxxxx>
• Re: BUG: spinlock lockup while performing FS operations
  • From: NeilBrown <neilb@xxxxxxx>
• Re: BUG: spinlock lockup while performing FS operations
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Clarification behind md 1.0 superblock resync_offset and recovery_offset?
  • From: NeilBrown <neilb@xxxxxxx>
• Clarification behind md 1.0 superblock resync_offset and recovery_offset?
  • From: "Andrei E. Warkentin" <andrey.warkentin@xxxxxxxxx>
• [PATCH] GCC compile fix: remove calculation of unused variable 'reservation'
  • From: Jes.Sorensen@xxxxxxxxxx
• BUG: spinlock lockup while performing FS operations
  • From: Валерий <paramonov@xxxxxxxxx>
• [PATCH] Always run Grow_continue() for started array.
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PULLREQUEST] md bugfix for 3.1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/3] Always run Grow_continue() for started array.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: always use set_migr_type to set type of migration
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Creating an md with 3TB drives.
  • From: Jérôme Poulin <jeromepoulin@xxxxxxxxx>
• Re: Creating an md with 3TB drives.
  • From: Sebastian Muniz <sjmuniz@xxxxxxxxx>
• Re: How to stress test an RAID 6 array?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• RE: Does Linux support Intel Smart Response Technology?
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH] imsm: always use set_migr_type to set type of migration
  • From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• RE: [PATCH 1/3] Always run Grow_continue() for started array.
  • From: "Kwolek, Adam" <adam.kwolek@xxxxxxxxx>
• Does Linux support Intel Smart Response Technology?
  • From: "linux-raid" <linux-raid@xxxxxxxxxxxxxxxx>
• Appropriate kernel group for IDE/ATA/SAS/SATA issues?
  • From: Jim Schatzman <james.schatzman@xxxxxxxxxxxxxxxx>
• Re: Does Linux support Intel Smart Response Technology?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Does Linux support Intel Smart Response Technology?
  • From: "Guy Watkins" <Guy@xxxxxxxxxxxxxxxx>
• Re: [PATCH] imsm: fix: correct adding and activation of spare disks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/3] Set correct reshape restart position
  • From: NeilBrown <neilb@xxxxxxx>