Linux RAID Storage Date Index

• Thread Index

• Re: Posting on RISKS - hacked NAS's
  • From: Benjammin2068 <benjammin2068@xxxxxxxxx>
• Re: Linux raid wiki - setting up a system - advice wanted :-)
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Linux raid wiki - setting up a system - advice wanted :-)
  • From: Francisco Parada <advanceandconquer@xxxxxxxxx>
• Re: Posting on RISKS - hacked NAS's
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Posting on RISKS - hacked NAS's
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Linux raid wiki - setting up a system - advice wanted :-)
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/5] r5cache: write part of r5cache
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 1/5] r5cache: write part of r5cache
  • From: Zhengyuan Liu <liuzhengyuang521@xxxxxxxxx>
• Re: Linux raid wiki
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Linux raid wiki - force assembling an array where one drive has a different event count - advice needed
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Linux raid wiki
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Linux raid wiki - force assembling an array where one drive has a different event count - advice needed
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Linux raid wiki - force assembling an array where one drive has a different event count - advice needed
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• RE: Linux raid wiki
  • From: "Peter Sangas" <pete@xxxxxxxxxx>
• Re: Linux raid wiki
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• RE: Linux raid wiki
  • From: "WNSDEV" <pete@xxxxxxxxxx>
• Re: RAID5 grow interrupted.
  • From: Axel Spallek <axel@xxxxxxxxxxx>
• [PATCH] raid6/test/test.c: bug fix: Specify aligned(alignment) attributes to the char arrays
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• RE: [PATCH v2] raid6/test/test.c: bug fix: Specify aligned(alignment) attributes to the char arrays
  • From: "Kammela, Gayatri" <gayatri.kammela@xxxxxxxxx>
• [PATCH v2] raid6/test/test.c: bug fix: Specify aligned(alignment) attributes to the char arrays
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• Linux raid wiki
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: RAID5 grow interrupted.
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: RAID5 grow interrupted.
  • From: Axel Spallek <axel@xxxxxxxxxxx>
• Re: RAID5 grow interrupted.
  • From: Axel Spallek <axel@xxxxxxxxxxx>
• Re: RAID5 grow interrupted.
  • From: Axel Spallek <axel@xxxxxxxxxxx>
• Re: RAID5 grow interrupted.
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: 95a05b3 broke mdadm --add on my superblock 1.0 array
  • From: Anthony DeRobertis <anthony@xxxxxxxxxxxx>
• Re: [PATCH v2] Fix RAID metadata check
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: RAID5 grow interrupted.
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• RAID5 grow interrupted.
  • From: Axel Spallek <axel@xxxxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• [PATCH v2] Fix RAID metadata check
  • From: Mariusz Dabrowski <mariusz.dabrowski@xxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Simon Becks <beckssimon5@xxxxxxxxx>
• Re: 95a05b3 broke mdadm --add on my superblock 1.0 array
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Simon Becks <beckssimon5@xxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Simon Becks <beckssimon5@xxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Simon Becks <beckssimon5@xxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Simon Becks <beckssimon5@xxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Simon Becks <beckssimon5@xxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Simon Becks <beckssimon5@xxxxxxxxx>
• Re: [PATCH] raid5: fix to detect failure of register_shrinker
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: [PATCH][RESEND] Fix RAID metadata check
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Benjamin ESTRABAUD <ben.estrabaud@xxxxxxxxxx>
• restore 3disk raid5 after raidpartitions have been setup with xfs filesystem by accident
  • From: Simon Becks <beckssimon5@xxxxxxxxx>
• [PATCH][RESEND] Fix RAID metadata check
  • From: Mariusz Dabrowski <mariusz.dabrowski@xxxxxxxxx>
• Re: 95a05b3 broke mdadm --add on my superblock 1.0 array
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: 95a05b3 broke mdadm --add on my superblock 1.0 array
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: Enlarging device of linear array again (Thank you Stan!)
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Enlarging device of linear array again (Thank you Stan!)
  • From: Ramon Hofer <ramonhofer@xxxxxxxxxx>
• Re: Enlarging device of linear array again (Thank you Stan!)
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Enlarging device of linear array again (Thank you Stan!)
  • From: Ramon Hofer <ramonhofer@xxxxxxxxxx>
• Re: 95a05b3 broke mdadm --add on my superblock 1.0 array
  • From: Anthony DeRobertis <anthony@xxxxxxxxxxxx>
• Re: [PATCH] mdadm: replace hard coded string length
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: 95a05b3 broke mdadm --add on my superblock 1.0 array
  • From: Anthony DeRobertis <anthony@xxxxxxxxxxxx>
• RAID1 Questions. Please help
  • From: "WNSDEV" <pete@xxxxxxxxxx>
• Re: 95a05b3 broke mdadm --add on my superblock 1.0 array
  • From: Anthony DeRobertis <anthony@xxxxxxxxxxxx>
• Re: 95a05b3 broke mdadm --add on my superblock 1.0 array
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: 95a05b3 broke mdadm --add on my superblock 1.0 array
  • From: Anthony DeRobertis <anthony@xxxxxxxxxxxx>
• Re: 95a05b3 broke mdadm --add on my superblock 1.0 array
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH] raid5: fix to detect failure of register_shrinker
  • From: Chao Yu <yuchao0@xxxxxxxxxx>
• 95a05b3 broke mdadm --add on my superblock 1.0 array
  • From: Anthony DeRobertis <anthony@xxxxxxxxxxxx>
• Re: Best tool to partition Drives with new sector geometry - (WAS: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive))
  • From: Benjammin2068 <benjammin2068@xxxxxxxxx>
• Re: Best tool to partition Drives with new sector geometry - (WAS: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive))
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Best tool to partition Drives with new sector geometry - (WAS: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive))
  • From: Benjammin2068 <benjammin2068@xxxxxxxxx>
• Re: Best tool to partition Drives with new sector geometry - (WAS: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive))
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Best tool to partition Drives with new sector geometry - (WAS: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive))
  • From: Benjammin2068 <benjammin2068@xxxxxxxxx>
• Re: Best tool to partition Drives with new sector geometry - (WAS: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive))
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Best tool to partition Drives with new sector geometry - (WAS: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive))
  • From: Benjammin2068 <benjammin2068@xxxxxxxxx>
• Re: Best tool to partition Drives with new sector geometry - (WAS: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive))
  • From: Benjammin2068 <benjammin2068@xxxxxxxxx>
• Re: Best tool to partition Drives with new sector geometry - (WAS: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive))
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Best tool to partition Drives with new sector geometry - (WAS: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive))
  • From: Benjammin2068 <benjammin2068@xxxxxxxxx>
