Linux RAID Storage Date Index

• Thread Index

• sync action not working/ignored
  • From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Shouldn't --zero-superblock reset the UUID?
  • From: "mirovis" <mirovis@xxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• [RFC PATCH] raid5: Correct some failed-stripe which because the badsector.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH 3/3] raid5: Fix to_read/to_write judgement.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH 2/3] raid5: fix possible oops in add_stripe_bio when enable pr_debug
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH 1/3] raid5: Add per-stripe lock on toread in func
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH 0/3] raid5: fix three bugs.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Shouldn't --zero-superblock reset the UUID?
  • From: "mirovis" <mirovis@xxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• Re: Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: hung in raise_barrier() in raid1.c -- any ideas?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: hung in raise_barrier() in raid1.c -- any ideas?
  • From: Chris Friesen <chris.friesen@xxxxxxxxxxx>
• Re: hung in raise_barrier() in raid1.c -- any ideas?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: hung in raise_barrier() in raid1.c -- any ideas?
  • From: Chris Friesen <chris.friesen@xxxxxxxxxxx>
• Re: Small short question Was: Re: Recovering from the kernel bug, Neil?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Small short question Was: Re: Recovering from the kernel bug, Neil?
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• hung in raise_barrier() in raid1.c -- any ideas?
  • From: Chris Friesen <chris.friesen@xxxxxxxxxxx>
• RAID array on block device vs. on partition
  • From: "Andrew Dedesko" <adedesko@xxxxxxxxxx>
• Re: Wrong array size detected after reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Wrong array size detected after reboot
  • From: Markus Irle <tha.bear@xxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Re: [PATCH] raid5: fix possible oops in add_stripe_bio when enable pr_debug
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [PATCH] raid5: fix possible oops in add_stripe_bio when enable pr_debug
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] raid5: fix possible oops in add_stripe_bio when enable pr_debug
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Re: [PATCH] md: Add two chances to update sync/recovery checkpoint
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md: Add two chances to update sync/recovery checkpoint
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: [PATCH] md/bitmap:Don't use IS_ERR to judge alloc_page().
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: NeilBrown <neilb@xxxxxxx>
• Re: GPT Table broken on a Raid1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: [PATCH - v2] DM RAID: Fix for ineffective "sync" directive
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] fix: imsm: re-enable size expansion to the max value
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] fix: adjust parse_size() to the unsigned size variable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] fix: imsm: do not accept too small sizes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Small short question Was: Re: Recovering from the kernel bug, Neil?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] fix: imsm: mdmon should reread component_size on wakeup
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 1/2]MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] fix segfaults in Detail()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid6 low performance 8x3tb drives in singledegraded mode(=7x3tb)
  • From: Kasper Sandberg <kontakt@xxxxxxxxxxxxxxxxxxx>
• Re: Subject: [PATCH 1/1] drivers/md/raid1.c: fix NULL pointer bug in fix_read_error function
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Wrong array size detected after reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Areca hardware RAID / first-ever SCSI bus reset: am I about to lose this disk controller?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Wrong array size detected after reboot
  • From: Markus Irle <tha.bear@xxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: raid6 low performance 8x3tb drives in singledegraded mode(=7x3tb)
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: Ferry <iscsitmp@xxxxxxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: freaky <freaky@xxxxxxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: freaky <freaky@xxxxxxxxxxxxx>
• GPT Table broken on a Raid1
  • From: Günther J. Niederwimmer <gjn@xxxxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: joystick <joystick@xxxxxxxxxxxxx>
• Re: Can't reshape RAID1 to RAID5 due to chunk size
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: raid6 low performance 8x3tb drives in singledegraded mode(=7x3tb)
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: Arne Redlich <arne.redlich@xxxxxxxxxxxxxx>
• Re: raid6 low performance 8x3tb drives in singledegraded mode(=7x3tb)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Can't reshape RAID1 to RAID5 due to chunk size
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PULL REQUEST] 3 fixes for md in 3.6.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Wrong array size detected after reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Stop IMSM verify?
  • From: Daniel Frey <djqfrey@xxxxxxxxx>
• Re: MD device always starting as /dev/md127
  • From: Bryan Bush <bbushvt@xxxxxxxxx>
• Re: MD device always starting as /dev/md127
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD device always starting as /dev/md127
  • From: Phil Turmel <philip@xxxxxxxxxx>
• MD device always starting as /dev/md127
  • From: Bryan Bush <bbushvt@xxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Serious performance issues with mdadm RAID-5 partition exported through LIO (iSCSI)
  • From: Ferry <iscsitmp@xxxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: GuoZhong Han <hanguozhong@xxxxxxxxxxxx>
• [patch 2/2]MD: raid5 avoid unnecessary zero page for trim
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 1/2]MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: What parameters to mdadm, to re-create md device with payload starting at 0x22000 position on backing storage?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: What parameters to mdadm, to re-create md device with payload starting at 0x22000 position on backing storage?
  • From: Adam Ryczkowski <adam.ryczkowski@xxxxxxxxxxxxxx>
