Linux RAID Storage Date Index

• Thread Index

• Re: md RAID with enterprise-class SATA or SAS drives
  • From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
• Re: and again: broken RAID5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: and again: broken RAID5
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Raid5 Array stopped suddenly, no apparent error messages.
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: and again: broken RAID5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Hot-replace for RAID5
  • From: Patrik Horník <patrik@xxxxxx>
• and again: broken RAID5
  • From: Lars Schimmer <l.schimmer@xxxxxxxxxxxxx>
• Re: Hot-replace for RAID5
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: md/raid10 deadlock at 'Failing raid device'
  • From: NeilBrown <neilb@xxxxxxx>
• md/raid10 deadlock at 'Failing raid device'
  • From: George Shuklin <george.shuklin@xxxxxxxxx>
• Re: md RAID with enterprise-class SATA or SAS drives
  • From: Richard Scobie <r.scobie@xxxxxxxxxxxx>
• Re: Another RAID-5 problem
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md RAID with enterprise-class SATA or SAS drives
  • From: Marcus Sorensen <shadowsor@xxxxxxxxx>
• Re: Interesting feature request for linux raid, waking up drives
  • From: Patrik Horník <patrik@xxxxxx>
• md RAID with enterprise-class SATA or SAS drives
  • From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
• Re: Interesting feature request for linux raid, waking up drives
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Interesting feature request for linux raid, waking up drives
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Interesting feature request for linux raid, waking up drives
  • From: Patrik Horník <patrik@xxxxxx>
• Re: Interesting feature request for linux raid, waking up drives
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• Re: Another RAID-5 problem
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• tracking parity mismatches to a failing disk
  • From: Michael Peterson <Michael.Peterson@xxxxxxxx>
• Raid5 Array stopped suddenly, no apparent error messages.
  • From: Brian McKee <brian@xxxxxxxxxxxxx>
• Interesting feature request for linux raid, waking up drives
  • From: Patrik Horník <patrik@xxxxxx>
• Re: Another RAID-5 problem
  • From: piergiorgio.sartor@xxxxxxxx
• Re: Another RAID-5 problem
  • From: NeilBrown <neilb@xxxxxxx>
• Another RAID-5 problem
  • From: piergiorgio.sartor@xxxxxxxx
• Re: [RFC 1/2] MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch v2 0/6] Add TRIM support for raid linear/0/1/10
  • From: Shaohua Li <shli@xxxxxxxxxxxx>
• ANNOUNCE: mdadm 3.2.4 - A tool for managing Soft RAID under Linux
  • From: NeilBrown <neilb@xxxxxxx>
• Re: tarballs in www.kernel.org with wrong extension
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Failed drive while converting raid5 to raid6, then a hard reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Failed drive while converting raid5 to raid6, then a hard reboot
  • From: Hákon Gíslason <hakon.gislason@xxxxxxxxx>
• Re: Failed drive while converting raid5 to raid6, then a hard reboot
  • From: Hákon Gíslason <hakon.gislason@xxxxxxxxx>
• Re: Failed drive while converting raid5 to raid6, then a hard reboot
  • From: Hákon Gíslason <hakon.gislason@xxxxxxxxx>
• Re: Failed drive while converting raid5 to raid6, then a hard reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Failed drive while converting raid5 to raid6, then a hard reboot
  • From: Hákon Gíslason <hakon.gislason@xxxxxxxxx>
• Re: Failed drive while converting raid5 to raid6, then a hard reboot
  • From: Hákon Gíslason <hakon.gislason@xxxxxxxxx>
• Re: logging the last state of the disk subsystem
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Failed drive while converting raid5 to raid6, then a hard reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Yet another corrupt raid5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC 1/2] MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC]md: using GFP_NOIO to allocate bio for flush request
  • From: NeilBrown <neilb@xxxxxxx>
• Re: logging the last state of the disk subsystem
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [RFC]md: using GFP_NOIO to allocate bio for flush request
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: help: re-add needed after each reboot
  • From: "D. Lin" <dlbulk-mllr@xxxxxxxxx>
• Re: Reason for md raid1 max_sectors_kb limited to 127?
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: [RFC 1/2] MD: raid5 trim support
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: create raid10 md raid which hangs on auto-read-only with resync=PENDING
  • From: Nikolay Kichukov <hijacker@xxxxxxxxx>
• Re: [RFC]md: using GFP_NOIO to allocate bio for flush request
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [RFC 1/2] MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 4/4] raid1: split large request for SSD
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 3/4] raid1: read balance chooses idlest disk
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 2/4] raid1: make sequential read detection per disk based
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 1/4] raid1: move distance based read balance to a separate function
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 0/4] Optimize raid1 read balance for SSD
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: mdadm v3.1.3 spare group does not work
  • From: NeilBrown <neilb@xxxxxxx>
• RE: [patch v2 0/6] Add TRIM support for raid linear/0/1/10
  • From: "Patelczyk, Maciej" <maciej.patelczyk@xxxxxxxxx>
• RE: mdadm v3.1.3 spare group does not work
  • From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
• Hot-replace for RAID5
  • From: Patrik Horník <patrik@xxxxxx>
• Re: help: re-add needed after each reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: help: re-add needed after each reboot
  • From: "D. Lin" <dlbulk-mllr@xxxxxxxxx>
• RE: mdadm v3.1.3 spare group does not work
  • From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
• RE: mdadm v3.1.3 spare group does not work
  • From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
• Re: mdadm v3.1.3 spare group does not work
  • From: NeilBrown <neilb@xxxxxxx>
• mdadm v3.1.3 spare group does not work
  • From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
• Re: Feature request for mdadm 3.3
  • From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
• Feature request for mdadm 3.3
  • From: Patrik Horník <patrik@xxxxxx>
• Re: help: re-add needed after each reboot
  • From: NeilBrown <neilb@xxxxxxx>
• help: re-add needed after each reboot
  • From: "D. Lin" <dlbulk-mllr@xxxxxxxxx>
• Re: Reason for md raid1 max_sectors_kb limited to 127?
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
• Re: Reason for md raid1 max_sectors_kb limited to 127?
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: Reason for md raid1 max_sectors_kb limited to 127?
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
• Re: Reason for md raid1 max_sectors_kb limited to 127?
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
• Re: Reason for md raid1 max_sectors_kb limited to 127?
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: Reason for md raid1 max_sectors_kb limited to 127?
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: Reason for md raid1 max_sectors_kb limited to 127?
  • From: NeilBrown <neilb@xxxxxxx>