• Re: Question about commit f9a67b1182e5 ("md/bitmap: clear bitmap if bitmap_create failed").
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: lots of "md: export_rdev(sde)" printed after create IMSM RAID10 with missing
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• Re: [PATCH v2] mdadm: replace hard coded string length
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH -next] dm cache policy smq: remove duplicated include from dm-cache-policy-smq.c
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH -next] dm cache policy smq: remove duplicated include from dm-cache-policy-smq.c
  • From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
• [PATCH v2] mdadm: replace hard coded string length
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH] imsm: remove redundant characters from some error messages
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• [PATCH] imsm: remove redundant characters from some error messages
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: [PATCH] mdadm: replace hard coded string length
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH] mdadm: replace hard coded string length
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: lots of "md: export_rdev(sde)" printed after create IMSM RAID10 with missing
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH] mdadm: replace hard coded string length
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mdadm: replace hard coded string length
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: [PATCH] imsm: do not activate spares for uninitialized member arrays
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH] mdadm: replace hard coded string length
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Inactive arrays
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: lots of "md: export_rdev(sde)" printed after create IMSM RAID10 with missing
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH] imsm: do not activate spares for uninitialized member arrays
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: moving spares into group and checking spares
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: moving spares into group and checking spares
  • From: scar <scar@xxxxxxxxxx>
• [PATCH] mdadm: replace hard coded string length
  • From: Song Liu <songliubraving@xxxxxx>
• Re: moving spares into group and checking spares
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: moving spares into group and checking spares
  • From: scar <scar@xxxxxxxxxx>
• Re: moving spares into group and checking spares
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• [PATCH] md: fix a potential deadlock
  • From: Shaohua Li <shli@xxxxxx>
• Re: lots of "md: export_rdev(sde)" printed after create IMSM RAID10 with missing
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: moving spares into group and checking spares
  • From: scar <scar@xxxxxxxxxx>
• Re: Question about commit f9a67b1182e5 ("md/bitmap: clear bitmap if bitmap_create failed").
  • From: Marion & Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Re: Inactive arrays
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: moving spares into group and checking spares
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: moving spares into group and checking spares
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: moving spares into group and checking spares
  • From: scar <scar@xxxxxxxxxx>
• Re: Inactive arrays
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: Inactive arrays
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: Inactive arrays
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: moving spares into group and checking spares
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: lots of "md: export_rdev(sde)" printed after create IMSM RAID10 with missing
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• [PATCH] Fix RAID metadata check
  • From: Mariusz Dabrowski <mariusz.dabrowski@xxxxxxxxx>
• Re: Question about commit f9a67b1182e5 ("md/bitmap: clear bitmap if bitmap_create failed").
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• moving spares into group and checking spares
  • From: scar <scar@xxxxxxxxxx>
• Re: Inactive arrays
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: Inactive arrays
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: Inactive arrays
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: Inactive arrays
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: RAID6 - CPU At 100% Usage After Reassembly
  • From: Francisco Parada <advanceandconquer@xxxxxxxxx>
• Re: RAID6 - CPU At 100% Usage After Reassembly
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Question about commit f9a67b1182e5 ("md/bitmap: clear bitmap if bitmap_create failed").
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [GIT PULL] MD update for 4.8-rc6
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: RAID6 - CPU At 100% Usage After Reassembly
  • From: Francisco Parada <advanceandconquer@xxxxxxxxx>
• Re: Inactive arrays
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: Inactive arrays
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Question about commit f9a67b1182e5 ("md/bitmap: clear bitmap if bitmap_create failed").
  • From: Christophe JAILLET <christophe.jaillet@xxxxxxxxxx>
• Re: [PATCH v3] mdadm: fix a buffer overflow
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: dm: Return correct value in retry loop
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: lots of "md: export_rdev(sde)" printed after create IMSM RAID10 with missing
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: lots of "md: export_rdev(sde)" printed after create IMSM RAID10 with missing
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• Re: [PATCH] dm: Return correct value in retry loop
  • From: Minfei Huang <mnghuan@xxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: lots of "md: export_rdev(sde)" printed after create IMSM RAID10 with missing
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: lots of "md: export_rdev(sde)" printed after create IMSM RAID10 with missing
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH v3] mdadm: fix a buffer overflow
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH v2] mdadm: fix a buffer overflow
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH V3] md-cluster: make md-cluster also can work when compiled into kernel
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH v2] mdadm: fix a buffer overflow
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH] raid5: allow arbitrary max_hw_sectors
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH v2] mdadm: fix a buffer overflow
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH] mdadm: fix a buffer overflow
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH] mdadm: fix a buffer overflow
  • From: Song Liu <songliubraving@xxxxxx>
• lots of "md: export_rdev(sde)" printed after create IMSM RAID10 with missing
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• Re: a hard lockup in md raid5 sequential write (v4.7-rc7)
  • From: Coly Li <colyli@xxxxxxx>
• [PATCH] dm: Return correct value in retry loop
  • From: Minfei Huang <mnghuan@xxxxxxxxx>
• RE: Checkarray doesn't seem to do anything
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [PATCH V3] md-cluster: make md-cluster also can work when compiled into kernel
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH V3] md-cluster: make md-cluster also can work when compiled into kernel
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH V2] md-cluster: make md-cluster also can work when compiled into kernel
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH V2] md-cluster: make md-cluster also can work when compiled into kernel
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH V2] md-cluster: make md-cluster also can work when compiled into kernel
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: RAID6 - CPU At 100% Usage After Reassembly
  • From: Francisco Parada <advanceandconquer@xxxxxxxxx>
• Re: RAID6 - CPU At 100% Usage After Reassembly
  • From: "Michael J. Shaver" <jmshaver@xxxxxxxxx>
• Raid failure- Please help - Linux-Raid noob
  • From: Norman <norman.quisumbing@xxxxxxxxxxxxx>
• RAID6 - CPU At 100% Usage After Reassembly
  • From: Francisco Parada <advanceandconquer@xxxxxxxxx>
• RAID6 - CPU At 100% Usage After Reassembly
  • From: Francisco Parada <advanceandconquer@xxxxxxxxx>
• [PATCH V2] md-cluster: make md-cluster also can work when compiled into kernel
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH] md-cluster: make md-cluster also can work when compiled into kernel
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH] md-cluster: make md-cluster also can work when compiled into kernel
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: travis+ml-linux-raid@xxxxxxxxxxxxxxxxx
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: md-cluster Module Requirement
  • From: Marc Smith <marc.smith@xxxxxxx>