• Re: Stop IMSM verify?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Wrong count of devices in /proc/mdstat after "want_replacement"
  • From: NeilBrown <neilb@xxxxxxx>
• Wrong count of devices in /proc/mdstat after "want_replacement"
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 6/7 v2] MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: What parameters to mdadm, to re-create md device with payload starting at 0x22000 position on backing storage?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• [PATCH] fix: imsm: mdmon should reread component_size on wakeup
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• What parameters to mdadm, to re-create md device with payload starting at 0x22000 position on backing storage?
  • From: Adam Ryczkowski <adam.ryczkowski@xxxxxxxxxxxxxx>
• RE: RAID0 DeviceDisappeared event happen when restart mdmonitor service
  • From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
• Re: RAID0 DeviceDisappeared event happen when restart mdmonitor service
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: RAID0 DeviceDisappeared event happen when restart mdmonitor service
  • From: NeilBrown <neilb@xxxxxxx>
• RE: RAID0 DeviceDisappeared event happen when restart mdmonitor service
  • From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
• Re: RAID0 DeviceDisappeared event happen when restart mdmonitor service
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• 3.6-rc5 cgroups blkio throttle + md regression
  • From: Joseph Glanville <joseph.glanville@xxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: mdadm kernel log messages explained
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• mdadm kernel log messages explained
  • From: Adam Ryczkowski <adam.ryczkowski@xxxxxxxxxxxxxx>
• mdadm kernel log messages explained
  • From: Adam Ryczkowski <adam.ryczkowski@xxxxxxxxxxxxxx>
• Re: Wrong array size detected after reboot
  • From: Markus Irle <tha.bear@xxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• [PATCH] md: Add two chances to update sync/recovery checkpoint
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH] md/bitmap:Don't use IS_ERR to judge alloc_page().
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH] raid5: Avoid doing more read on dev of a stripe at the same time
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Small short question
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• [PATCH - v2] DM RAID: Fix for ineffective "sync" directive
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Small short question
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• [PATCH] fix: imsm: do not accept too small sizes
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• [PATCH] fix: adjust parse_size() to the unsigned size variable
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• [PATCH] fix: imsm: re-enable size expansion to the max value
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Small short question Was: Re: Recovering from the kernel bug, Neil?
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: Recovering from the kernel bug, Neil?
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• RAID0 DeviceDisappeared event happen when restart mdmonitor service
  • From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: raid5:bad sectors after lost power
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid5:bad sectors after lost power
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• Re: raid1 issue after disk failure: both disks of the array are still active
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• raid1 issue after disk failure: both disks of the array are still active
  • From: Niccolò Belli <darkbasic@xxxxxxxxxxxxxxx>
• RE: [PATCH] fix segfaults in Detail()
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: raid5:bad sectors after lost power
  • From: Mathias Buren <mathias.buren@xxxxxxxxx>
• raid5:bad sectors after lost power
  • From: "vincent" <hanguozhong@xxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: John Robinson <john.robinson@xxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Subject: [PATCH 1/1] drivers/md/raid1.c: fix NULL pointer bug in fix_read_error function
  • From: hank <pyu@xxxxxxxxxx>
• Re: Subject: [PATCH 1/1] drivers/md/raid1.c: fix NULL pointer bug in fix_read_error function
  • From: NeilBrown <neilb@xxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Mathias Buren <mathias.buren@xxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: GuoZhong Han <hanguozhong@xxxxxxxxxxxx>
• Re: Subject: [PATCH 1/1] drivers/md/raid1.c: fix NULL pointer bug in fix_read_error function
  • From: hank <pyu@xxxxxxxxxx>
• Re: Stop IMSM verify?
  • From: Daniel Frey <djqfrey@xxxxxxxxx>
• Re: Stop IMSM verify?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm forces resync every boot
  • From: Daniel Frey <djqfrey@xxxxxxxxx>
• Stop IMSM verify?
  • From: Daniel Frey <djqfrey@xxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: How can I ensure that my swraid saves checkpoints with sysrq reboot?
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: How can I ensure that my swraid saves checkpoints with sysrq reboot?
  • From: NeilBrown <neilb@xxxxxxx>
• How can I ensure that my swraid saves checkpoints with sysrq reboot?
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid6 low performance 8x3tb drives in singledegraded mode(=7x3tb)
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Howto avoid full re-sync
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Howto avoid full re-sync
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Re: raid6 low performance 8x3tb drives in singledegraded mode(=7x3tb)
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• R: Data recovery after the failure of two disks of 4
  • From: Carabetta Giulio <g.carabetta@xxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: make filesystem failed while the capacity of raid5 is big than 16TB
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• make filesystem failed while the capacity of raid5 is big than 16TB
  • From: "vincent" <hanguozhong@xxxxxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Can't reshape RAID1 to RAID5 due to chunk size
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: [patch 6/7 v2] MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• raid6 low performance 8x3tb drives in singledegraded mode(=7x3tb)
  • From: Kasper Sandberg <kontakt@xxxxxxxxxxxxxxxxxxx>