• Reason for md raid1 max_sectors_kb limited to 127?
  • From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• 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: Garðar Arnarsson <gardar@xxxxxxxxxxx>
• Re: [PATCH 1/2] super-intel.c: Don't try to close negative fd
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Backup file size when migrating from raid5 to raid6?
  • From: NeilBrown <neilb@xxxxxxx>
• Backup file size when migrating from raid5 to raid6?
  • From: Garðar Arnarsson <gardar@xxxxxxxxxxx>
• Re: Yet another corrupt raid5
  • From: Philipp Wendler <ml@xxxxxxxxxxxxxxxxx>
• Re: logging the last state of the disk subsystem
  • From: Ivan Fedorets <ivan.fedorets@xxxxxxxxx>
• Re: Yet another corrupt raid5
  • From: NeilBrown <neilb@xxxxxxx>
• tarballs in www.kernel.org with wrong extension
  • From: "Joao Cardoso (Alt-F)" <whoami.jcard@xxxxxxxxx>
• Yet another corrupt raid5
  • From: Philipp Wendler <ml@xxxxxxxxxxxxxxxxx>
• Re: Script for offsite storeage of RAID info needed for recovery
  • From: Martin Wegner <mw@xxxxxxxxx>
• Re: [PATCH 1/2] super-intel.c: Don't try to close negative fd
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Script for offsite storeage of RAID info needed for recovery
  • From: Krzysztof Adamski <k@xxxxxxxxxxx>
• Re: [BISECT] Kernel panic, RIP bitmap_create
  • From: Karl Newman <siliconfiend@xxxxxxxxx>
• [PATCH 2/2] super-intel.c: Fix resource leak from opendir()
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 1/2] super-intel.c: Don't try to close negative fd
  • From: Jes.Sorensen@xxxxxxxxxx
• [PULL REQUEST] one bugfix for md in 3.4.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [BISECT] Kernel panic, RIP bitmap_create
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [BISECT] Kernel panic, RIP bitmap_create
  • From: Karl Newman <siliconfiend@xxxxxxxxx>
• Moving drives from different PC's advice please.
  • From: wilsonjonathan <piercing_male@xxxxxxxxxxx>
• Re: create raid10 md raid which hangs on auto-read-only with resync=PENDING
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Last call for input to mdadm-3.2.4
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• create raid10 md raid which hangs on auto-read-only with resync=PENDING
  • From: Nikolay Kichukov <hijacker@xxxxxxxxx>
• Re: Monitoring for failed drives
  • From: Brian Candler <B.Candler@xxxxxxxxx>
• Re: [BISECT] Kernel panic, RIP bitmap_create
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] arch/x86: use kernel_fpu_[begin|end] for RAID5 checksumming
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [BISECT] Kernel panic, RIP bitmap_create
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [BISECT] Kernel panic, RIP bitmap_create
  • From: Karl Newman <siliconfiend@xxxxxxxxx>
• Re: [BISECT] Kernel panic, RIP bitmap_create
  • From: NeilBrown <neilb@xxxxxxx>
• [BISECT] Kernel panic, RIP bitmap_create
  • From: Karl Newman <siliconfiend@xxxxxxxxx>
• Re: [PATCH] arch/x86: use kernel_fpu_[begin|end] for RAID5 checksumming
  • From: NeilBrown <neilb@xxxxxxx>
• Last call for input to mdadm-3.2.4
  • From: NeilBrown <neilb@xxxxxxx>
• Re: async_tx and RAID HW xor engine
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: linbloke <linbloke@xxxxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Alex <creamyfish@xxxxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: Brian Candler <B.Candler@xxxxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: Brian Candler <B.Candler@xxxxxxxxx>
• Re: Another corrupt RAID5
  • From: NeilBrown <neilb@xxxxxxx>
• Another corrupt RAID5
  • From: Andrew Thrift <andrew@xxxxxxxxxxxxxxxxx>
• Re: async_tx and RAID HW xor engine
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] arch/x86: use kernel_fpu_[begin|end] for RAID5 checksumming
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• Re: async_tx and RAID HW xor engine
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: recovering from raid5 corruption
  • From: Shaya Potter <spotter@xxxxxxxxx>
• Failed drive while converting raid5 to raid6, then a hard reboot
  • From: Hákon Gíslason <hakon.gislason@xxxxxxxxx>
• Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
  • From: Paweł Brodacki <pawel.brodacki@xxxxxxxxxxxxxx>
• async_tx and RAID HW xor engine
  • From: Rajasekhar Pulluru <pullururajasekhar@xxxxxxxxx>
• Re: recovering from raid5 corruption
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Re: recovering from raid5 corruption
  • From: Shaya Potter <spotter@xxxxxxxxx>
• Re: recovering from raid5 corruption
  • From: NeilBrown <neilb@xxxxxxx>
• Re: recovering from raid5 corruption
  • From: Shaya Potter <spotter@xxxxxxxxx>
• Re: [PATCH] imsm: fix: thunderdome may drop 2tb attribute
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
  • From: NeilBrown <neilb@xxxxxxx>
• Re: recovering from raid5 corruption
  • From: Shaya Potter <spotter@xxxxxxxxx>
• Re: recovering from raid5 corruption
  • From: NeilBrown <neilb@xxxxxxx>
• Re: recovering from raid5 corruption
  • From: NeilBrown <neilb@xxxxxxx>
• Re: recovering from raid5 corruption
  • From: Shaya Potter <spotter@xxxxxxxxx>
• Re: recovering from raid5 corruption
  • From: Shaya Potter <spotter@xxxxxxxxx>
• Re: recovering from raid5 corruption
  • From: NeilBrown <neilb@xxxxxxx>
• recovering from raid5 corruption
  • From: Shaya Potter <spotter@xxxxxxxxx>
• Re: mdadm: ioctl(GET_DISK_INFO) question
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
• Re: [Doubt] how is a disk marked faulty in RAID5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm: ioctl(GET_DISK_INFO) question
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help to assemble raid5 - no superblock!
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 issues after reorder of boot drives.
  • From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
• Re: [Doubt] how is a disk marked faulty in RAID5
  • From: Anuj Goel <agoel@xxxxxxxxxxxxxxxxx>
• raid10 issues after reorder of boot drives.
  • From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Emmanuel Noobadmin <centos.admin@xxxxxxxxx>