• Re: md-cluster Module Requirement
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: md-cluster Module Requirement
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: md-cluster Module Requirement
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: md-cluster Module Requirement
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 4/5] r5cache: r5c recovery
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 0/5] raid5-cache: enabling cache features
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 5/5] r5cache: handle SYNC and FUA
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 2/5] r5cache: sysfs entry r5c_state
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 1/5] r5cache: write part of r5cache
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 3/5] r5cache: naive reclaim approach
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH] dm-bufio: Remove deprecated create_singlethread_workqueue
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [PATCH] raid5: guarantee enough stripes to avoid reshape hang
  • From: NeilBrown <neilb@xxxxxxxx>
• [GIT PULL] MD update for 4.8-rc4
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH] raid5: guarantee enough stripes to avoid reshape hang
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH] dm-bufio: Remove deprecated create_singlethread_workqueue
  • From: Bhaktipriya Shridhar <bhaktipriya96@xxxxxxxxx>
• [PATCH v3] raid6: fix the input of raid6 algorithm
  • From: liuzhengyuan@xxxxxxxxxx
• Re: Raid settings
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid settings
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Raid settings
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid settings
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid settings
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid settings
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Raid settings
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Raid settings
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Raid settings
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Benjammin2068 <benjammin2068@xxxxxxxxx>
• Re: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Benjammin2068 <benjammin2068@xxxxxxxxx>
• Re: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Raid settings
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Raid settings
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: [PATCH v2] raid6: fix the input of raid6 algorithm
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• Re: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Benjammin2068 <benjammin2068@xxxxxxxxx>
• [PATCH v2] raid6: fix the input of raid6 algorithm
  • From: liuzhengyuan@xxxxxxxxxx
• Re: kernel checksumming performance vs actual raid device performance
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• md-cluster Module Requirement
  • From: Marc Smith <marc.smith@xxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: travis+ml-linux-raid@xxxxxxxxxxxxxxxxx
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: travis@xxxxxxxxxxxxxxxxx
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: travis+ml-linux-raid@xxxxxxxxxxxxxxxxx
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: travis@xxxxxxxxxxxxxxxxx
• Re: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Benjammin2068 <benjammin2068@xxxxxxxxx>
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Ben <benjammin2068@xxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH v2] mdopen: Prevent overrunning the devname buffer when copying devnm into it for long md names.
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 1/3] MD: hold mddev lock for .quiesce in md_do_sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: [dm-devel] [PATCH v2] mdopen: Prevent overrunning the devname buffer when copying devnm into it for long md names.
  • From: Shaun Tancheff <shaun.tancheff@xxxxxxxxxxx>
• Re: [dm-devel] [PATCH v2] mdopen: Prevent overrunning the devname buffer when copying devnm into it for long md names.
  • From: Shaun Tancheff <shaun.tancheff@xxxxxxxxxxx>
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: travis+ml-linux-raid@xxxxxxxxxxxxxxxxx
• Re: [PATCH 1/3] MD: hold mddev lock for .quiesce in md_do_sync
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• [PATCH v2] mdopen: Prevent overrunning the devname buffer when copying devnm into it for long md names.
  • From: Robert LeBlanc <robert@xxxxxxxxxxxxx>
• Re: [PATCH] raid6: fix the input of raid6 algorithm
  • From: "liuzhengyuan" <liuzhengyuan@xxxxxxxxxx>
• Re: [PATCH 1/3] MD: hold mddev lock for .quiesce in md_do_sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 1/3] MD: hold mddev lock for .quiesce in md_do_sync
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: bootsect replicated in p1, RAID enclosure suggestions?
  • From: travis+ml-linux-raid@xxxxxxxxxxxxxxxxx
• Re: kernel checksumming performance vs actual raid device performance
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH v2] raid10: record correct address of bad block
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH -next] md-cluster: fix error return code in join()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH] mdopen: Prevent overrunning the devname buffer when copying devnm into it for long md names.
  • From: Robert LeBlanc <robert@xxxxxxxxxxxxx>
• Re: [RFC] Some fixes to allow for more than 128 md devices.
  • From: Robert LeBlanc <robert@xxxxxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Ben <benjammin2068@xxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] raid5: fix memory leak of bio integrity data
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• [PATCH v2] raid10: record correct address of bad block
  • From: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx>
• Re: [PATCH 2/2] r5cache: remove journal support
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 2/2] r5cache: remove journal support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 1/2] r5cache: set MD_JOURNAL_CLEAN correctly
  • From: Shaohua Li <shli@xxxxxxxxxx>
• bootsect replicated in p1, RAID enclosure suggestions?
  • From: travis+ml-linux-raid@xxxxxxxxxxxxxxxxx
• [PATCH 1/2] raid5: fix memory leak of bio integrity data
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 2/2] raid5: avoid unnecessary bio data set
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH] raid6: fix the input of raid6 algorithm
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• [PATCH] raid6: fix the input of raid6 algorithm
  • From: liuzhengyuan@xxxxxxxxxx
• Re: Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Need Help with crashed RAID5 (that was rebuilding and then had SATA error on another drive)
  • From: Ben Kamen <benjammin2068@xxxxxxxxx>
• Re: [PATCH v2 0/6] Add AVX512 optimized gen_syndrome, xor_syndrome and recovery functions
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [RFC] Some fixes to allow for more than 128 md devices.
  • From: Robert LeBlanc <robert@xxxxxxxxxxxxx>
• Re: Assistance Reviewing Proposed Recovery Measures
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH -next] md-cluster: fix error return code in join()
  • From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
• Re: Rewrite md raid1 member
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Assistance Reviewing Proposed Recovery Measures
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Rewrite md raid1 member
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Re: Assistance Reviewing Proposed Recovery Measures
  • From: Sarah Newman <srn@xxxxxxxxx>
• [RFC] Some fixes to allow for more than 128 md devices.
  • From: Robert LeBlanc <robert@xxxxxxxxxxxxx>
• [RFC] Some fixes to allow for more than 128 md devices.
  • From: Robert LeBlanc <robert@xxxxxxxxxxxxx>
• Re: Rewrite md raid1 member
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• Re: Rewrite md raid1 member
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• [PATCH 2/2] r5cache: remove journal support
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 1/2] r5cache: set MD_JOURNAL_CLEAN correctly
  • From: Song Liu <songliubraving@xxxxxx>
• Re: Rewrite md raid1 member
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• Assistance Reviewing Proposed Recovery Measures
  • From: Chris Maxwell <cmaxwell@xxxxxx>