• Re: md: raid5 resync corrects read errors on data block - is this correct?
  • From: NeilBrown <neilb@xxxxxxx>
• md: raid5 resync corrects read errors on data block - is this correct?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [PATCH 1/3] raid: replace list_for_each_continue_rcu with new interface
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] raid: replace list_for_each_continue_rcu with new interface
  • From: Michael Wang <wangyun@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] raid: replace list_for_each_continue_rcu with new interface
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovering from the kernel bug, Neil?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 6/7 v2] MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Data recovery after the failure of two disks of 4
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch v2]raid5: fix directio regression
  • From: NeilBrown <neilb@xxxxxxx>
• Re: status of patches ( raid5 multiple threads )
  • From: NeilBrown <neilb@xxxxxxx>
• Re: question about bitmap for raid6
  • From: NeilBrown <neilb@xxxxxxx>
• status of patches ( raid5 multiple threads )
  • From: vincent Ferrer <vincentchicago1@xxxxxxxxx>
• FW: question about bitmap for raid6
  • From: Ming Lei <Ming.Lei@xxxxxxxxxxxx>
• Re: Howto avoid full re-sync
  • From: Ralf Müller <ralf@xxxxxxxx>
• Re: Recovering from the kernel bug, Neil?
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: [PATCH 1/3] raid: replace list_for_each_continue_rcu with new interface
  • From: Michael Wang <wangyun@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH RESEND] Fix and extend raid6check repair
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] DM RAID: Fix for ineffective "sync" directive
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Howto avoid full re-sync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Safe disk replace
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Wrong array size detected after reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Howto avoid full re-sync
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Recovering from the kernel bug, Neil?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovering from the kernel bug, Neil?
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: Wrong array size detected after reboot
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Wrong array size detected after reboot
  • From: Markus Irle <tha.bear@xxxxxxxxx>
• Re: Howto avoid full re-sync
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Howto avoid full re-sync
  • From: Ralf Müller <ralf@xxxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• [PATCH] dm mpath: move the dereference below the NULL test
  • From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
• Re: Issue with md and 4K sector alignment
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Howto avoid full re-sync
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Content Of Files May Be Changed After One Disk Is Failed In RAID5
  • From: clplayer <cl.player@xxxxxxxxx>
• Re: Issue with md and 4K sector alignment
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• [PATCH] fix segfaults in Detail()
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: Safe disk replace
  • From: John Drescher <drescherjm@xxxxxxxxx>
• [PATCH] dm-bufio: use list_move instead of list_del/list_add
  • From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
• Re: Safe disk replace
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• [PATCH 3/3] raid5:Move comment to func handle_stripe.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH 2/3] raid5: If stripe was on delay state,it don't judge other disks state.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH 1/3] raid5: remove unnecessary parameter.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH 0/3][trivial] Fix some trivial bugs
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Safe disk replace
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: [PATCH] DM RAID: Fix comparison of index and quantity for "rebuild" parameter
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Safe disk replace
  • From: John Drescher <drescherjm@xxxxxxxxx>
• Re: Safe disk replace
  • From: John Drescher <drescherjm@xxxxxxxxx>
• [PATCH] DM RAID: Fix comparison of index and quantity for "rebuild" parameter
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: [PATCH 1 of 3] MD RAID10: Prep for DM RAID10 device replacement capability
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH] DM RAID: Fix for ineffective "sync" directive
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Safe disk replace
  • From: John Drescher <drescherjm@xxxxxxxxx>
• Data recovery after the failure of two disks of 4
  • From: Carabetta Giulio <g.carabetta@xxxxxx>
• Re: [PATCH 1 of 3] MD RAID10: Prep for DM RAID10 device replacement capability
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] DM RAID: Fix for ineffective "sync" directive
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problems after extending partition [SOLVED]
  • From: Ross Boylan <ross@xxxxxxxxxxxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: Ric Wheeler <ricwheeler@xxxxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: Chris Friesen <chris.friesen@xxxxxxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: Ric Wheeler <ricwheeler@xxxxxxxxx>
• RFC: use TRIM data from filesystems to speed up array rebuild?
  • From: Chris Friesen <chris.friesen@xxxxxxxxxxx>
• Re: Safe disk replace
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Safe disk replace
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Safe disk replace
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Safe disk replace
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Safe disk replace
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Safe disk replace
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• Subject: [PATCH 1/1] drivers/md/raid1.c: fix NULL pointer bug in fix_read_error function
  • From: hank <pyu@xxxxxxxxxx>
• Re: mdadm.conf on Ubuntu - it's alive!
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• RE: mdadm.conf on Ubuntu - it's alive!
  • From: Gilbert Standen <gstanden@xxxxxxxxxxxxxx>
• Re: [PATCH] debian: symlink mdmon pidfile into /run/sendsigs.omit.d
  • From: Miquel van Smoorenburg <mikevs@xxxxxxxxxx>
• Re: Problems after extending partition
  • From: Ross Boylan <ross@xxxxxxxxxxxxxxxx>