• mdadm: ioctl(GET_DISK_INFO) question
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Help to assemble raid5 - no superblock!
  • From: Salatiel Filho <salatiel.filho@xxxxxxxxx>
• RE: [PATCH] imsm: fix: thunderdome may drop 2tb attribute
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• Re: dmesg deluge: RAID1 conf printout
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Removing a failing drive from multiple arrays
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
  • From: Richard Henderson <rth@xxxxxxxxxxx>
• Re: [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• [PATCH 2/2] Introduce sysfs_set_num_signed() and use it to set bitmap/offset
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/2] Solve problem adding internal bitmaps to 1.0 arrays
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: Removing a failing drive from multiple arrays
  • From: Brian Candler <B.Candler@xxxxxxxxx>
• Re: Removing a failing drive from multiple arrays
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Verify an error from ioctl STOP_ARRAY is missing
  • From: "Tomczak, Marcin" <marcin.tomczak@xxxxxxxxx>
• Re: Removing a failing drive from multiple arrays
  • From: Brian Candler <B.Candler@xxxxxxxxx>
• Re: Removing a failing drive from multiple arrays
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Alex <creamyfish@xxxxxxxxx>
• Re: RAID6 fails to assemble after unclean shutdown
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID6 fails to assemble after unclean shutdown
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: md raid recovery - perplexed
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Removing a failing drive from multiple arrays
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Alex <creamyfish@xxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Emmanuel Noobadmin <centos.admin@xxxxxxxxx>
• Re: Monitoring for failed drives
  • From: Brian Candler <B.Candler@xxxxxxxxx>
• Re: Monitoring for failed drives
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Monitoring for failed drives
  • From: Brian Candler <B.Candler@xxxxxxxxx>
• Re: RAID6 fails to assemble after unclean shutdown
  • From: Brian Candler <B.Candler@xxxxxxxxx>
• Re: Unable to grow raid10 (error -22)
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: RAID6 fails to assemble after unclean shutdown
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Unable to grow raid10 (error -22)
  • From: NeilBrown <neilb@xxxxxxx>
• RAID6 fails to assemble after unclean shutdown
  • From: Brian Candler <B.Candler@xxxxxxxxx>
• Unable to grow raid10 (error -22)
  • From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
• Re: Raid1: sdb has a lot mor work then sda
  • From: Kay Diederichs <kay.diederichs@xxxxxxxxxxxxxxx>
• Re: [RFC 1/2] MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Alex <creamyfish@xxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Removing a failing drive from multiple arrays
  • From: Bill Davidsen <davidsen@xxxxxxx>
• [Doubt] how is a disk marked faulty in RAID5
  • From: Anuj Goel <agoel@xxxxxxxxxxxxxxxxx>
• Re: Raid1: sdb has a lot mor work then sda
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Raid1: sdb has a lot mor work then sda
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Raid1: sdb has a lot mor work then sda
  • From: Daniel Spannbauer <ds@xxxxxxxx>
• Raid1: sdb has a lot mor work then sda
  • From: Daniel Spannbauer <ds@xxxxxxxx>
• Re: Disk link failure impact on Disks and RAID superblock in MD.
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• [PULL REQUEST] md: a couple of minor bug fixes, and one serious bug fixed.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 crashed, need comments on possible repair solution
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 crashed, need comments on possible repair solution
  • From: Christoph Nelles <evilazrael@xxxxxxxxxxxxx>
• Re: Raid5 crashed, need comments on possible repair solution
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/1] Make failure message on re-add more explcit
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Alex <creamyfish@xxxxxxxxx>
• Raid5 crashed, need comments on possible repair solution
  • From: Christoph Nelles <evilazrael@xxxxxxxxxxxxx>
• Re: md/bitmap: move some fields of 'struct bitmap' into a 'storage' substruct.
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: mdadm on an MvixBox running OpenWRT
  • From: "Hotmail \(John Fleuren\)" <john_fleuren@xxxxxxxxxxx>
• Re: dmesg deluge: RAID1 conf printout
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Re: mdadm -E won't examine loop back device, works ok on source disk
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm -E won't examine loop back device, works ok on source disk
  • From: Veedar Hokstadt <veedar@xxxxxxxxx>
• Re: Intel fakeraid working?
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Intel fakeraid working?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] fix: correct extending size of raid0 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md/bitmap: move some fields of 'struct bitmap' into a 'storage' substruct.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: fix: rebuild does not continue after reboot
  • From: NeilBrown <neilb@xxxxxxx>
• Re: dmesg deluge: RAID1 conf printout
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Removing a failing drive from multiple arrays
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Removing a failing drive from multiple arrays
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: mdadm -E won't examine loop back device, works ok on source disk
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm on an MvixBox running OpenWRT
  • From: NeilBrown <neilb@xxxxxxx>
• mdadm -E won't examine loop back device, works ok on source disk
  • From: Veedar Hokstadt <veedar@xxxxxxxxx>
• Re: Removing a failing drive from multiple arrays
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: dmesg deluge: RAID1 conf printout
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: dmesg deluge: RAID1 conf printout
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Alex <creamyfish@xxxxxxxxx>
• Re: dmesg deluge: RAID1 conf printout
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md raid recovery - perplexed
  • From: Ken Gunderson <kgunders@xxxxxxxxxxxx>
• Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
  • From: Paweł Brodacki <pawel.brodacki@xxxxxxxxxxxxxx>
• dmesg deluge: RAID1 conf printout
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: pglxra2.for.sabi.co.UK@xxxxxxxxxxxxxxx (Peter Grandi)
• md raid recovery - perplexed
  • From: Ken Gunderson <kgunders@xxxxxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Is this enough for us to have triple-parity RAID?
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Removing a failing drive from multiple arrays
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Removing a failing drive from multiple arrays
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Removing a failing drive from multiple arrays
  • From: Bill Davidsen <davidsen@xxxxxxx>
• re: md/bitmap: move some fields of 'struct bitmap' into a 'storage' substruct.
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] imsm: fix: rebuild does not continue after reboot
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
  • From: Paweł Brodacki <pawel.brodacki@xxxxxxxxxxxxxx>