• Re: Rewrite md raid1 member
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: URE, link resets, user hostile defaults
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Rewrite md raid1 member
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• Re: URE, link resets, user hostile defaults
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Rewrite md raid1 member
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: URE, link resets, user hostile defaults
  • From: Pasi Kärkkäinen <pasik@xxxxxx>
• Re: Adding journal to existing raid5 arrary
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 09/16] md: raid5: Convert to hotplug state machine
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• OOM/panic observed durintg creating RAID4 with DIF/DIX enabled disk
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• raid6 algorithm issues with 64K page_size
  • From: Zhengyuan Liu <liuzhengyuang521@xxxxxxxxx>
• Re: Adding journal to existing raid5 arrary
  • From: Maarten van Malland <maartenvanmalland@xxxxxxxxx>
• Re: Rewrite md raid1 member
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• Re: Rewrite md raid1 member
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Rewrite md raid1 member
  • From: Chris Dunlop <chris@xxxxxxxxxxxx>
• Re: Adding journal to existing raid5 arrary
  • From: Song Liu <songliubraving@xxxxxx>
• Adding journal to existing raid5 arrary
  • From: Maarten van Malland <maartenvanmalland@xxxxxxxxx>
• Re: [PATCH] md: don't print the same repeated messages about delayed sync operation
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] raid10: record correct address of bad block
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: How to get md to attempt to scrub blocks in its bad blocks list
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• How to get md to attempt to scrub blocks in its bad blocks list
  • From: Tim Small <tim@xxxxxxxxxxxxxxxx>
• Re: [PATCH V2 00/10] The latest changes for md-cluster
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 1/3] MD: hold mddev lock for .quiesce in md_do_sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md: do not count journal as spare in GET_ARRAY_INFO
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: Can't mount Old RHEL 6 Raid with new install of CentOS 7, now can't mount with original RHEL 6
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Can't mount Old RHEL 6 Raid with new install of CentOS 7, now can't mount with original RHEL 6
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: read errors with md RAID5 array
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Can't mount Old RHEL 6 Raid with new install of CentOS 7, now can't mount with original RHEL 6
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Can't mount Old RHEL 6 Raid with new install of CentOS 7, now can't mount with original RHEL 6
  • From: John Dawson <linux@xxxxxxxxxxxxxxx>
• Re: read errors with md RAID5 array
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• [PATCH] md: don't print the same repeated messages about delayed sync operation
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: read errors with md RAID5 array
  • From: Tim Small <tim@xxxxxxxxxxxxxxxx>
• Re: read errors with md RAID5 array
  • From: Tim Small <tim@xxxxxxxxxxxxxxxx>
• Re: Raid5 reshape stuck at 0% - SuSE leap 42.1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• [RFC PATCH 02/16] DM: Ability to choose the compressor.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 03/16] DM: Error if enough space is not available.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 07/16] DM: Optimize memory allocated to hold compressed buffer.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 04/16] DM: Ensure that the read request is within the device range.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 01/16] DM: dm-inplace-compress: an inplace compressed DM target
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 06/16] DM: separate out compression and decompression routines.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 10/16] DM: Try to use the bio buffer for decompression instead of allocating one.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 05/16] DM: allocation/free helper routines.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 08/16] DM: Tag a magicmarker at the end of each compressed segment.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 13/16] DM: macros to set and get the state of the request.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 11/16] DM: Try to avoid temporary buffer allocation to hold compressed data.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 14/16] DM: Wasted bio copy.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 12/16] DM: release unneeded buffer as soon as possible.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 15/16] DM: Add sysfs parameters to track total memory saved and allocated.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 16/16] DM: add documentation for dm-inplace-compress.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 09/16] DM: Delay allocation of decompression buffer during read.
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• [RFC PATCH 00/16] dm-inplace-compression block device
  • From: Ram Pai <linuxram@xxxxxxxxxx>
• Re: [PATCH] mdadm: add man page for --add-journal
  • From: Song Liu <songliubraving@xxxxxx>
• Re: read errors with md RAID5 array
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: read errors with md RAID5 array
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: read errors with md RAID5 array
  • From: Tim Small <tim@xxxxxxxxxxxxxxxx>
• Re: [PATCH] mdadm: add man page for --add-journal
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: read errors with md RAID5 array
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• read errors with md RAID5 array
  • From: Tim Small <tim@xxxxxxxxxxxxxxxx>
• Re: [PATCH] mdadm: add man page for --add-journal
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• [PATCH v2 0/6] Add AVX512 optimized gen_syndrome, xor_syndrome and recovery functions
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• [PATCH v2 1/6] lib/raid6: Add AVX512 optimized gen_syndrome functions
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• [PATCH v2 2/6] lib/raid6: Add AVX512 optimized recovery functions
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• [PATCH v2 3/6] lib/raid6/test/Makefile: Add avx512 gen_syndrome and recovery functions
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• [PATCH v2 4/6] lib/raid6: Add AVX512 optimized xor_syndrome functions
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• [PATCH v2 6/6] (DO NOT APPLY) lib/raid6: Add unroll by 8 to AVX512 optimized xor_syndrome functions.
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• [PATCH v2 5/6] (DO NOT APPLY) lib/raid6: Add unroll by 8 to AVX512 optimized gen_syndrome functions
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• best kernel ??
  • From: bobzer <bobzer@xxxxxxxxx>
• Re: [PATCH v2] block: make sure big bio is splitted into at most 256 bvecs
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH] mdadm: put journal device in right place of --detail
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH] mdadm: add man page for --add-journal
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Unable to convert raid1 to raid5
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH v2] block: make sure big bio is splitted into at most 256 bvecs
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• [PATCH] raid10: record correct address of bad block
  • From: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx>
• [PATCH V2 04/10] md: changes for MD_STILL_CLOSED flag
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH V2 06/10] md-cluster: protect md_find_rdev_nr_rcu with rcu lock
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH V2 03/10] md-cluster: remove some unnecessary dlm_unlock_sync
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH V2 09/10] md-cluster: introduce dlm_lock_sync_interruptible to fix tasks hang
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH V2 08/10] md-cluster: convert the completion to wait queue
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH V2 07/10] md: remove obsolete ret in md_start_sync
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH V2 10/10] md-cluster: make resync lock also could be interruptted
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH V2 02/10] md-cluster: use FORCEUNLOCK in lockres_free
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH V2 01/10] md-cluster: call md_kick_rdev_from_array once ack failed
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH V2 05/10] md-cluster: clean related infos of cluster
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH V2 00/10] The latest changes for md-cluster
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: Can't mount Old RHEL 6 Raid with new install of CentOS 7, now can't mount with original RHEL 6
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Unable to convert raid1 to raid5
  • From: NeilBrown <nfbrown@xxxxxxxxxx>