• Re: Problems after extending partition
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Problems after extending partition
  • From: Ross Boylan <ross@xxxxxxxxxxxxxxxx>
• Re: [patch 0/7 v2] MD linear/0/1/10/5 TRIM support
  • From: Shaohua Li <shli@xxxxxxxxxxxx>
• Re: [patch 0/7 v2] MD linear/0/1/10/5 TRIM support
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [patch 0/7 v2] MD linear/0/1/10/5 TRIM support
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• [RFC][PATCH] Immutable bio vecs
  • From: Kent Overstreet <koverstreet@xxxxxxxxxx>
• Re: mdadm: Assemble.c: "force-one" update conflicts with the split-brain protection logic
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• md raid with lvm lv member
  • From: Markus Falb <markus.falb@xxxxxxxx>
• [PATCH 3 of 3] DM RAID: Add rebuild capability for RAID10
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 2 of 3] DM RAID: Move 'rebuild' checking code to its own function
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 1 of 3] MD RAID10: Prep for DM RAID10 device replacement capability
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: [PATCH] debian: symlink mdmon pidfile into /run/sendsigs.omit.d
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] debian: symlink mdmon pidfile into /run/sendsigs.omit.d
  • From: Miquel van Smoorenburg <mikevs@xxxxxxxxxx>
• Re: [PATCH] debian: symlink mdmon pidfile into /run/sendsigs.omit.d
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• [PATCH] debian: symlink mdmon pidfile into /run/sendsigs.omit.d
  • From: Miquel van Smoorenburg <mikevs@xxxxxxxxxx>
• Re: Confusion about chunk/stripe size mdadm in combination with LVM stripe size
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: kedacomkernel <kedacomkernel@xxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 1/3] raid: replace list_for_each_continue_rcu with new interface
  • From: Michael Wang <wangyun@xxxxxxxxxxxxxxxxxx>
• Re: Lose two disks during Raid 10 rebuild
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] DM RAID: Fix for ineffective "sync" directive
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Confusion about chunk/stripe size mdadm in combination with LVM stripe size
  • From: Caspar Smit <c.smit@xxxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Dan Williams <djbw@xxxxxx>
• mdadm: Assemble.c: "force-one" update conflicts with the split-brain protection logic
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Spares not added upon reboot after distro upgrade
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Re: Spares not added upon reboot after distro upgrade
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Re: md raid6 not working
  • From: "Vanhorn, Mike" <michael.vanhorn@xxxxxxxxxx>
• Re: Spares not added upon reboot after distro upgrade
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• [PATCH] raid5: remove unnecessary "set_bit(STRIPE_HANDLE,&sh->state)" in func handle_stripe_dirtying.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• RE: Re: raid5: When add stripe_head to inactive_list, it should remove hash.
  • From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Shaohua Li <shli@xxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Re: raid5: When add stripe_head to inactive_list, it should remove hash.
  • From: kedacomkernel <kedacomkernel@xxxxxxxxx>
• Re: md raid6 not working
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: raid5: When add stripe_head to inactive_list, it should remove hash.
  • From: Dan Williams <djbw@xxxxxx>
• Re: Controller problems during reshape -> can't continue reshape after reboot.
  • From: Michael-John Turner <mj@xxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Miquel van Smoorenburg <mikevs@xxxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Fengguang Wu <fengguang.wu@xxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• RE: md raid6 not working
  • From: "Vanhorn, Mike" <michael.vanhorn@xxxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• Re: mdadm --monitor: need extra feature?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• mdadm --monitor: need extra feature?
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Fengguang Wu <fengguang.wu@xxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Controller problems during reshape -> can't continue reshape after reboot.
  • From: Tim Small <tim@xxxxxxxxxxxxxxxx>
• Re: Controller problems during reshape -> can't continue reshape after reboot.
  • From: Tim Small <tim@xxxxxxxxxxxxxxxx>
• Re: Re: raid5: When add stripe_head to inactive_list, it should remove hash.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Controller problems during reshape -> can't continue reshape after reboot.
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] raid: replace list_for_each_continue_rcu with new interface
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• Re: Controller problems during reshape -> can't continue reshape after reboot.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md raid6 not working
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm -add doesn't start rebuilding array
  • From: NeilBrown <neilb@xxxxxxx>
• Controller problems during reshape -> can't continue reshape after reboot.
  • From: Tim Small <tim@xxxxxxxxxxxxxxxx>
• md raid6 not working
  • From: "Vanhorn, Mike" <michael.vanhorn@xxxxxxxxxx>
• Re: raid5: When add stripe_head to inactive_list, it should remove hash.
  • From: Dan Williams <djbw@xxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Using SCSI timeouts in place of ERC
  • From: joystick <joystick@xxxxxxxxxxxxx>
• mdadm -add doesn't start rebuilding array
  • From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