• [PATCH] fix: correct extending size of raid0 array
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• RE: [PATCH 07/14] FIX: Extend size of raid0 array
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• about stripe cache in raid5.c
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Alex <creamyfish@xxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Alex <creamyfish@xxxxxxxxx>
• Re: Removing a failing drive from multiple arrays
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Should mdraid implement timeouts?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: migrating from metadata 0.9 to 1.0 before growing?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 07/14] FIX: Extend size of raid0 array
  • From: NeilBrown <neilb@xxxxxxx>
• Removing a failing drive from multiple arrays
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• RE: [PATCH 07/14] FIX: Extend size of raid0 array
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: migrating from metadata 0.9 to 1.0 before growing?
  • From: Lars Täuber <taeuber@xxxxxxx>
• Should mdraid implement timeouts?
  • From: Pierre Beck <mail@xxxxxxxxxxxxxx>
• Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [dm-devel] [PATCH 0 of 4] dm-raid: various bug fixes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: non fs-data and gpt partitioned md
  • From: NeilBrown <neilb@xxxxxxx>
• Re: non fs-data and gpt partitioned md
  • From: Ken Gunderson <kgunders@xxxxxxxxxxxx>
• Re: non fs-data and gpt partitioned md
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/4] lib/raid6: fix test program build
  • From: NeilBrown <neilb@xxxxxxx>
• Re: non fs-data and gpt partitioned md
  • From: Ken Gunderson <kgunders@xxxxxxxxxxxx>
• Re: arch/86: AVX RAID5 xor checksumming v1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [dm-devel] [PATCH 0 of 4] dm-raid: various bug fixes
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] raid5: add AVX optimized RAID5 checksumming
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• arch/86: AVX RAID5 xor checksumming v1
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Any 3.4-rc3 known issues?
  • From: Tom Rini <tom.rini@xxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Fixing broken metadata?
  • From: Tom Rini <tom.rini@xxxxxxxxx>
• Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
  • From: Paweł Brodacki <pawel.brodacki@xxxxxxxxxxxxxx>
• Fixing broken metadata?
  • From: Tom Rini <tom.rini@xxxxxxxxx>
• Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Alex <creamyfish@xxxxxxxxx>
• Re: [PATCH 0 of 4] dm-raid: various bug fixes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Disk link failure impact on Disks and RAID superblock in MD.
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Disk link failure impact on Disks and RAID superblock in MD.
  • From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
• Re: RAID 1 partition with hot spare shows [UUU] ?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: RAID 1 partition with hot spare shows [UUU] ?
  • From: John Crisp <john@xxxxxxxxxxxxxx>
• Re: mdadm: sending ioctl 800c0910 to a partition!
  • From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
• Re: RAID 1 partition with hot spare shows [UUU] ?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: [RFC 1/2] MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [RFC 1/2] MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 syncing at 24 MB/s?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC 1/2] MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: RAID6 syncing at 24 MB/s?
  • From: "George Spelvin" <linux@xxxxxxxxxxx>
• Re: RAID6 syncing at 24 MB/s?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC 1/2] MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 syncing at 24 MB/s?
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• RAID6 syncing at 24 MB/s?
  • From: "George Spelvin" <linux@xxxxxxxxxxx>
• Re: mdadm: sending ioctl 800c0910 to a partition!
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: [PATCH 0/1] Make failure message on re-add more explcit
  • From: NeilBrown <neilb@xxxxxxx>
• Re: software raid and ERC
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0 of 4] dm-raid: various bug fixes
  • From: NeilBrown <neilb@xxxxxxx>
• mdadm: sending ioctl 800c0910 to a partition!
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: [md PATCH 00/24] Allow bitmaps to be resized.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: software raid and ERC
  • From: "." <desire@xxxxxxxxx>
• [PATCH 5 of 5] MD RAID1: Further conditionalize 'fullsync'
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 4 of 5] DM RAID: Use md_error() in place of simply setting Faulty bit
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 3 of 5] DM RAID: Use safe version of rdev_for_each
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 2 of 5] DM RAID: Record and handle missing devices
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 1 of 5] DM RAID: Set recovery flags on resume
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 0 of 4] dm-raid: various bug fixes
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: software raid and ERC
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: [md PATCH 00/24] Allow bitmaps to be resized.
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: [PATCH 0 of 2] dm-raid: Bug fixes
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [RFC 1/2] MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: RAID 1 partition with hot spare shows [UUU] ?
  • From: NeilBrown <neilb@xxxxxxx>
• RAID 1 partition with hot spare shows [UUU] ?
  • From: John Crisp <john@xxxxxxxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• non fs-data and gpt partitioned md
  • From: Ken Gunderson <kgunders@xxxxxxxxxxxx>
• A RAID Story
  • From: Kristleifur Daðason <kristleifur@xxxxxxxxxxxxxxx>
• Re: [RFC 1/2] MD: raid5 trim support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: [RFC 1/2] MD: raid5 trim support
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: software raid and ERC
  • From: Emmanuel Noobadmin <centos.admin@xxxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: Stefan /*St0fF*/ Hübner <stefan.huebner@xxxxxxxxxxxxxxxxxx>
• Re: RAID5 XOR speed vs RAID6 Q speed (was Re: AVX RAID5 xor checksumming)
  • From: Boaz Harrosh <bharrosh@xxxxxxxxxxx>
• Re: [RFC 1/2] MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [RFC 1/2] MD: raid5 trim support
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: software raid and ERC
  • From: "." <desire@xxxxxxxxx>
• Re: [PATCH] md/raid10:using conf->chunk_mask instead "chunk_secotrs - 1"
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md/raid10:using conf->chunk_mask instead "chunk_secotrs - 1"
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• [md PATCH 17/24] md/bitmap: make bitmap bitops atomic.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 24/24] md/raid5: Allow reshape while a bitmap is present.
  • From: NeilBrown <neilb@xxxxxxx>