• [PATCH] md: do not count journal as spare in GET_ARRAY_INFO
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH] mdadm: put journal device in right place of --detail
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH] mdadm: add man page for --add-journal
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 1/3] MD: hold mddev lock for .quiesce in md_do_sync
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v2] block: make sure big bio is splitted into at most 256 bvecs
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Can't mount Old RHEL 6 Raid with new install of CentOS 7, now can't mount with original RHEL 6
  • From: John Dawson <linux@xxxxxxxxxxxxxxx>
• Re: [PATCH] NULL pointer in raid1_make_request passed to bio_trim when adding md as bcache caching dev
  • From: Eric Wheeler <bcache@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] block: make sure big bio is splitted into at most 256 bvecs
  • From: Eric Wheeler <bcache@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] NULL pointer in raid1_make_request passed to bio_trim when adding md as bcache caching dev
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH v2 1/1] block: fix blk_queue_split() resource exhaustion
  • From: Eric Wheeler <bcache@xxxxxxxxxxxxxxxxxx>
• [PATCH] NULL pointer in raid1_make_request passed to bio_trim when adding md as bcache caching dev
  • From: Eric Wheeler <bcache@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] Incremental: don't try to load_container() for a subarray
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• [PATCH] Incremental: don't try to load_container() for a subarray
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: The subarray is loaded container by load_container
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: No '--add-journal' helper page in "man mdadm" and "mdadm --manage --help"
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 1/2] MD: add extra parameter for .quiesce
  • From: shli@xxxxxxxxxx
• [PATCH 2/2] MD: make sure raid5-cache superblock write with reconfig_mutex hold
  • From: shli@xxxxxxxxxx
• [PATCH -next] dm flakey: fix error return code in flakey_ctr()
  • From: Wei Yongjun <weiyj.lk@xxxxxxxxx>
• Re: Raid5 reshape stuck at 0% - SuSE leap 42.1
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Raid5 reshape stuck at 0% - SuSE leap 42.1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid5 reshape stuck at 0% - SuSE leap 42.1
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Raid5 reshape stuck at 0% - SuSE leap 42.1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid5 reshape stuck at 0% - SuSE leap 42.1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid5 reshape stuck at 0% - SuSE leap 42.1
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Raid5 reshape stuck at 0% - SuSE leap 42.1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid5 reshape stuck at 0% - SuSE leap 42.1
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Raid5 reshape stuck at 0% - SuSE leap 42.1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid5 reshape stuck at 0% - SuSE leap 42.1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid5 reshape stuck at 0% - SuSE leap 42.1
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Raid5 reshape stuck at 0% - SuSE leap 42.1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Unable to convert raid1 to raid5
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Unable to convert raid1 to raid5
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: migration of raid 5 to raid 6 and disk of 2TB to 4TB
  • From: bobzer <bobzer@xxxxxxxxx>
• Re: RAID5 Performance
  • From: pg@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: [PATCH 1/3] MD: hold mddev lock for .quiesce in md_do_sync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: INFO: task systemd-udevd:794 blocked for more than 600 seconds observed after mdadm -G operation
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: migration of raid 5 to raid 6 and disk of 2TB to 4TB
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 4/8] md-cluster: introduce dlm_lock_sync_interruptible to fix tasks hang
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH][RESEND] md: Prevent IO hold during accessing to faulty raid5 array
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Unable to convert raid1 to raid5
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• RAID 6 "Bad block number requested"
  • From: "Jens-U. Mozdzen" <jmozdzen@xxxxxx>
• Re: journal disk become the first of --detail list after fail/remove one disk
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: INFO: task systemd-udevd:794 blocked for more than 600 seconds observed after mdadm -G operation
  • From: yizhan <yizhan@xxxxxxxxxx>
• Re: INFO: task systemd-udevd:794 blocked for more than 600 seconds observed after mdadm -G operation
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH RFC] mm, writeback: flush plugged IO in wakeup_flusher_threads()
  • From: Konstantin Khlebnikov <koct9i@xxxxxxxxx>
• xosview - anybody willing to test it (the raid features :-)
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH RFC] mm, writeback: flush plugged IO in wakeup_flusher_threads()
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH RFC] mm, writeback: flush plugged IO in wakeup_flusher_threads()
  • From: Konstantin Khlebnikov <khlebnikov@xxxxxxxxxxxxxx>
• Re: The subarray is loaded container by load_container
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 37/45] drivers: use req op accessor
  • From: Shaun Tancheff <shaun.tancheff@xxxxxxxxxxx>
• INFO: task systemd-udevd:794 blocked for more than 600 seconds observed after mdadm -G operation
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• Re: [PATCH 37/45] drivers: use req op accessor
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: journal disk become the first of --detail list after fail/remove one disk
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• No '--add-journal' helper page in "man mdadm" and "mdadm --manage --help"
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• journal disk become the first of --detail list after fail/remove one disk
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• Re: [PATCH 37/45] drivers: use req op accessor
  • From: Mike Christie <mchristi@xxxxxxxxxx>
• Re: [PATCH 1/3] MD: hold mddev lock for .quiesce in md_do_sync
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 37/45] drivers: use req op accessor
  • From: Shaun Tancheff <shaun.tancheff@xxxxxxxxxxx>
• Re: [PATCH 37/45] drivers: use req op accessor
  • From: Mike Christie <mchristi@xxxxxxxxxx>
• Re: [PATCH] raid5: fix incorrectly counter of conf->empty_inactive_list_nr
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 37/45] drivers: use req op accessor
  • From: Ross Zwisler <zwisler@xxxxxxxxx>
• Re: Inactive arrays
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: [PATCH 42/45] block, fs, drivers: remove REQ_OP compat defs and related code
  • From: Mike Christie <mchristi@xxxxxxxxxx>
• Re: [PATCH 42/45] block, fs, drivers: remove REQ_OP compat defs and related code
  • From: Ross Zwisler <zwisler@xxxxxxxxx>
• [PATCH][RESEND] md: Prevent IO hold during accessing to faulty raid5 array
  • From: Alexey Obitotskiy <aleksey.obitotskiy@xxxxxxxxx>
• AW: [PATCH 0/4] Add AVX512 optimized gen_syndrome and recovery functions
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: [PATCH] raid5: fix incorrectly counter of conf->empty_inactive_list_nr
  • From: "liuzhengyuan" <liuzhengyuan@xxxxxxxxxx>
• Re: [PATCH 3/3] MD: hold mddev lock for md-cluster receive thread
  • From: Guoqing Jiang <jgq516@xxxxxxxxx>