• Re: raid5: When add stripe_head to inactive_list, it should remove hash.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Issue with md and 4K sector alignment
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Issue with md and 4K sector alignment
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: Inexpensive RAID1 controller for home server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: Richard Scobie <r.scobie@xxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Inexpensive RAID1 controller for home server?
  • From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: NeilBrown <neilb@xxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Inexpensive RAID1 controller for home server?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: Inexpensive RAID1 controller for home server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Issue with md and 4K sector alignment
  • From: Kyle Brantley <kyle@xxxxxxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Recovering from the kernel bug
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Inexpensive RAID1 controller for home server?
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: md raid behavior, bad sector uncorrectable read error
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Spares not added upon reboot after distro upgrade
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Re: Inexpensive RAID1 controller for home server?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Inexpensive RAID1 controller for home server?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• md raid behavior, bad sector uncorrectable read error
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Few questions about TRIM/discard
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Inexpensive RAID1 controller for home server?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Still problems with ddf stuff
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• raid5: When add stripe_head to inactive_list, it should remove hash.
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PULL REQUEST] md: 2 patches, both heading for -stable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md: raid 10 supports TRIM
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdraid6 problem post 3.5.0
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID extremely slow
  • From: Jan Engelhardt <jengelh@xxxxxxx>
• RE: Array rebuilding over and over
  • From: "Singer, Benedict" <bzsing@xxxxxxxxx>
• Re: Array rebuilding over and over
  • From: NeilBrown <neilb@xxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: NeilBrown <neilb@xxxxxxx>
• Array rebuilding over and over
  • From: "Singer, Benedict" <bzsing@xxxxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: ext4 write performance regression in 3.6-rc1 on RAID0/5
  • From: Fengguang Wu <fengguang.wu@xxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: md: raid 10 supports TRIM
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md: raid 10 supports TRIM
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PATCH 1/3] raid: replace list_for_each_continue_rcu with new interface
  • From: Michael Wang <wangyun@xxxxxxxxxxxxxxxxxx>
• [PATCH 0/3] raid, kmemleak, netfilter: replace list_for_each_continue_rcu with new interface
  • From: Michael Wang <wangyun@xxxxxxxxxxxxxxxxxx>
• Re: md: raid 10 supports TRIM
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Backup file size when migrating from raid5 to raid6?
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Backup file size when migrating from raid5 to raid6?
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Backup file size when migrating from raid5 to raid6?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Backup file size when migrating from raid5 to raid6?
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: vincent Ferrer <vincentchicago1@xxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: vincent Ferrer <vincentchicago1@xxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: Flynn <flynn@xxxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• re: md: raid 10 supports TRIM
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: raid5 to utilize upto 8 cores
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• raid5 to utilize upto 8 cores
  • From: vincent Ferrer <vincentchicago1@xxxxxxxxx>
• [PATCH] MAINTAINERS: update address for Dan Williams
  • From: Dan Williams <djbw@xxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID5 - Disk failed during re-shape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: O_DIRECT to md raid 6 is slow
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Error in rebuild of two "layered" md devices in container
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• RE: RAID5 - Disk failed during re-shape
  • From: Sam Clark <sclark_77@xxxxxxxxxxx>
• [PATCH RESEND] Fix and extend raid6check repair
  • From: Robert Buchholz <robert.buchholz@xxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: md raid10 Oops on recent kernels
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: [patch v2]raid5: fix directio regression
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Re: O_DIRECT to md raid 6 is slow
  • From: kedacomkernel <kedacomkernel@xxxxxxxxx>
• Re: Re: [patch v2]raid5: fix directio regression
  • From: kedacomkernel <kedacomkernel@xxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: O_DIRECT to md raid 6 is slow
  • From: kedacomkernel <kedacomkernel@xxxxxxxxx>
• Re: [patch v2]raid5: fix directio regression
  • From: NeilBrown <neilb@xxxxxxx>
• O_DIRECT to md raid 6 is slow
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: Error in rebuild of two "layered" md devices in container
  • From: NeilBrown <neilb@xxxxxxx>
• Re: ddf failed disk disappears after adding spare
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Version 3.2.5 and ddf issues (bugreport)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID5 - Disk failed during re-shape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md raid10 Oops on recent kernels
  • From: Ivan Vasilyev <ivan.vasilyev@xxxxxxxxx>
• RE: RAID5 - Disk failed during re-shape
  • From: Sam Clark <sclark_77@xxxxxxxxxxx>
• Re: Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [patch v2]raid5: fix directio regression
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] query udev dir via pkg-config
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: RAID5 - Disk failed during re-shape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md raid10 Oops on recent kernels
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Manage.c: fix make everything compilation error
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RFC: Add WWN in superblock
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] sha1.h: remove ansidecl.h header inclusion
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md/linear: rcu_dereference outside read-lock section
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] query udev dir via pkg-config
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md/linear: rcu_dereference outside read-lock section
  • From: Denis Efremov <yefremov.denis@xxxxxxxxx>
• [PATCH] query udev dir via pkg-config
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Re: Experience of LSI MegaRAID 9260CV?
  • From: Marcus Sorensen <shadowsor@xxxxxxxxx>
• md raid10 Oops on recent kernels
  • From: Ivan Vasilyev <ivan.vasilyev@xxxxxxxxx>