• [RFC 0/2] raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [RFC 1/2] MD: raid5 trim support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [RFC 2/2] MD: raid5 avoid unnecessary zero page for trim
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [md PATCH 18/24] md/bitmap: create a 'struct bitmap_counts' substructure of 'struct bitmap'
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 23/24] md/raid10: resize bitmap when required during reshape.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 22/24] md: allow array to be resized while bitmap is present.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 21/24] md/bitmap: make sure reshape request are reflected in superblock.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 20/24] md/bitmap: add bitmap_resize function to allow bitmap resizing.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 19/24] md/bitmap: use DIV_ROUND_UP instead of open-code
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 16/24] md/bitmap: make _page_attr bitops atomic.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 15/24] md/bitmap: merge bitmap_file_unmap and bitmap_file_put.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 14/24] md/bitmap: remove async freeing of bitmap file.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 13/24] md/bitmap: convert some spin_lock_irqsave to spin_lock_irq
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 12/24] md/bitmap: use set_bit, test_bit, etc for operation on bitmap->flags.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 11/24] md/bitmap: remove single-bit manipulation on sb->state
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 10/24] md/bitmap: remove bitmap_mask_state
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 09/24] md/bitmap: move storage allocation from bitmap_load to bitmap_create.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 08/24] md/bitmap: separate bitmap file allocation to its own function.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 07/24] md/bitmap: store bytes in file rather than just in last page.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 06/24] md/bitmap: move some fields of 'struct bitmap' into a 'storage' substruct.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 05/24] md/bitmap: change *_page_attr() to take a page number, not a page.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 04/24] md/bitmap: centralise allocation of bitmap file pages.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 03/24] md/bitmap: allow a bitmap with no backing storage.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 02/24] md/bitmap: add new 'space' attribute for bitmaps.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 01/24] md/bitmap: disentangle two different 'pending' flags.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 00/24] Allow bitmaps to be resized.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Is this enough for us to have triple-parity RAID?
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: [patch]raid5: support sync request
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch]raid5: support sync request
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch]raid5: remove unused variables
  • From: NeilBrown <neilb@xxxxxxx>
• Is this enough for us to have triple-parity RAID?
  • From: Alex <creamyfish@xxxxxxxxx>
• [patch]raid5: support sync request
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch]raid5: remove unused variables
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Re: [PATCH] md/raid1:Fix bug about fixing read errors.
  • From: "kedacomkernel" <kedacomkernel@xxxxxxxxx>
• Re: [PATCH 0 of 2] dm-raid: Bug fixes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md/raid10:Memleak fix if allocate rep1_bio failed in function want_replacement().
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] FIX: resolve make everything compilation error
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 00/14] imsm: volume expand
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 07/14] FIX: Extend size of raid0 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: display maximum volumes per controller and array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md/raid1:Fix bug about fixing read errors.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md:Fix mem leak about rdev->badblocks.page.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 2 of 2] dm-raid: record and handle missing devices
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 1 of 2] dm-raid: set recovery flags on resume
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• [PATCH 0 of 2] dm-raid: Bug fixes
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• RE: mdadm git build failure in super-intel.c
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• [PATCH] FIX: resolve make everything compilation error
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• [PATCH] md/raid10:Memleak fix if allocate rep1_bio failed in function want_replacement().
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Re: question about raid10 near copy info in man mdadm.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: question about raid10 near copy info in man mdadm.
  • From: "kedacomkernel" <kedacomkernel@xxxxxxxxx>
• Re: question about raid10 near copy info in man mdadm.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: question about raid10 near copy info in man mdadm.
  • From: "kedacomkernel" <kedacomkernel@xxxxxxxxx>
• Re: question about raid10 near copy info in man mdadm.
  • From: NeilBrown <neilb@xxxxxxx>
• [RFC]md: using GFP_NOIO to allocate bio for flush request
  • From: Shaohua Li <shli@xxxxxxxxxx>
• question about raid10 near copy info in man mdadm.
  • From: "kedacomkernel" <kedacomkernel@xxxxxxxxx>
• mdadm git build failure in super-intel.c
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: arch/86: AVX RAID5 xor checksumming
  • From: Ingo Molnar <mingo@xxxxxxxxxx>
• [PATCH 14/14] FIX: Assembled second array is in read only state during reshape
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 13/14] FIX: Size change is possible as standalone change only
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 12/14] imsm: FIX: Component size alignment check
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 11/14] imsm: Support setting max size for size change operation
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 10/14] imsm: Add function imsm_get_free_size()
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 08/14] FIX: Respect metadata size limitations
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 09/14] FIX: Detect error and rollback metadata
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 07/14] FIX: Extend size of raid0 array
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 06/14] imsm: FIX: Support metadata changes rollback
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 05/14] FIX: Support metadata changes rollback
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 04/14] imsm: Execute size change for external metatdata
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 03/14] imsm: Add new metadata update for volume size expansion
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 02/14] imsm: FIX: Add volume size expand support to imsm_analyze_change()
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 01/14] imsm: FIX: Update function imsm_num_data_members() for Raid1/10
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• [PATCH 00/14] imsm: volume expand
  • From: Adam Kwolek <adam.kwolek@xxxxxxxxx>
• Re: Problem assembling a degraded RAID5
  • From: Martin Wegner <mw@xxxxxxxxx>
• Re: lib/raid6: SSSE3 optimized recovery functions v2
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: lib/raid6: SSSE3 optimized recovery functions v2
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• [PATCH 1/4] lib/raid6: fix test program build
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• [PATCH 2/4] lib/raid6: Add SSSE3 optimized recovery functions
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• [PATCH 3/4] lib/raid6: update test program for recovery functions
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• [PATCH 4/4] lib/raid6: cleanup gen_syndrome function selection
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• Re: Bug#658701: mdadm: should send email if mismatches are reported by a check
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Problem assembling a degraded RAID5
  • From: Martin Wegner <mw@xxxxxxxxx>
• Re: lib/raid6: SSSE3 optimized recovery functions v2
  • From: NeilBrown <neilb@xxxxxxx>
• [PULL REQUEST] a few little fixes for md in 3.4
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH][Trivial] mdadm man page: fix typo
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: [PATCH][Trivial] mdadm man page: fix typo
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Failed Array Rebuild advice Please
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH][Trivial] mdadm man page: fix typo
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: Failed Array Rebuild advice Please
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• [PATCH 4/4] lib/raid6: cleanup gen_syndrome function selection
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• lib/raid6: SSSE3 optimized recovery functions v2
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• [PATCH 3/4] lib/raid6: update test program for recovery functions
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• [PATCH 2/4] lib/raid6: Add SSSE3 optimized recovery functions
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• [PATCH 1/4] lib/raid6: fix test program build
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• [PATCH] imsm: display maximum volumes per controller and array
  • From: "Labun, Marcin" <Marcin.Labun@xxxxxxxxx>
• [PATCH] md/raid1:Fix bug about fixing read errors.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• [PATCH] md:Fix mem leak about rdev->badblocks.page.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• question about:raid1 fix_read_error
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Re: Failed Array Rebuild advice Please
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Failed Array Rebuild advice Please
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: mdadm 3.2.3 and adding metadata 1.0 bitmaps
  • From: Joe Lawrence <jdl1291@xxxxxxxxx>