• Re: [PATCH 3/3] MD: hold mddev lock for md-cluster receive thread
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: WARNING: CPU: 4 PID: 10512 at drivers/md/raid5-cache.c:728 r5l_do_reclaim+0x415/0x430 [raid456]
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 4/8] md-cluster: introduce dlm_lock_sync_interruptible to fix tasks hang
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH V2 1/8] md-cluster: call md_kick_rdev_from_array once ack failed
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 1/8] md-cluster: call md_kick_rdev_from_array once ack failed
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH] raid5: fix incorrectly counter of conf->empty_inactive_list_nr
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 3/3] MD: hold mddev lock for md-cluster receive thread
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 2/3] MD: hold mddev lock to change bitmap location
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 1/3] MD: hold mddev lock for .quiesce in md_do_sync
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH 4/4] (DO NOT APPLY) lib/raid6: Add unroll by 8 to AVX512 optimized gen_syndrome functions
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• [PATCH 3/4] lib/raid6/test/Makefile: Add avx512 gen_syndrome and recovery functions
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• [PATCH 2/4] lib/raid6: Add AVX512 optimized recovery functions
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• [PATCH 1/4] lib/raid6: Add AVX512 optimized gen_syndrome functions
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• [PATCH 0/4] Add AVX512 optimized gen_syndrome and recovery functions
  • From: Gayatri Kammela <gayatri.kammela@xxxxxxxxx>
• Re: [PATCH 4/8] md-cluster: introduce dlm_lock_sync_interruptible to fix tasks hang
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 3/3] MD: hold mddev lock for md-cluster receive thread
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 1/8] md-cluster: call md_kick_rdev_from_array once ack failed
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 0/4] Add AVX512 optimized gen_syndrome and recovery functions
  • From: Shaohua Li <shli@xxxxxxxxxx>
• RE: [PATCH 0/4] Add AVX512 optimized gen_syndrome and recovery functions
  • From: "Kammela, Gayatri" <gayatri.kammela@xxxxxxxxx>
• [PATCH 0314/1285] Replace numeric parameter like 0444 with macro
  • From: Baole Ni <baolex.ni@xxxxxxxxx>
• Re: [PATCH] mdadm:add 'clustered' in typo prompt when specify wrong param for bitmap
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: WARNING: CPU: 4 PID: 10512 at drivers/md/raid5-cache.c:728 r5l_do_reclaim+0x415/0x430 [raid456]
  • From: yizhan <yizhan@xxxxxxxxxx>
• [PATCH 0315/1285] Replace numeric parameter like 0444 with macro
  • From: Baole Ni <baolex.ni@xxxxxxxxx>
• Re: Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: WARNING: CPU: 4 PID: 10512 at drivers/md/raid5-cache.c:728 r5l_do_reclaim+0x415/0x430 [raid456]
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: Inactive arrays
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 3/3] MD: hold mddev lock for md-cluster receive thread
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH] mdadm:add 'clustered' in typo prompt when specify wrong param for bitmap
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• Inactive arrays
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: RAID5 Performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 4/8] md-cluster: introduce dlm_lock_sync_interruptible to fix tasks hang
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 1/8] md-cluster: call md_kick_rdev_from_array once ack failed
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 6/8] md-cluster: make resync lock also could be interruptted
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 6/8] md-cluster: make resync lock also could be interruptted
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 4/8] md-cluster: introduce dlm_lock_sync_interruptible to fix tasks hang
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 1/8] md-cluster: call md_kick_rdev_from_array once ack failed
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 3/3] MD: hold mddev lock for md-cluster receive thread
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: xosview
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: xosview
  • From: Bill Hudacek <bill.hudacek@xxxxxxxxx>
• One question about raid10 resync
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: WARNING: CPU: 4 PID: 10512 at drivers/md/raid5-cache.c:728 r5l_do_reclaim+0x415/0x430 [raid456]
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• Re: WARNING: CPU: 4 PID: 10512 at drivers/md/raid5-cache.c:728 r5l_do_reclaim+0x415/0x430 [raid456]
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 3/3] MD: hold mddev lock for md-cluster receive thread
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: To add, or not to add, a bio REQ_ROTATIONAL flag
  • From: Eric Wheeler <bcache@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/3] MD: hold mddev lock for .quiesce in md_do_sync
  • From: yizhan <yizhan@xxxxxxxxxx>
• [PATCH 2/3] MD: hold mddev lock to change bitmap location
  • From: shli@xxxxxxxxxx
• [PATCH 3/3] MD: hold mddev lock for md-cluster receive thread
  • From: shli@xxxxxxxxxx
• [PATCH 1/3] MD: hold mddev lock for .quiesce in md_do_sync
  • From: shli@xxxxxxxxxx
• Re: [PATCH] raid5: fix incorrectly counter of conf->empty_inactive_list_nr
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] raid10: increment write counter after bio is split
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md: Prevent IO hold during accessing to failed raid5 array
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: xosview
  • From: Glenn Enright <glenn.enright@xxxxxxxxx>
• xosview
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH] md: Prevent IO hold during accessing to failed raid5 array
  • From: "Obitotskiy, Aleksey" <aleksey.obitotskiy@xxxxxxxxx>
• Re: To add, or not to add, a bio REQ_ROTATIONAL flag
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: To add, or not to add, a bio REQ_ROTATIONAL flag
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• To add, or not to add, a bio REQ_ROTATIONAL flag
  • From: Eric Wheeler <bcache@xxxxxxxxxxxxxxxxxx>
• Re: SOLVED [was Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?]
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: SOLVED [was Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?]
  • From: Andreas Dröscher <raid@xxxxxxxxxx>
• Re: RAID5 Performance
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: RAID5 Performance
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: RAID5 Performance
  • From: pg@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• [GIT PULL] MD update for 4.8
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: RAID5 Performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID5 Performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID5 Performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID5 Performance
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: RAID5 Performance
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• Re: SOLVED [was Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?]
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• Re: RAID5 Performance
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• [PATCH] raid10: increment write counter after bio is split
  • From: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx>
• Re: test file disappeared after -f, -r, --add-journal for write-journal device
  • From: yizhan <yizhan@xxxxxxxxxx>
• [PATCH] raid5: fix incorrectly counter of conf->empty_inactive_list_nr
  • From: ZhengYuan Liu <liuzhengyuan@xxxxxxxxxx>