• [PATCH] sha1.h: remove ansidecl.h header inclusion
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• RFC: Add WWN in superblock
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [PATCH] Manage.c: fix make everything compilation error
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Experience of LSI MegaRAID 9260CV?
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Disk Order
  • From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Device Unusable At Startup
  • From: Jake Thomas <thomasj10@xxxxxxxxxxxxx>
• Re: Device Unusable At Startup
  • From: Jake Thomas <thomasj10@xxxxxxxxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 6/7 v2] MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 6/7 v2] MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 6/7 v2] MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 0/7 v2] MD linear/0/1/10/5 TRIM support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 6/7 v2] MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Disk Order
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Device Unusable At Startup
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Disk Order
  • From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
• Re: Disk Order
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Device Unusable At Startup
  • From: Jake Thomas <thomasj10@xxxxxxxxxxxxx>
• Re: Disk Order
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Disk Order
  • From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
• Re: Disk Order
  • From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID5 - Disk failed during re-shape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Disk Order
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Device Unusable At Startup
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Device Unusable At Startup
  • From: Jake Thomas <thomasj10@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] mdassemble: split dietlibc logic into dedicated target
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] fix handling of CPPFLAGS
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Grow.c: change size to be unsigned and use '0' in case of 'no change'
  • From: NeilBrown <neilb@xxxxxxx>
• Disk Order
  • From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
• [PATCH 2/2] mdassemble: split dietlibc logic into dedicated target
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• [PATCH 1/2] fix handling of CPPFLAGS
  • From: Mike Frysinger <vapier@xxxxxxxxxx>
• Solved! (was Re: RAID6 Reshape (one more time))
  • From: Flynn <flynn@xxxxxxxxxxx>
• Re: [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: RAID5 - Disk failed during re-shape
  • From: Sam Clark <sclark_77@xxxxxxxxxxx>
• Re: RAID5 - Disk failed during re-shape
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• Re: RAID5 - Disk failed during re-shape
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Re: [PATCH 0/8] Set bi_rw when alloc bio before call bio_add_page.
  • From: Muthu Kumar <muthu.lkml@xxxxxxxxx>
• RE: What does the '-1' value of size mean now?
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• [PATCH] Grow.c: change size to be unsigned and use '0' in case of 'no change'
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• [patch 7/7 v2] MD: raid5 avoid unnecessary zero page for trim
  • From: Shaohua Li <shli@xxxxxxxxxxxx>
• [patch 6/7 v2] MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxxxx>
• [patch 5/7 v2] md: raid 10 supports TRIM
  • From: Shaohua Li <shli@xxxxxxxxxxxx>
• [patch 4/7 v2] md: raid 1 supports TRIM
  • From: Shaohua Li <shli@xxxxxxxxxxxx>
• [patch 3/7 v2] md: raid 0 supports TRIM
  • From: Shaohua Li <shli@xxxxxxxxxxxx>
• [patch 2/7 v2] md: linear supports TRIM
  • From: Shaohua Li <shli@xxxxxxxxxxxx>
• [patch 1/7 v2] block: makes bio_split support bio without data
  • From: Shaohua Li <shli@xxxxxxxxxxxx>
• [patch 0/7 v2] MD linear/0/1/10/5 TRIM support
  • From: Shaohua Li <shli@xxxxxxxxxxxx>
• Re: RAID10 Performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: replaced disk in RAID1 imsm array - how to activate?
  • From: Miquel van Smoorenburg <mikevs@xxxxxxxxxx>
• What does the '-1' value of size mean now?
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: replaced disk in RAID1 imsm array - how to activate?
  • From: Miquel van Smoorenburg <mikevs@xxxxxxxxxx>
• Re: replaced disk in RAID1 imsi array - how to activate?
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• replaced disk in RAID1 imsi array - how to activate?
  • From: Miquel van Smoorenburg <mikevs@xxxxxxxxxx>
• [patch 2/2 v3]raid5: create multiple threads to handle stripes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 1/2 V3]MD: change the parameter of md thread
  • From: Shaohua Li <shli@xxxxxxxxxx>
• RAID5 - Disk failed during re-shape
  • From: Sam Clark <sclark_77@xxxxxxxxxxx>
• Re: What happened to TRIM support for raid linear/0/1/10?
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch]raid5: fix directio regression
  • From: Shaohua Li <shli@xxxxxxxxxx>
• RAID6 Reshape (one more time)
  • From: Flynn <flynn@xxxxxxxxxxx>
• Re: What happened to TRIM support for raid linear/0/1/10?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [patch]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: [patch]raid5: fix directio regression
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: [patch]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: RAID10 Performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID10 Performance
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RAID10 Performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• What happened to TRIM support for raid linear/0/1/10?
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: Re: [patch]raid5: fix directio regression
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Re: [patch]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: RAID10 Performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [RFC v2]raid5: create multiple threads to handle stripes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Re: [patch]raid5: fix directio regression
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [RFC v2]raid5: create multiple threads to handle stripes
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Re: [patch]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: Re: [patch]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Re: [patch]raid5: fix directio regression
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch]raid5: fix directio regression
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• [patch]raid5: fix directio regression
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH] md/raid5: Fix two small bugs in init_stripe().
  • From: "Jianpeng Ma" <majianpeng@xxxxxxxxx>