• [PATCH] md/raid1:If raid1 only had one disk and readed error,should call rdev_set_badblocks().
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Re: Failed Array Rebuild advice Please
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: [PATCH 0/1] Make failure message on re-add more explcit
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Failed Array Rebuild advice Please
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm 3.2.3 and adding metadata 1.0 bitmaps
  • From: NeilBrown <neilb@xxxxxxx>
• Failed Array Rebuild advice Please
  • From: jahammonds prost <gmitch64@xxxxxxxxx>
• Re: arch/86: AVX RAID5 xor checksumming
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: arch/86: AVX RAID5 xor checksumming
  • From: NeilBrown <neilb@xxxxxxx>
• Correct stride and stripe-width
  • From: Salatiel Filho <salatiel.filho@xxxxxxxxx>
• Re: arch/86: AVX RAID5 xor checksumming
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• mdadm 3.2.3 and adding metadata 1.0 bitmaps
  • From: Joe Lawrence <jdl1291@xxxxxxxxx>
• Re: Intel fakeraid working?
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [PATCH] md/raid1,raid10:If r1bio->sectors % 8 != 0,then the memcmp and latermemcpy will omit the last bio_vec.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] MD: Bitmap version cleanup.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: about:conf->recovery_disabled and mddev->recovery_disabled
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Re: Re: [PATCH] md/raid1:combine code in fix_read_error andfix_sync_read_error.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Re: resync after a power failure
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] mdadm: do not read the 'clean' flag from potentially non-up-to-date drive
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md/raid1:combine code in fix_read_error and fix_sync_read_error.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Intel fakeraid working?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/1] Make failure message on re-add more explcit
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/4] Imsm OROM compatibility/boot support fixes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Fix two typos in fprintf messages
  • From: NeilBrown <neilb@xxxxxxx>
• resync after a power failure
  • From: Salatiel Filho <salatiel.filho@xxxxxxxxx>
• Re: [PATCH] mdadm: do not read the 'clean' flag from potentially non-up-to-date drive
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: about:conf->recovery_disabled and mddev->recovery_disabled
  • From: NeilBrown <neilb@xxxxxxx>
• Re: doubt in chunk_aligned_read()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: doubt in chunk_aligned_read()
  • From: Anuj Goel <talk2anuj@xxxxxxxxx>
• about:conf->recovery_disabled and mddev->recovery_disabled
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Re: Can't add drive to array 3.3 & 3.2.3
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: RAID5 XOR speed vs RAID6 Q speed (was Re: AVX RAID5 xor checksumming)
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH] mdadm: do not read the 'clean' flag from potentially non-up-to-date drive
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Intel fakeraid working?
  • From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
• Re: Can't add drive to array 3.3 & 3.2.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Can't add drive to array 3.3 & 3.2.3
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: Raid 6 rebuild
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PATCH] md/raid1:combine code in fix_read_error and fix_sync_read_error.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Raid 6 rebuild
  • From: Bryan Bush <bbushvt@xxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Can't add drive to array 3.3 & 3.2.3
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Can't add drive to array 3.3 & 3.2.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: Intel fakeraid working?
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: Intel fakeraid working?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Intel fakeraid working?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/1] Make failure message on re-add more explcit
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Intel fakeraid working?
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Intel fakeraid working?
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: [PATCH 1/4] imsm: monitor: do not finish migration if there are no failed disks
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 3/4] imsm: avoid double change of serial number of missing device
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 4/4] imsm: monitor: do not finish recovery, when raid goes to read-only
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 2/4] imsm: clean up missing disks if there are any left after migration
  • From: "Williams, Dan J" <dan.j.williams@xxxxxxxxx>
• [PATCH 4/4] imsm: monitor: do not finish recovery, when raid goes to read-only
  • From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• [PATCH 3/4] imsm: avoid double change of serial number of missing device
  • From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• [PATCH 2/4] imsm: clean up missing disks if there are any left after migration
  • From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• [PATCH 1/4] imsm: monitor: do not finish migration if there are no failed disks
  • From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• [PATCH 0/4] Imsm OROM compatibility/boot support fixes
  • From: Przemyslaw Czarnowski <przemyslaw.hawrylewicz.czarnowski@xxxxxxxxx>
• [PATCH] Fix two typos in fprintf messages
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: md/raid1:If r1bio->sectors % 8 != 0,then the memcmp and latermemcpy will omit the last bio_vec.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md/raid1,raid10:If r1bio->sectors % 8 != 0,then the memcmp and latermemcpy will omit the last bio_vec.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Re: Re: md/raid1:If r1bio->sectors % 8 != 0,then the memcmp and latermemcpy will omit the last bio_vec.
  • From: "kedacomkernel" <kedacomkernel@xxxxxxxxx>
• Re: md/raid1:Fix a logic bug in fix_sync_read_error().
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: md/raid1:Fix a logic bug in fix_sync_read_error().
  • From: "kedacomkernel" <kedacomkernel@xxxxxxxxx>
• Re: doubt in chunk_aligned_read()
  • From: Anuj Goel <talk2anuj@xxxxxxxxx>
• Re: doubt in chunk_aligned_read()
  • From: NeilBrown <neilb@xxxxxxx>
• doubt in chunk_aligned_read()
  • From: Anuj Goel <talk2anuj@xxxxxxxxx>
• Re: Intel fakeraid working?
  • From: NeilBrown <neilb@xxxxxxx>
• Intel fakeraid working?
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: RAID5 check does not read disk media
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID-10 explicitly defined drive pairs?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: RAID5 check does not read disk media
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• RAID5 check does not read disk media
  • From: Peter Urbanec <linux-raid@xxxxxxxxxxx>
• Re: Help to assemble raid5 - no superblock!
  • From: NeilBrown <neilb@xxxxxxx>
• Help to assemble raid5 - no superblock!
  • From: Salatiel Filho <salatiel.filho@xxxxxxxxx>
• Re: [PATCH] userns: Replace netlink uses of cap_raised with capable.
  • From: "Andrew G. Morgan" <morgan@xxxxxxxxxx>
• Re: [PATCH] userns: Replace netlink uses of cap_raised with capable.
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH] userns: Replace netlink uses of cap_raised with capable.
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• Re: [PATCH] userns: Replace netlink uses of cap_raised with capable.
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• [PATCH] userns: Replace netlink uses of cap_raised with capable.
  • From: ebiederm@xxxxxxxxxxxx (Eric W. Biederman)