• [PATCH 8/8] md-cluster: remove EXPERIMENTAL info
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 6/8] md-cluster: make resync lock also could be interruptted
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 7/8] md-cluster: clean related infos of cluster
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 5/8] md: changes for MD_STILL_CLOSED flag
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 4/8] md-cluster: introduce dlm_lock_sync_interruptible to fix tasks hang
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 3/8] md-cluster: remove some unnecessary dlm_unlock_sync
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 2/8] md-cluster: use FORCEUNLOCK in lockres_free
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 1/8] md-cluster: call md_kick_rdev_from_array once ack failed
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: Kernel deadlock during mdadm reshape
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: test file disappeared after -f, -r, --add-journal for write-journal device
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: WARNING: CPU: 4 PID: 10512 at drivers/md/raid5-cache.c:728 r5l_do_reclaim+0x415/0x430 [raid456]
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] raid5: fix incorrectly counter of conf->empty_inactive_list_nr
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: RAID5 Performance
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• SOLVED [was: Re: Lost RAID6 disks when moving to new PC]
  • From: Alex Owen <alex@xxxxxxxxxxxx>
• Re: RAID5 Performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: SOLVED [was Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?]
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: SOLVED [was Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?]
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: RAID5 Performance
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: migration of raid 5 to raid 6 and disk of 2TB to 4TB
  • From: pg@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Lost RAID6 disks when moving to new PC
  • From: Alex Owen <alex@xxxxxxxxxxxx>
• Re: migration of raid 5 to raid 6 and disk of 2TB to 4TB
  • From: pg@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: RAID5 Performance
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: SOLVED [was Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?]
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: migration of raid 5 to raid 6 and disk of 2TB to 4TB
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: migration of raid 5 to raid 6 and disk of 2TB to 4TB
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• Re: migration of raid 5 to raid 6 and disk of 2TB to 4TB
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: migration of raid 5 to raid 6 and disk of 2TB to 4TB
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: The subarray is loaded container by load_container
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• Re: SOLVED [was Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?]
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• test file disappeared after -f, -r, --add-journal for write-journal device
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• Re: Lost RAID6 disks when moving to new PC
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• WARNING: CPU: 4 PID: 10512 at drivers/md/raid5-cache.c:728 r5l_do_reclaim+0x415/0x430 [raid456]
  • From: Yi Zhang <yizhan@xxxxxxxxxx>
• Lost RAID6 disks when moving to new PC
  • From: Alex Owen <alex@xxxxxxxxxxxx>
• SOLVED [was Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?]
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: RAID5 Performance
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: RAID5 Performance
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• RAID5 Performance
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Kernel deadlock during mdadm reshape
  • From: Michael Shaver <jmshaver@xxxxxxxxx>
• Re: migration of raid 5 to raid 6 and disk of 2TB to 4TB
  • From: bobzer <bobzer@xxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• GPT Table broken on a Raid1 (necroposting)
  • From: Luis Panadero Guardeño <luis.panadero@xxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: migration of raid 5 to raid 6 and disk of 2TB to 4TB
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: migration of raid 5 to raid 6 and disk of 2TB to 4TB
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• GPT corruption on Primary Header, backup OK, fixing primary nuked array -- help?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: migration of raid 5 to raid 6 and disk of 2TB to 4TB
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: migration of raid 5 to raid 6 and disk of 2TB to 4TB
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• migration of raid 5 to raid 6 and disk of 2TB to 4TB
  • From: bobzer <bobzer@xxxxxxxxx>
• Re: [PATCH v2 1/1] block: fix blk_queue_split() resource exhaustion
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: Cannot start array on disk
  • From: Bhatia Amit <amitbhatia@xxxxxxxxxxxxxx>
• Re: Cannot start array on disk
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Cannot start array on disk
  • From: Bhatia Amit <amitbhatia@xxxxxxxxxxxxxx>
• Re: Cannot start array on disk
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Cannot start array on disk
  • From: Bhatia Amit <amitbhatia@xxxxxxxxxxxxxx>
• Re: Cannot start array on disk
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Recovering RAID Volumes from 6 Disks
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: How does md gurantee not miss to free an active stripe_head when md stops?
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v2 1/1] block: fix blk_queue_split() resource exhaustion
  • From: Eric Wheeler <bcache@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mdcheck: Send progress messages to system log
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH] Monitor: release /proc/mdstat fd when no arrays present
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH v3] Remove: container should wait for an array to release a drive
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• [PATCH v3] Remove: container should wait for an array to release a drive
  • From: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx>
• Re: [PATCH v4 18/21] fuse: Add support for pid namespaces
  • From: Miklos Szeredi <mszeredi@xxxxxxxxxx>
• Re: dm stripe: add DAX support
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: Cannot start array on disk
  • From: Bhatia Amit <amitbhatia@xxxxxxxxxxxxxx>
• Re: dm stripe: add DAX support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v4 18/21] fuse: Add support for pid namespaces
  • From: Sheng Yang <sheng@xxxxxxxxxx>
• Re: [PATCH v2] Remove: container should wait for an array to release a drive
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Recovering RAID Volumes from 6 Disks
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Recovering RAID Volumes from 6 Disks
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Recovering RAID Volumes from 6 Disks
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Recovering RAID Volumes from 6 Disks
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Recovering RAID Volumes from 6 Disks
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH v4 18/21] fuse: Add support for pid namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: How does md gurantee not miss to free an active stripe_head when md stops?
  • From: "Vaughan" <cxt9401@xxxxxxx>
• Re: Cannot start array on disk
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH] raid5: fix incorrectly counter of conf->empty_inactive_list_nr
  • From: Zhengyuan Liu <liuzhengyuang521@xxxxxxxxx>
• [PATCH v2] Remove: container should wait for an array to release a drive
  • From: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx>
• Re: [PATCH] raid10: improve random reads performance
  • From: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx>
• RE: [PATCH] md: Prevent IO hold during accessing to failed raid5 array
  • From: "Obitotskiy, Aleksey" <aleksey.obitotskiy@xxxxxxxxx>
• Re: Cannot start array on disk
  • From: Bhatia Amit <amitbhatia@xxxxxxxxxxxxxx>
• Re: [PATCH v4 18/21] fuse: Add support for pid namespaces
  • From: Sheng Yang <sheng@xxxxxxxxxx>
• Re: Cannot start array on disk
  • From: Bhatia Amit <amitbhatia@xxxxxxxxxxxxxx>
• Re: a hard lockup in md raid5 sequential write (v4.7-rc7)
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md: Prevent IO hold during accessing to failed raid5 array
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Recovering RAID Volumes from 6 Disks
  • From: Amit Biswas <abiswas@xxxxxxx>