• Device Unusable At Startup
  • From: Jake Thomas <thomasj10@xxxxxxxxxxxxx>
• swapping a single drive with a RAID-1 array. At array boot, "No Boot Device found". What've I missed?
  • From: pgn14@xxxxxxxxxxxxxx
• Re: How does one assemble a DDF or IMSM array?
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: RAID6 Reshape Gone Awry
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID6 Reshape Gone Awry
  • From: Flynn <flynn@xxxxxxxxxxx>
• Re: RAID6 Reshape Gone Awry
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: RAID6 Reshape Gone Awry
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID6 Reshape Gone Awry
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: How does one assemble a DDF or IMSM array?
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• RAID6 Reshape Gone Awry
  • From: Flynn <flynn@xxxxxxxxxxx>
• SparesMissing event
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• How does one assemble a DDF or IMSM array?
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: listy@xxxxxxxxxxx
• Re: OT: silent data corruption reading from hard drives
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Jeff Johnson <jeff.johnson@xxxxxxxxxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: listy@xxxxxxxxxxx
• Re: OT: silent data corruption reading from hard drives
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Iustin Pop <iusty@xxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: [PATCH 1/2 V1] [PATCH] fs/block-dev.c:fix performance regression in O_DIRECT writes to md block devices
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Re: [PATCH 1/2 V1] [PATCH] fs/block-dev.c:fix performance regression in O_DIRECT writes to md block devices
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PULL REQUEST] few more md patches now that dependencies are present.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] udev-rules: prevent systemd from mount devices before they are ready.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Version 3.2.5 and ddf issues (bugreport)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Error in rebuild of two "layered" md devices in container
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Error in rebuild of two "layered" md devices in container
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: ddf failed disk disappears after adding spare
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: ddf failed disk disappears after adding spare
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: OT: silent data corruption reading from hard drives
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: persistent removed MD referrence on reboot
  • From: Skip Coombe <skipcoombe@xxxxxxxxx>
• OT: silent data corruption reading from hard drives
  • From: matt <listy@xxxxxxxxxxx>
• Re: [PULL REQUEST] md update for 3.6
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PULL REQUEST] md update for 3.6
  • From: NeilBrown <neilb@xxxxxxx>
• ddf failed disk disappears after adding spare
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: persistent removed MD referrence on reboot
  • From: linbloke <linbloke@xxxxxxxxxxx>
• Re: persistent removed MD referrence on reboot
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• [RFC v2]raid5: create multiple threads to handle stripes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: RAID extremely slow
  • From: Bill Davidsen <davidsen@xxxxxxx>
• [PATCH v5] DM RAID: Add support for MD RAID10
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• How does one assemble a DDF or IMSM array?
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: persistent removed MD referrence on reboot
  • From: Skip Coombe <skipcoombe@xxxxxxxxx>
• Re: [PATCH 0/4] Plugging changes for blk/md/umem
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] udev-rules: prevent systemd from mount devices before they are ready.
  • From: harald@xxxxxxxxxx
• Re: Version 3.2.5 and ddf issues (bugreport)
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: [PATCH 0/4] Plugging changes for blk/md/umem
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 0/4] Plugging changes for blk/md/umem
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 0/4] Plugging changes for blk/md/umem
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/4] Plugging changes for blk/md/umem
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Version 3.2.5 and ddf issues (bugreport)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1 repair: sync_request() aborts if one of the drives has bad block recorded
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1 repair: sync_request() aborts if one of the drives has bad block recorded
  • From: NeilBrown <neilb@xxxxxxx>
• Re: persistent removed MD referrence on reboot
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Re: [PATCH 0/8] Set bi_rw when alloc bio before call bio_add_page.
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• persistent removed MD referrence on reboot
  • From: Skip Coombe <skipcoombe@xxxxxxxxx>
• Re: [RFC PATCH] fs/direct-io.c: Set bi_rw when alloc bio.
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: problem hot-adding spare / internal bitmap problem?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Re: [RFC PATCH] fs/direct-io.c: Set bi_rw when alloc bio.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: problem hot-adding spare / internal bitmap problem?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: problem hot-adding spare / internal bitmap problem?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• problem hot-adding spare / internal bitmap problem?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: RAID10 Performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Version 3.2.5 and ddf issues (bugreport)
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Version 3.2.5 and ddf issues (bugreport)
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: RAID extremely slow
  • From: Kevin Ross <kevin@xxxxxxxxxxxxxx>
• Re: RAID10 Performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID extremely slow
  • From: Grant Coady <gcoady.lk@xxxxxxxxx>
• Re: RAID extremely slow
  • From: Kevin Ross <kevin@xxxxxxxxxxxxxx>