• [PATCH 1/2] crypto: wait for a full jiffy in do_xor_speed
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• [PATCH 2/2] crypto: disable preemption while benchmarking RAID5 xor checksumming
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• Re: RAID5 XOR speed vs RAID6 Q speed (was Re: AVX RAID5 xor checksumming)
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• Re: RAID5 XOR speed vs RAID6 Q speed (was Re: AVX RAID5 xor checksumming)
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• [md PATCH 10/10] md/raid10: add reshape support
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 09/10] md/raid10: split out interpretation of layout to separate function.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 08/10] md/raid10: Introduce 'prev' geometry to support reshape.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 07/10] md: use resync_max_sectors for reshape as well as resync.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 06/10] md: teach sync_page_io about new_data_offset.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 05/10] md/raid10: collect some geometry fields into a dedicated structure.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 04/10] md/raid5: allow for change in data_offset while managing a reshape.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 03/10] md/raid5: Use correct data_offset for all IO.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 02/10] md: add possibility to change data-offset for devices.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 01/10] md: allow a reshape operation to be reversed.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 00/10] md patches for 3.5: RAID10 reshape
  • From: NeilBrown <neilb@xxxxxxx>
• [PULL REQUEST] md bugfixes for 3.4-rc
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID5 XOR speed vs RAID6 Q speed (was Re: AVX RAID5 xor checksumming)
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• Re: Linux 3.3.1 resync speed
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Linux 3.3.1 resync speed
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• Re: Linux 3.3.1 resync speed
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Linux 3.3.1 resync speed
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• [PATCH] imsm: fix: thunderdome may drop 2tb attribute
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• RE: [PATCH 1/6] imsm: avoid overflows for disks over 1TB
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: David Brown <david@xxxxxxxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID6 grow failed
  • From: Bryan Bush <bbushvt@xxxxxxxxx>
• Re: RAID6 grow failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md/raid1:using else-if instead if.
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: md/raid1:Fix a logic bug in fix_sync_read_error().
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md/raid1:Using 1 instead of update.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md/raid1:using else-if instead if.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md/raid1:If r1bio->sectors % 8 != 0,then the memcmp and later memcpy will omit the last bio_vec.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md/raid1:Remove unnecessary judgement.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: When allocating resync pages,judge the queue limit of mddev.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md/raid5:Fix a bug about judging the operation is syncing or replaing in analyse_stripe().
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md/raid1:remove unnecessary set_bit(MD_RECOVERY_INTR,&mddev->recovery).
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md:Add the judgement about the size of suspend_lo and suspend_hi.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md/raid1:Remove unnecessary rcu_dereference(conf->mirrors[i].rdev). Because rde->nr_pending > 0,so can not remove this disk.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md/raid1:!conf->r1buf_pool is unlikely in function sync_request.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 grow failed
  • From: Bryan Bush <bbushvt@xxxxxxxxx>
• Re: RAID6 grow failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/6] imsm: 2TB disks/volumes support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/6] imsm: avoid overflows for disks over 1TB
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md/raid1:using else-if instead if.
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: RAID6 grow failed
  • From: Bryan Bush <bbushvt@xxxxxxxxx>
• Re: RAID5 XOR speed vs RAID6 Q speed (was Re: AVX RAID5 xor checksumming)
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: RAID6 grow failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Marcus Sorensen <shadowsor@xxxxxxxxx>
• Re: RAID6 grow failed
  • From: Bryan Bush <bbushvt@xxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PATCH] md/raid1:Using 1 instead of update.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• [PATCH] md/raid1:using else-if instead if.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: RAID6 grow failed
  • From: Bryan Bush <bbushvt@xxxxxxxxx>
• Re: RAID6 grow failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID6 grow failed
  • From: Bryan Bush <bbushvt@xxxxxxxxx>
• RAID5 XOR speed vs RAID6 Q speed (was Re: AVX RAID5 xor checksumming)
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• [PATCH] md/raid1:use bi->bv_len instead of PAGE_SIZE.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Re: RAID5 created by 8 disks works with xfs
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• md/raid1:If r1bio->sectors % 8 != 0,then the memcmp and later memcpy will omit the last bio_vec.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• md/raid1:Fix a logic bug in fix_sync_read_error().
  • From: "kedacomkernel" <kedacomkernel@xxxxxxxxx>
• md/raid1:Remove unnecessary judgement.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• RAID5 created by 8 disks works with xfs
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: mdadm raid6 recovery status
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] imsm: set 2tb disk attribute for spare
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• RE: mdadm raid6 recovery status
  • From: "Paramasivam, Meenakshisundaram" <mparamas@xxxxxxxxx>
• When allocating resync pages,judge the queue limit of mddev.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• [PATCH] raid5: add AVX optimized RAID5 checksumming
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• AVX RAID5 xor checksumming
  • From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
• Re: mdadm raid6 recovery status
  • From: NeilBrown <neilb@xxxxxxx>
• RE: mdadm raid6 recovery status
  • From: "Paramasivam, Meenakshisundaram" <mparamas@xxxxxxxxx>
• RE: mdadm raid6 recovery status
  • From: "Paramasivam, Meenakshisundaram" <mparamas@xxxxxxxxx>
• [PATCH 6/6] check that no disk over 2TB is used to create container when no support
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• [PATCH 5/6] check volume size in validate_geometry_imsm_orom
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• [PATCH 2/6] clear hi bits if not used after loading metadata from disk
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• [PATCH 4/6] show 2TB volumes/disks support in --detail-platform
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• [PATCH 3/6] simplify calculating array_blocks
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• [PATCH 1/6] imsm: avoid overflows for disks over 1TB
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• [PATCH 0/6] imsm: 2TB disks/volumes support
  • From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
• md/raid5:Fix a bug about judging the operation is syncing or replaing in analyse_stripe().
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Re: [PULL REQUEST] two md updates for 3.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm raid6 recovery status
  • From: NeilBrown <neilb@xxxxxxx>
• Check not actually reading drives
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• Re: Hints on reducing kickouts
  • From: John Obaterspok <john.obaterspok@xxxxxxxxx>