• Re: [PATCH] raid10: improve random reads performance
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH RFC] md/raid1: fix deadlock between freeze_array() and wait_barrier().
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Recovering RAID Volumes from 6 Disks
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH] md: add missing sysfs_notify on array_state update
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] Fix kernel module refcount handling
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md: use seconds granularity for error logging
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Recovering RAID Volumes from 6 Disks
  • From: Amit Biswas <abiswas@xxxxxxx>
• Re: [PATCH] Remove: container should wait for an array to release a drive
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH] Remove: container should wait for an array to release a drive
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH RFC] md/raid1: fix deadlock between freeze_array() and wait_barrier().
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Cannot start array on disk
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH v2 1/1] block: fix blk_queue_split() resource exhaustion
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• Re: [PATCH] Remove: container should wait for an array to release a drive
  • From: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx>
• Re: [PATCH] Remove: container should wait for an array to release a drive
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• superblock help
  • From: Bryan Hepworth <bryan.hepworth@xxxxxxxxxxxxxxx>
• Re: [PATCH] Remove: container should wait for an array to release a drive
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• [PATCH] Remove: container should wait for an array to release a drive
  • From: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx>
• Re: raid5/6: general protection fault in async_copy_data
  • From: Joey Liao <joeyliao@xxxxxxxx>
• Raid1 rcu stall while I/O stress test
  • From: Chien Lee <chienlee@xxxxxxxx>
• Re: Recover filenames from failed RAID0
  • From: keld@xxxxxxxxxx
• How does md gurantee not miss to free an active stripe_head when md stops?
  • From: "Vaughan" <cxt9401@xxxxxxx>
• a hard lockup in md raid5 sequential write (v4.7-rc7)
  • From: Coly Li <colyli@xxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage) with check/repair/sync
  • From: Matthias Dahl <ml_linux-kernel@xxxxxxxxxxxxxxxx>
• Cannot start array on disk
  • From: Bhatia Amit <amitbhatia@xxxxxxxxxxxxxx>
• Re: Recover filenames from failed RAID0
  • From: Michel Dubois <michel.dubois.mtl@xxxxxxxxx>
• Re: Help with assembling a stopped array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Help with assembling a stopped array
  • From: Vegard Haugland <vegard@xxxxxxxxxxx>
• Re: dm: fix parameter to blk_delay_queue()
  • From: Tahsin Erdogan <tahsin@xxxxxxxxxx>
• Re: dm: fix parameter to blk_delay_queue()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm: fix parameter to blk_delay_queue()
  • From: Tahsin Erdogan <tahsin@xxxxxxxxxx>
• [PATCH] md: Prevent IO hold during accessing to failed raid5 array
  • From: Alexey Obitotskiy <aleksey.obitotskiy@xxxxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage) with check/repair/sync
  • From: Matthias Dahl <ml_linux-kernel@xxxxxxxxxxxxxxxx>
• Re: Recover filenames from failed RAID0
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH RFC] md/raid1: fix deadlock between freeze_array() and wait_barrier().
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH RFC] md/raid1: fix deadlock between freeze_array() and wait_barrier().
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
• Re: Help with assembling a stopped array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Help with assembling a stopped array
  • From: Vegard Haugland <vegard@xxxxxxxxxxx>
• Re: [dm-devel] Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Matthias Dahl <ml_linux-kernel@xxxxxxxxxxxxxxxx>
• Fwd: kernel checksumming performance vs actual raid device performance
  • From: Doug Dumitru <doug@xxxxxxxxxx>
• Re: [dm-devel] Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• Re: dm stripe: add DAX support
  • From: "Kani, Toshimitsu" <toshi.kani@xxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Matthias Dahl <ml_linux-kernel@xxxxxxxxxxxxxxxx>
• Re: Help with assembling a stopped array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Matthias Dahl <ml_linux-kernel@xxxxxxxxxxxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: kernel checksumming performance vs actual raid device performance
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 1/1] block: fix blk_queue_split() resource exhaustion
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [dm-devel] [PATCH v2 1/1] block: fix blk_queue_split() resource exhaustion
  • From: Eric Wheeler <bcache@xxxxxxxxxxxxxxxxxx>
• Re: dm stripe: add DAX support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Help with assembling a stopped array
  • From: Vegard Haugland <vegard@xxxxxxxxxxx>
• Re: dm stripe: add DAX support
  • From: "Kani, Toshimitsu" <toshi.kani@xxxxxxx>
• Re: [PATCH RFC] md/raid1: fix deadlock between freeze_array() and wait_barrier().
  • From: NeilBrown <neilb@xxxxxxxx>
• kernel checksumming performance vs actual raid device performance
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Matthias Dahl <ml_linux-kernel@xxxxxxxxxxxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Matthias Dahl <ml_linux-kernel@xxxxxxxxxxxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Matthias Dahl <ml_linux-kernel@xxxxxxxxxxxxxxxx>
• Re: [PATCH RFC] md/raid1: fix deadlock between freeze_array() and wait_barrier().
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Michal Hocko <mhocko@xxxxxxxxxx>
• Page Allocation Failures/OOM with dm-crypt on software RAID10 (Intel Rapid Storage)
  • From: Matthias Dahl <ml_linux-kernel@xxxxxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH v2 1/1] block: fix blk_queue_split() resource exhaustion
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 1/1] block: fix blk_queue_split() resource exhaustion
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• [PATCH v2 1/1] block: fix blk_queue_split() resource exhaustion
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• Re: [PATCH 1/1] block: fix blk_queue_split() resource exhaustion
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 1/1] block: fix blk_queue_split() resource exhaustion
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• [PATCH 0/1] block: fix blk_queue_split() resource exhaustion
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• Re: dm: raid456 basic support
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [dm-devel] [RFC] block: fix blk_queue_split() resource exhaustion
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• Re: block: fix blk_queue_split() resource exhaustion
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [dm-devel] [RFC] block: fix blk_queue_split() resource exhaustion
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• Re: [dm-devel] [RFC] block: fix blk_queue_split() resource exhaustion
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• Re: [dm-devel] [RFC] block: fix blk_queue_split() resource exhaustion
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: [dm-devel] [RFC] block: fix blk_queue_split() resource exhaustion
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [dm-devel] [RFC] block: fix blk_queue_split() resource exhaustion
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• re: dm: raid456 basic support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH RFC] md/raid1: fix deadlock between freeze_array() and wait_barrier().
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: block: fix blk_queue_split() resource exhaustion
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [dm-devel] [RFC] block: fix blk_queue_split() resource exhaustion
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: block: fix blk_queue_split() resource exhaustion
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC] block: fix blk_queue_split() resource exhaustion
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: block: fix blk_queue_split() resource exhaustion
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>