• Re: RAID extremely slow
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: RAID10 Performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Re: [RFC PATCH] fs/direct-io.c: Set bi_rw when alloc bio.
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: [RFE] Please, add optional RAID1 feature (= chunk checksums) to make it more robust
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RAID10 Performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID10 Performance
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [RFC PATCH] fs/direct-io.c: Set bi_rw when alloc bio.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: RAID10 Performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [RFE] Please, add optional RAID1 feature (= chunk checksums) to make it more robust
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID extremely slow
  • From: Kevin Ross <kevin@xxxxxxxxxxxxxx>
• Re: RAID extremely slow
  • From: David Dillow <dave@xxxxxxxxxxxxxx>
• Re: RAID extremely slow
  • From: David Dillow <dave@xxxxxxxxxxxxxx>
• Re: RAID extremely slow
  • From: Kevin Ross <kevin@xxxxxxxxxxxxxx>
• Re: RAID extremely slow
  • From: David Dillow <dave@xxxxxxxxxxxxxx>
• Re: RAID extremely slow
  • From: Kevin Ross <kevin@xxxxxxxxxxxxxx>
• Re: RAID extremely slow
  • From: Kevin Ross <kevin@xxxxxxxxxxxxxx>
• RAID10 Performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• [RFC 2/2]raid1: use discard if sync data is 0
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [RFC 1/2]raid1: only write mismatch sectors in sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: RAID extremely slow
  • From: Kevin Ross <kevin@xxxxxxxxxxxxxx>
• [PATCH 4/4] blk: pass from_schedule to non-request unplug functions.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 3/4] block: stack unplug
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 2/4] blk: centralize non-request unplug handling.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 1/4] md: remove plug_cnt feature of plugging.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 0/4] Plugging changes for blk/md/umem
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID extremely slow
  • From: Kevin Ross <kevin@xxxxxxxxxxxxxx>
• Re: RAID extremely slow
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: RAID extremely slow
  • From: Kevin Ross <kevin@xxxxxxxxxxxxxx>
• Re: RAID extremely slow
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Does mdadm require udev/sysfs to create imsm RAID1?
  • From: NeilBrown <neilb@xxxxxxx>
• Does mdadm require udev/sysfs to create imsm RAID1?
  • From: Scott Johnson <scottej23@xxxxxxxxx>
• Re: raid1 repair: sync_request() aborts if one of the drives has bad block recorded
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: smarter md minor search than "find_free_devnum" needed
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: [RFE] Please, add optional RAID1 feature (= chunk checksums) to make it more robust
  • From: Jaromir Capik <jcapik@xxxxxxxxxx>
• Re: Need to remove failed disk from RAID5 array
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: [RFE] Please, add optional RAID1 feature (= chunk checksums) to make it more robust
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Problem recovering failed Intel Rapid Storage raid5 volume
  • From: Khurram Hassan <kfhassan@xxxxxxxxx>
• Re: [RFE] Please, add optional RAID1 feature (= chunk checksums) to make it more robust
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH v4] DM RAID: Add support for MD RAID10
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH v4] DM RAID: Add support for MD RAID10
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH v4] DM RAID: Add support for MD RAID10
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problem recovering failed Intel Rapid Storage raid5 volume
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFE] Please, add optional RAID1 feature (= chunk checksums) to make it more robust
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: [RFE] Please, add optional RAID1 feature (= chunk checksums) to make it more robust
  • From: Drew <drew.kay@xxxxxxxxx>
• [PATCH v4] DM RAID: Add support for MD RAID10
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: [RFE] Please, add optional RAID1 feature (= chunk checksums) to make it more robust
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: [RFE] Please, add optional RAID1 feature (= chunk checksums) to make it more robust
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Problem recovering failed Intel Rapid Storage raid5 volume
  • From: Khurram Hassan <kfhassan@xxxxxxxxx>
• smarter md minor search than "find_free_devnum" needed
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: [RFE] Please, add optional RAID1 feature (= chunk checksums) to make it more robust
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [RFE] Please, add optional RAID1 feature (= chunk checksums) to make it more robust
  • From: Jaromir Capik <jcapik@xxxxxxxxxx>
• vulnerability during partition-size-growth procedures
  • From: Brendan Hide <brendan@xxxxxxxxxxxxxxxxx>
• Re: [RFE] Please, add optional RAID1 feature (= chunk checksums) to make it more robust
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [RFE] Please, add optional RAID1 feature (= chunk checksums) to make it more robust
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Need to remove failed disk from RAID5 array
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Question about how to migrate raid0 to raid5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 array tend to two degraded raid10 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problem recovering failed Intel Rapid Storage raid5 volume
  • From: NeilBrown <neilb@xxxxxxx>
• Re: "A Nasty md/raid bug"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Find mismatch in data blocks during raid6 repair
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Problem recovering failed Intel Rapid Storage raid5 volume
  • From: Khurram Hassan <kfhassan@xxxxxxxxx>
• "A Nasty md/raid bug"
  • From: "Peter Modrala" <x3m2@xxxxxxxxxx>