• Re: mdadm raid6 recovery status
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: re-adding a disk to a raid1 array with bitmap
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PULL REQUEST] two md updates for 3.3
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• RE: mdadm raid6 recovery status
  • From: "Paramasivam, Meenakshisundaram" <mparamas@xxxxxxxxx>
• md/raid1:remove unnecessary set_bit(MD_RECOVERY_INTR,&mddev->recovery).
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• md:Add the judgement about the size of suspend_lo and suspend_hi.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• md/raid1:Remove unnecessary rcu_dereference(conf->mirrors[i].rdev). Because rde->nr_pending > 0,so can not remove this disk.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• md/raid1:!conf->r1buf_pool is unlikely in function sync_request.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Re: RAID6 grow failed
  • From: Bryan Bush <bbushvt@xxxxxxxxx>
• Re: RAID6 grow failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: SSD cache for software RAID
  • From: daobang wang <wangdb1981@xxxxxxxxx>
• Re: RAID6 grow failed
  • From: Bryan Bush <bbushvt@xxxxxxxxx>
• Re: RAID6 grow failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm raid6 recovery status
  • From: NeilBrown <neilb@xxxxxxx>
• Re: SSD cache for software RAID
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• SSD cache for software RAID
  • From: 王道邦 <wangdb1981@xxxxxxxxx>
• Re: RAID6 grow failed
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• RAID6 grow failed
  • From: Bryan Bush <bbushvt@xxxxxxxxx>
• Re: Re: md/raid5:Fix recover/replace stop if handle stipe failed
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• mdadm raid6 recovery status
  • From: "Paramasivam, Meenakshisundaram" <mparamas@xxxxxxxxx>
• Re: md/raid5:Fix recover/replace stop if handle stipe failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Re: md/raid5:Fix recover/replace stop if handle stipe failed
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Re: md/raid5:Fix recover/replace stop if handle stipe failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: re-adding a disk to a raid1 array with bitmap
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Invalidating the pages read from a disk which md marks as faulty later
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Re: md/raid5:Fix recover/replace stop if handle stipe failed
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Re: [PATCH v2] Avoid OOPS when reshaping raid1 to raid0
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH v2] Avoid OOPS when reshaping raid1 to raid0
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md/raid5:Fix recover/replace stop if handle stipe failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md/raid1: If md_integrity_register() failed,run() must free the mem
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md/raid0: If md_integrity_register() failed,raid0_run() must free the mem.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md/linear: If md_integrity_register() failed,linear_run() must free the mem.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH v2] Avoid OOPS when reshaping raid1 to raid0
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: [PATCH 1/1] Avoid OOPS when reshaping raid1 to raid0
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 1/1] Avoid OOPS when reshaping raid1 to raid0
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 018 of 29] md: Support changing rdev size on running arrays.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Rescue md/6 array: advice please
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: RAID-10 explicitly defined drive pairs?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Rescue md/6 array: advice please
  • From: Ruth Ivimey-Cook <ruth@xxxxxxxxxx>
• Re: [PATCH 018 of 29] md: Support changing rdev size on running arrays.
  • From: Markus Hochholdinger <Markus@xxxxxxxxxxxxxxxxx>
• restoring array after zeroing superblocks
  • From: Alexander Peganz <a.peganz@xxxxxxxxx>
• Re: raid10n2/xfs setup guidance on write-cache/barrier
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• md/raid1: If md_integrity_register() failed,run() must free the mem
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• md/raid0: If md_integrity_register() failed,raid0_run() must free the mem.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• md/linear: If md_integrity_register() failed,linear_run() must free the mem.
  • From: "majianpeng" <majianpeng@xxxxxxxxx>
• Re: raid10n2/xfs setup guidance on write-cache/barrier
  • From: pg@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Kernel oops adding bitmap
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Fwd: grub-probe seems to be having problems
  • From: jlcenter@xxxxxxxxxxx
• Re: [PATCH 1/1] Avoid OOPS when reshaping raid1 to raid0
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• [PATCH 0/1] Avoid OOPS when reshaping raid1 to raid0
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 1/1] Avoid OOPS when reshaping raid1 to raid0
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: RAID-10 explicitly defined drive pairs?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID-10 explicitly defined drive pairs?
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [patch v2 2/6] blk: dont allow discard request merge temporarily
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: grub-probe seems to be having problems
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch v2 2/6] blk: dont allow discard request merge temporarily
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Fwd: grub-probe seems to be having problems
  • From: jlcenter@xxxxxxxxxxx
• Re: [patch v2 2/6] blk: dont allow discard request merge temporarily
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Kernel oops adding bitmap
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Kernel oops adding bitmap
  • From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
• Re: Kernel oops adding bitmap
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: [PATCH 00/11] Various cleanups and minor fixes
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [patch v2 0/6] Add TRIM support for raid linear/0/1/10
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: [patch v2 0/6] Add TRIM support for raid linear/0/1/10
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: [patch v2 0/6] Add TRIM support for raid linear/0/1/10
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: [patch v2 0/6] Add TRIM support for raid linear/0/1/10
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch v2 2/6] blk: dont allow discard request merge temporarily
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 00/11] Various cleanups and minor fixes
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 07/11] match_metadata_desc0(): Use calloc instead of malloc+memset
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 05/11] Use 4K buffer alignment for superblock allocations
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 10/11] super-intel.c: Use ROUND_UP() instead of manually coding it
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 11/11] __write_init_super_ddf(): Use posix_memalign() instead of static aligned buffer
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 08/11] Generalize ROUND_UP() macro and introduce matching ROUND_UP_PTR()
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 09/11] super1.c: use ROUND_UP/ROUND_UP_PTR
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 06/11] Use struct align_fd to cache fd's block size for aligned reads/writes
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 03/11] init_super1() memset full buffer allocated for superblock
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 02/11] Define and use SUPER1_SIZE for allocations
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 04/11] match_metadata_desc1(): Use calloc instead of malloc+memset
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 01/11] super1.c don't keep recalculating bitmap pointer
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 00/11] Various cleanups and minor fixes
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: [patch v2 2/6] blk: dont allow discard request merge temporarily
  • From: Vivek Goyal <vgoyal@xxxxxxxxxx>
• Re: raid10n2/xfs setup guidance on write-cache/barrier
  • From: Jessie Evangelista <jessie.evangelista@xxxxxxxxx>
• Re: [patch v2 0/6] Add TRIM support for raid linear/0/1/10
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch v2 0/6] Add TRIM support for raid linear/0/1/10
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>