Linux RAID Storage Date Index

• Thread Index

• Re: [PATCH v5 2/8] md: Neither resync nor reshape while the system is frozen
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: Linux Plumbers MD BOF discussion notes
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: Linux Plumbers MD BOF discussion notes
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH v2] mdmon: get safe mode delay file descriptor early
  • From: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx>
• Re: [PATCH v5 2/8] md: Neither resync nor reshape while the system is frozen
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: [PATCH v5 1/8] md: Introduce md_stop_all_writes()
  • From: "Luis R. Rodriguez" <mcgrof@xxxxxxxxxx>
• Re: Linux Plumbers MD BOF discussion notes
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Is the LSI SAS9211-8i still the go to HBA?
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: [PATCH] imsm: Set disk slot number
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] mdmon: get safe mode delay file descriptor early
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [PATCH] imsm: Set disk slot number
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• [PATCH] mdmon: get safe mode delay file descriptor early
  • From: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx>
• [PATCH] md-cluster: make function cluster_check_sync_size static
  • From: Colin King <colin.king@xxxxxxxxxxxxx>
• Re: Is the LSI SAS9211-8i still the go to HBA?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Is the LSI SAS9211-8i still the go to HBA?
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: Is the LSI SAS9211-8i still the go to HBA?
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Is the LSI SAS9211-8i still the go to HBA?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [PATCH 00/18] use ARRAY_SIZE macro
  • From: Jérémy Lefaure <jeremy.lefaure@xxxxxxxxxxxx>
• Re: Is the LSI SAS9211-8i still the go to HBA?
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: [MDADM PATCH 2/2] Give enough time to udev to handle events
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH v5 1/8] md: Introduce md_stop_all_writes()
  • From: Bart Van Assche <bart.vanassche@xxxxxxx>
• [PATCH v5 2/8] md: Neither resync nor reshape while the system is frozen
  • From: Bart Van Assche <bart.vanassche@xxxxxxx>
• Re: [PATCH 00/12] Multiple PPL support and PPL bugfixes
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 0/3] mdadm patches for some trivial fixes
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] Monitor: Check redundancy for arrays
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] imsm: New disk controller domains
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] Grow: stop previous reshape process first
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 00/18] use ARRAY_SIZE macro
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [MDADM PATCH 2/2] Give enough time to udev to handle events
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [MDADM PATCH 1/2] Close mdfd before returning main function
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 00/18] use ARRAY_SIZE macro
  • From: Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxxxxx>
• Re: [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: Is the LSI SAS9211-8i still the go to HBA?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [mdadm PATCH 1/1] Fix a build error
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Is the LSI SAS9211-8i still the go to HBA?
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: [PATCH 00/18] use ARRAY_SIZE macro
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH 0/2] Two fixes for PPL recovery
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 00/18] use ARRAY_SIZE macro
  • From: Jérémy Lefaure <jeremy.lefaure@xxxxxxxxxxxx>
• Re: [mdadm PATCH 1/1] Fix a build error
  • From: Jes Sorensen <jsorensen@xxxxxx>
• Re: [PATCH 00/18] use ARRAY_SIZE macro
  • From: "Tobin C. Harding" <me@xxxxxxxx>
• [PATCH 11/18] dm space map metadata: use ARRAY_SIZE
  • From: Jérémy Lefaure <jeremy.lefaure@xxxxxxxxxxxx>
• [PATCH 00/18] use ARRAY_SIZE macro
  • From: Jérémy Lefaure <jeremy.lefaure@xxxxxxxxxxxx>
• Re: Linux Plumbers MD BOF discussion notes
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Accidentally resized array to 9
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Accidentally resized array to 9
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Accidentally resized array to 9
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [mdadm PATCH 1/1] Fix a build error
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Latest on SSD Raid
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: [mdadm PATCH 1/1] Fix a build error
  • From: Jes Sorensen <jsorensen@xxxxxx>
• Re: Latest on SSD Raid
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: [PATCH 0/4] RFC: attempt to remove md deadlocks with metadata without
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Stuck in md_write_start because MD_SB_CHANGE_PENDING can't be cleared
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [MDADM PATCH 2/2] Give enough time to udev to handle events
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [MDADM PATCH 2/2] Give enough time to udev to handle events
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Linux Plumbers MD BOF discussion notes
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [mdadm PATCH 1/1] Fix a build error
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Accidentally resized array to 9
  • From: Eli Ben-Shoshan <eli@xxxxxxxxxxxxxx>
• Re: [mdadm PATCH 1/1] Fix a build error
  • From: Jes Sorensen <jsorensen@xxxxxx>
• Re: Accidentally resized array to 9
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Accidentally resized array to 9
  • From: Eli Ben-Shoshan <eli@xxxxxxxxxxxxxx>
• [PATCH 2/2] raid5-ppl: check recovery_offset when performing ppl recovery
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH 1/2] raid5-ppl: don't resync after rebuild
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH 0/2] Two fixes for PPL recovery
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: Accidentally resized array to 9
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Accidentally resized array to 9
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• [GIT PULL] MD update for 4.14-rc3
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 2/2] md: clear THREAD_WAKEUP flag in mddev_trylock
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 1/2] md-cluster: fix wrong condition check in raid1_write_request
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Is the LSI SAS9211-8i still the go to HBA?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Latest on SSD Raid
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Latest on SSD Raid
  • From: Dag Nygren <dag@xxxxxxxxxx>
• Re: Accidentally resized array to 9
  • From: Eli Ben-Shoshan <eli@xxxxxxxxxxxxxx>
• Re: Accidentally resized array to 9
  • From: Eli Ben-Shoshan <eli@xxxxxxxxxxxxxx>
• Re: occasional hard lockup on raid on nvme disks (fio processes hung)
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: Accidentally resized array to 9
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Accidentally resized array to 9
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Accidentally resized array to 9
  • From: Eli Ben-Shoshan <eli@xxxxxxxxxxxxxx>
• [PATCH 2/2] md: clear THREAD_WAKEUP flag in mddev_trylock
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 1/2] md-cluster: fix wrong condition check in raid1_write_request
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: Need Help for Raid Recovery
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• [PATCH 10/12] imsm: always do ppl recovery when starting a rebuilding array
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 12/12] imsm: write initial ppl on a disk added for rebuild
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 11/12] imsm: use correct map when validating ppl
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 09/12] imsm: Write empty PPL header if assembling regular clean array.
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 08/12] imsm: don't skip resync when an invalid ppl header is found
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 07/12] Grow: fix switching on PPL during recovery
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 06/12] imsm: switch to multiple ppls automatically during assemble
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 05/12] Zeroout whole ppl space during creation/force assemble
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 04/12] imsm: validate multiple ppls during assemble
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 03/12] imsm: Add support for multiple ppls
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 02/12] super1: Add support for multiple-ppls
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 01/12] Don't abort starting the array if kernel does not support ppl
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 00/12] Multiple PPL support and PPL bugfixes
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: What is the proper way to start an array with many failed (but good) disks
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: Is the LSI SAS9211-8i still the go to HBA?
  • From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
• Re: Is the LSI SAS9211-8i still the go to HBA?
  • From: Carsten Aulbert <carsten.aulbert@xxxxxxxxxx>
• Re: What is the proper way to start an array with many failed (but good) disks
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Is the LSI SAS9211-8i still the go to HBA?
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• What is the proper way to start an array with many failed (but good) disks
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: Need Help for Raid Recovery
  • From: Xuesong LU <disluxs@xxxxxxxxxx>
• Re: Resolved? ServeRAID-BR10i (LSI SAS1068E) strageness
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Resolved? ServeRAID-BR10i (LSI SAS1068E) strageness
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: [PATCH 0/3] md: retry bailed bio
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Can't mount /dev/md0 Raid5
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [mdadm PATCH] mdopen: call "modprobe md_mod" if it might be needed.
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [PATCH] dm-crypt: Fix memory leak in crypt_ctr_cipher_old()
  • From: Jeffy Chen <jeffy.chen@xxxxxxxxxxxxxx>
• Re: [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: [mdadm PATCH] mdopen: call "modprobe md_mod" if it might be needed.
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [mdadm PATCH] mdopen: call "modprobe md_mod" if it might be needed.
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [mdadm PATCH] mdopen: call "modprobe md_mod" if it might be needed.
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Hannes Reinecke <hare@xxxxxxx>
• Re: [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [mdadm PATCH] mdopen: call "modprobe md_mod" if it might be needed.
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [PATCH v3 1/6] md: Make md resync and reshape threads freezable
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: [PATCH v3 1/6] md: Make md resync and reshape threads freezable
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• [PATCH v4 1/7] md: Make md resync and reshape threads freezable
  • From: Bart Van Assche <bart.vanassche@xxxxxxx>
• Re: Need Help for Raid Recovery
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH v3 1/6] md: Make md resync and reshape threads freezable
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: [mdadm PATCH] mdopen: call "modprobe md_mod" if it might be needed.
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Need Help for Raid Recovery
  • From: Xuesong LU <disluxs@xxxxxxxxxx>
• [mdadm PATCH] mdopen: call "modprobe md_mod" if it might be needed.
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [PATCH v3 1/6] md: Make md resync and reshape threads freezable
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Re: possible HighPoint RocketRAID 2720SGL failure
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid recovery after unfinished shrink reshape
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: possible HighPoint RocketRAID 2720SGL failure
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: possible HighPoint RocketRAID 2720SGL failure
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: mdadm - raid6 best practices ?
  • From: Nikhil Kshirsagar <nkshirsa@xxxxxxxxxx>
• Re: mdadm - raid6 best practices ?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: possible HighPoint RocketRAID 2720SGL failure
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• [PATCH v3 1/6] md: Make md resync and reshape threads freezable
  • From: Bart Van Assche <bart.vanassche@xxxxxxx>
• Re: mdadm - raid6 best practices ?
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: mdadm - raid6 best practices ?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: mdadm - raid6 best practices ?
  • From: Song Liu <songliubraving@xxxxxx>
• Re: possible HighPoint RocketRAID 2720SGL failure
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Raid recovery after unfinished shrink reshape
  • From: Dan Porter <dpreid@xxxxxxxxx>
• Re: ServeRAID-BR10i (LSI SAS1068E) strageness
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Can't mount /dev/md0 Raid5
  • From: Joseba Ibarra <wajalotnet@xxxxxxxxx>
• Re: ServeRAID-BR10i (LSI SAS1068E) strageness
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: possible HighPoint RocketRAID 2720SGL failure
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• ServeRAID-BR10i (LSI SAS1068E) strageness
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• mdadm - raid6 best practices ?
  • From: Nikhil Kshirsagar <nkshirsa@xxxxxxxxxx>
• Re: possible HighPoint RocketRAID 2720SGL failure
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• [PATCH] md/raid5: cap worker count
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH 3/3] dm-raid: fix a race condition in request handling
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH 1/3] md: separate request handling
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH 2/3] md: fix a race condition for flush request handling
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH 0/3] md: retry bailed bio
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: raid1 IO hang - md_submit_flush_data ignores md_write_start return value
  • From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
• Re: Data recovery
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Data recovery
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Data recovery
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Data recovery
  • From: Vojtěch Kletečka <vojta.kletecka@xxxxxxxxx>
• Re: Data recovery
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Data recovery
  • From: Vojtěch Kletečka <vojta.kletecka@xxxxxxxxx>
• Re: possible HighPoint RocketRAID 2720SGL failure
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Data recovery
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [bug report] raid5: offload stripe handle to workqueue
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• possible HighPoint RocketRAID 2720SGL failure
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Re: Data recovery
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Data recovery
  • From: Vojtěch Kletečka <vojta.kletecka@xxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: raid1 IO hang - md_submit_flush_data ignores md_write_start return value
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• raid1 IO hang - md_submit_flush_data ignores md_write_start return value
  • From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
• [mdadm PATCH 1/1] Fix a build error
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [GIT PULL] MD update for 4.14-rc2
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [mdadm PATCH 1/1] Fix a building error
  • From: Paul Menzel <pmenzel@xxxxxxxxxxxxx>
• Re: [mdadm PATCH 1/1] Fix a building error
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [mdadm PATCH 1/1] Fix a building error
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [mdadm PATCH 1/1] Fix a building error
  • From: Paul Menzel <pmenzel@xxxxxxxxxxxxx>
• [mdadm PATCH 1/1] Fix a building error
  • From: Xiao Ni <xni@xxxxxxxxxx>
• does multipath of mdraid is still alive
  • From: tang tang <shenjietangtang@xxxxxxxxx>
• [MDADM PATCH 2/2] Give enough time to udev to handle events
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [MDADM PATCH 1/2] Close mdfd before returning main function
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [MDADM PATCH 0/2] /dev/md0 can't be released immediatly
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Linux Plumbers MD BOF discussion notes
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• does mdraid mulitpath is still alive
  • From: tang tang <shenjietangtang@xxxxxxxxx>
• Re: Linux Plumbers MD BOF discussion notes
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Linux Plumbers MD BOF discussion notes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 0/4] RFC: attempt to remove md deadlocks with metadata without
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Linux Plumbers MD BOF discussion notes
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Linux Plumbers MD BOF discussion notes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Linux Plumbers MD BOF discussion notes
  • From: Coly Li <colyli@xxxxxxx>
• Linux Plumbers MD BOF discussion notes
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Nix <nix@xxxxxxxxxxxxx>
• Oops with 4.12.6 while syncing and writing to array
  • From: Patrick Boettcher <patrick.boettcher@xxxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [PATCH 0/4] RFC: attempt to remove md deadlocks with metadata without
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH 0/4] RFC: attempt to remove md deadlocks with metadata without
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 0/4] RFC: attempt to remove md deadlocks with metadata without
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH 0/4] RFC: attempt to remove md deadlocks with metadata without
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: debian9/raid1 assembly/unexpected failure opening device
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/4] RFC: attempt to remove md deadlocks with metadata without
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [PATCH 0/4] RFC: attempt to remove md deadlocks with metadata without
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: debian9/raid1 assembly/unexpected failure opening device
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [PATCH 0/4] RFC: attempt to remove md deadlocks with metadata without
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [PATCH 4/4] md: allow metadata update while suspending.
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH 3/4] md: use mddev_suspend/resume instead of ->quiesce()
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH 2/4] md: don't call bitmap_create() while array is quiesced.
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH 1/4] md: always hold reconfig_mutex when calling mddev_suspend()
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH 0/4] RFC: attempt to remove md deadlocks with metadata without
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Stuck in md_write_start because MD_SB_CHANGE_PENDING can't be cleared
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Stuck in md_write_start because MD_SB_CHANGE_PENDING can't be cleared
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Stuck in md_write_start because MD_SB_CHANGE_PENDING can't be cleared
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: mismatch sector in range, kernel 4.13
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• Re: mismatch sector in range, kernel 4.13
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: mismatch sector in range, kernel 4.13
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• Re: mismatch sector in range, kernel 4.13
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: mismatch sector in range, kernel 4.13
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• Re: mismatch sector in range, kernel 4.13
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: mismatch sector in range, kernel 4.13
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: raid5 messed up
  • From: Weedy <weedy2887@xxxxxxxxx>
• BDI_CAP_STABLE_WRITES for stacked device (Re: Enable skip_copy can cause data integrity issue in some storage) stack
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: raid5 messed up
  • From: "Thomas C. Bishop" <bishop@xxxxxxxxxx>
• Re: raid5 messed up
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• [PATCH] imsm: New disk controller domains
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• Re: raid5 messed up
  • From: "Thomas C. Bishop" <bishop@xxxxxxxxxx>
• [PATCH] Grow: stop previous reshape process first
  • From: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx>
• Re: [PATCH 06/14] md/bcache: Use %pS printk format for direct addresses
  • From: Sergey Senozhatsky <sergey.senozhatsky.work@xxxxxxxxx>
• Re: [PATCH 06/14] md/bcache: Use %pS printk format for direct addresses
  • From: Coly Li <i@xxxxxxx>
• Re: [PATCH 06/14] md/bcache: Use %pS printk format for direct addresses
  • From: Helge Deller <deller@xxxxxx>
• Re: Stuck in md_write_start because MD_SB_CHANGE_PENDING can't be cleared
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 06/14] md/bcache: Use %pS printk format for direct addresses
  • From: Coly Li <i@xxxxxxx>
• Re: Stuck in md_write_start because MD_SB_CHANGE_PENDING can't be cleared
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Enable skip_copy can cause data integrity issue in some storage stack
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: raid5 messed up
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: raid5 messed up
  • From: "Thomas C. Bishop" <bishop@xxxxxxxxxx>
• Re: raid5 messed up
  • From: "Thomas C. Bishop" <bishop@xxxxxxxxxx>
• [GIT PULL] MD update for 4.14-rc1
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH 06/14] md/bcache: Use %pS printk format for direct addresses
  • From: Helge Deller <deller@xxxxxx>
• Re: Enable skip_copy can cause data integrity issue in some storage stack
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH v2] md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
  • From: Dennis Yang <dennisyang@xxxxxxxx>
• Re: Superblock Missing
  • From: David Mitchell <mr.david.mitchell@xxxxxxxxx>
• [PATCH v2] md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
  • From: Dennis Yang <dennisyang@xxxxxxxx>
• Re: [PATCH] md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH] md/raid5: fix a race condition in stripe batch
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: BUG_ON(sh->batch_head) in init_stripe()
  • From: Stephane Thiell <sthiell@xxxxxxxxxxxx>
• [PATCH v8 00/20] simplify crypto wait for async op
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 03/20] net: use -EAGAIN for transient busy indication
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 06/20] crypto: introduce crypto wait for async op
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 08/20] crypto: move pub key to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 09/20] crypto: move drbg to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 11/20] crypto: move testmgr to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 12/20] fscrypt: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 13/20] dm: move dm-verity to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 14/20] cifs: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 15/20] ima: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 16/20] crypto: tcrypt: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 17/20] crypto: talitos: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 20/20] crypto: adapt api sample to use async. op wait
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 19/20] crypto: mediatek: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 18/20] crypto: qce: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 10/20] crypto: move gcm to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 07/20] crypto: move algif to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 05/20] crypto: marvell/cesa: remove redundant backlog checks on EBUSY
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 04/20] crypto: remove redundant backlog checks on EBUSY
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 02/20] crypto: ccp: use -EAGAIN for transient busy indication
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v8 01/20] crypto: change transient busy return code to -EAGAIN
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: [PATCH v7 00/19] simplify crypto wait for async op
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: [PATCH v7 00/19] simplify crypto wait for async op
  • From: Harsh Jain <harshjain.prof@xxxxxxxxx>
• [PATCH 3/3] mdadm: fixes some trivial typos in comments
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• [PATCH 2/3] mdadm/manpage: disable bitmap_resize for external file bitmap
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• [PATCH 1/3] mdadm/grow: Component size must be larger than chunk size
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• [PATCH 0/3] mdadm patches for some trivial fixes
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• Re: mismatch sector in range, kernel 4.13
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: raid5 messed up
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: mismatch sector in range, kernel 4.13
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: future of raid 6
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH] md: allow changing set_name of running array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH v4] bcache: Don't reinvent the wheel but use existing llist API
  • From: Coly Li <colyli@xxxxxxx>
• Re: [PATCH v4] bcache: Don't reinvent the wheel but use existing llist API
  • From: Byungchul Park <byungchul.park@xxxxxxx>
• Re: Stuck in md_write_start because MD_SB_CHANGE_PENDING can't be cleared
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Stuck in md_write_start because MD_SB_CHANGE_PENDING can't be cleared
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] md: allow changing set_name of running array
  • From: NeilBrown <neilb@xxxxxxxx>
• mismatch sector in range, kernel 4.13
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Oops on raid10 resync on v4.12.2
  • From: Petr Janecek <janecek@xxxxxx>
• Re: [PATCH] md: allow changing set_name of running array
  • From: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
• Re: Superblock Missing
  • From: David Mitchell <mr.david.mitchell@xxxxxxxxx>
• Re: Superblock Missing
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Superblock Missing
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: future of raid 6
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• [PATCH] Monitor: Check redundancy for arrays
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• Re: future of raid 6
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Stuck in md_write_start because MD_SB_CHANGE_PENDING can't be cleared
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Stuck in md_write_start because MD_SB_CHANGE_PENDING can't be cleared
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Stuck in md_write_start because MD_SB_CHANGE_PENDING can't be cleared
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Superblock Missing
  • From: David Mitchell <mr.david.mitchell@xxxxxxxxx>
• Re: Stuck in md_write_start because MD_SB_CHANGE_PENDING can't be cleared
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH] md: allow changing set_name of running array
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Stuck in md_write_start because MD_SB_CHANGE_PENDING can't be cleared
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: future of raid 6
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• Re: future of raid 6
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• future of raid 6
  • From: Markus <M4rkusXXL@xxxxxx>
• Re: [PATCH v7 00/19] simplify crypto wait for async op
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: Superblock Missing
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Superblock Missing
  • From: David Mitchell <mr.david.mitchell@xxxxxxxxx>
• Stuck in md_write_start because MD_SB_CHANGE_PENDING can't be cleared
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Superblock Missing
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Superblock Missing
  • From: David Mitchell <mr.david.mitchell@xxxxxxxxx>
• Re: raid5 messed up
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: raid5 messed up
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• raid5 messed up
  • From: "Thomas C. Bishop" <bishop@xxxxxxxxxx>
• Re: [PATCH] md: allow changing set_name of running array
  • From: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
• Re: [PATCH 5/5] mdadm/test: add new testcase for testing readonly/readwrite
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 4/5] mdadm/test: get rid of tests/check
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 3/5] mdadm/test: get rid of the tests/testdev
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 2/5] mdadm/test: use the first element of array as parsing condition
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 1/5] mdadm/bitmap: examine-bitmap failed when bitmap is external mode
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH v2] mdadm: set journal_clean after scanning all disks
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 2/2] mdadm: remove journal with "remove-journal"
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• Re: report a bug that panic when grow size for external bitmap
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• Re: Encrypted software RAID1 with Debian Stretch
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
  • From: Dennis Yang <dennisyang@xxxxxxxx>
• tests/21raid5cache: tasks blocked for more than 480 seconds
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• Enable skip_copy can cause data integrity issue in some storage stack
  • From: alexwu <alexwu@xxxxxxxxxxxx>
• Re: [PATCH] md/bitmap: disable bitmap_resize for file-backed bitmaps.
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: [PATCH] md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: The dev node can't be released at once after stopping raid
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: The dev node can't be released at once after stopping raid
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH] mdadm: handle super == NULL case in avail_size1
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] md: allow changing set_name of running array
  • From: NeilBrown <neilb@xxxxxxxx>
• Encrypted software RAID1 with Debian Stretch
  • From: commentsabout@xxxxxxxxxx
• Re: [PATCH] mdadm: handle super == NULL case in avail_size1
  • From: Song Liu <songliubraving@xxxxxx>
• Re: The dev node can't be released at once after stopping raid
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] mdadm: handle super == NULL case in avail_size1
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] mdadm: remove journal with "remove-journal"
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH] mdadm: handle super == NULL case in avail_size1
  • From: Song Liu <songliubraving@xxxxxx>
• Re: debian9/raid1 assembly/unexpected failure opening device
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: debian9/raid1 assembly/unexpected failure opening device
  • From: Joel Walberg <joel.walberg@xxxxxxxxx>
• Re: debian9/raid1 assembly/unexpected failure opening device
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: debian9/raid1 assembly/unexpected failure opening device
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: debian9/raid1 assembly/unexpected failure opening device
  • From: Joel Walberg <joel.walberg@xxxxxxxxx>
• Re: debian9/raid1 assembly/unexpected failure opening device
  • From: Joel Walberg <joel.walberg@xxxxxxxxx>
• Re: debian9/raid1 assembly/unexpected failure opening device
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: [PATCH v7 00/19] simplify crypto wait for async op
  • From: Harsh Jain <harshjain.prof@xxxxxxxxx>
• debian9/raid1 assembly/unexpected failure opening device
  • From: Joel Walberg <joel.walberg@xxxxxxxxx>
• Re: The dev node can't be released at once after stopping raid
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: The dev node can't be released at once after stopping raid
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: The dev node can't be released at once after stopping raid
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: The dev node can't be released at once after stopping raid
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: The dev node can't be released at once after stopping raid
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: report a bug that panic when grow size for external bitmap
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: report a bug that panic when grow size for external bitmap
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• Re: report a bug that panic when grow size for external bitmap
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH] md/bitmap: disable bitmap_resize for file-backed bitmaps.
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 2/2] mdadm: remove journal with "remove-journal"
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: oleksandr@xxxxxxxxxxxxxx
• Re: [PATCH -v4 1/1] mdadm/test: Add one test case for raid5 reshape
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• Re: [PATCH -v4 1/1] mdadm/test: Add one test case for raid5 reshape
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: oleksandr@xxxxxxxxxxxxxx
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: report a bug that panic when grow size for external bitmap
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• Re: report a bug that panic when grow size for external bitmap
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: report a bug that panic when grow size for external bitmap
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• [PATCH] md: allow changing set_name of running array
  • From: Michał Mirosław <mirq-linux@xxxxxxxxxxxx>
• Re: [PATCH v2] mdadm: set journal_clean after scanning all disks
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 0/2] mdadm patches for r5cache and mdadm.spec
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [PATCH v2] mdadm: set journal_clean after scanning all disks
  • From: Song Liu <songliubraving@xxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Oleksandr Natalenko <oleksandr@xxxxxxxxxxxxxx>
• Re: report a bug that panic when grow size for external bitmap
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: report a bug that panic when grow size for external bitmap
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• Re: report a bug that panic when grow size for external bitmap
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: report a bug that panic when grow size for external bitmap
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• Re: [PATCH 2/2] mdadm: save previous journal_clean when reload super
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• [PATCH 0/2] mdadm patches for r5cache and mdadm.spec
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 2/2] mdadm: save previous journal_clean when reload super
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 1/2] mdadm: install two more udev rules in mdadm.spec
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH -v4 1/1] mdadm/test: Add one test case for raid5 reshape
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Oleksandr Natalenko <oleksandr@xxxxxxxxxxxxxx>
• Re: [PATCH 0/2] md: Add support for Multiple PPLs
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• [PATCH] md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
  • From: Dennis Yang <dennisyang@xxxxxxxx>
• report a bug that panic when grow size for external bitmap
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• Re: [PATCH -v4 1/1] mdadm/test: Add one test case for raid5 reshape
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• [PATCH 5/5] mdadm/test: add new testcase for testing readonly/readwrite
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• [PATCH 4/5] mdadm/test: get rid of tests/check
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• [PATCH 3/5] mdadm/test: get rid of the tests/testdev
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• [PATCH 0/5] mdadm/test: Update for mdadm test part
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• [PATCH 1/5] mdadm/bitmap: examine-bitmap failed when bitmap is external mode
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• [PATCH 2/5] mdadm/test: use the first element of array as parsing condition
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• raid5_finish_reshape is stuck at revalidate_disk
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH 0/2] md: Add support for Multiple PPLs
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• occasional hard lockup on raid on nvme disks (fio processes hung)
  • From: Nikhil Kshirsagar <nkshirsa@xxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Oleksandr Natalenko <oleksandr@xxxxxxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Oleksandr Natalenko <oleksandr@xxxxxxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Martin Steigerwald <martin@xxxxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Oleksandr Natalenko <oleksandr@xxxxxxxxxxxxxx>
• Re: I/O hangs after resuming from suspend-to-ram
  • From: Oleksandr Natalenko <oleksandr@xxxxxxxxxxxxxx>
• Re: [PATCH 0/2] md: Add support for Multiple PPLs
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 0/2] md: Add support for Multiple PPLs
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• RE: force raid reassembly
  • From: Bryan Hepworth <bryan.hepworth@xxxxxxxxxxxxxxx>
• [PATCH] md/raid1/10: reset bio allocated from mempool
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md/raid5: release/flush io in raid5_do_work()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH] md/raid5: release/flush io in raid5_do_work()
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH v7 00/19] simplify crypto wait for async op
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 02/19] crypto: ccp: use -EAGAIN for transient busy indication
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 03/19] crypto: remove redundant backlog checks on EBUSY
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 04/19] crypto: marvell/cesa: remove redundant backlog checks on EBUSY
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 06/19] crypto: move algif to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 07/19] crypto: move pub key to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 08/19] crypto: move drbg to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 09/19] crypto: move gcm to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 10/19] crypto: move testmgr to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 12/19] dm: move dm-verity to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 13/19] cifs: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 14/19] ima: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 15/19] crypto: tcrypt: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 16/19] crypto: talitos: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 17/19] crypto: qce: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 19/19] crypto: adapt api sample to use async. op wait
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 18/19] crypto: mediatek: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 11/19] fscrypt: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 05/19] crypto: introduce crypto wait for async op
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v7 01/19] crypto: change transient busy return code to -EAGAIN
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: [PATCH v6 04/19] crypto: marvell/cesa: remove redundant backlog checks on EBUSY
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: [PATCH v6 04/19] crypto: marvell/cesa: remove redundant backlog checks on EBUSY
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH 2/6] raid5: remove a call to get_start_sect
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: don't require a struct block_device to submit a bio
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/6] btrfs: index check-integrity state hash by a dev_t
  • From: Liu Bo <bo.li.liu@xxxxxxxxxx>
• Re: [PATCH 2/6] raid5: remove a call to get_start_sect
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: don't require a struct block_device to submit a bio
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: don't require a struct block_device to submit a bio
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] Detail: differentiate between container and inactive arrays
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [PATCH 1/6] btrfs: index check-integrity state hash by a dev_t
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 4/6] block: add a __disk_get_part helper
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 3/6] block: reject attempts to allocate more than DISK_MAX_PARTS partitions
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 5/6] block: cache the partition index in struct block_device
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 2/6] raid5: remove a call to get_start_sect
  • From: Christoph Hellwig <hch@xxxxxx>
• don't require a struct block_device to submit a bio
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH V2 0/9] nullb: extend nullb for destructive tests
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Soft/Hard lockup detected in raid5_unplug() when doing heavy I/O on RAID6
  • From: Dennis Yang <shinrairis@xxxxxxxxx>
• I/O hangs after resuming from suspend-to-ram
  • From: Oleksandr Natalenko <oleksandr@xxxxxxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: BUG_ON(sh->batch_head) in init_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: BUG_ON(sh->batch_head) in init_stripe()
  • From: Stephane Thiell <sthiell@xxxxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Warning in raid5-cache.c with NVME journal and DM_MQ_DEFAULT
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 0/2] md: Add support for Multiple PPLs
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 2/2] dm integrity: use init_completion instead of COMPLETION_INITIALIZER_ONSTACK
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: BUG_ON(sh->batch_head) in init_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 0/2] md: Add support for Multiple PPLs
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH v6 00/19] simplify crypto wait for async op
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 01/19] crypto: change transient busy return code to -EAGAIN
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 02/19] crypto: ccp: use -EAGAIN for transient busy indication
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 03/19] crypto: remove redundant backlog checks on EBUSY
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 04/19] crypto: marvell/cesa: remove redundant backlog checks on EBUSY
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 06/19] crypto: move algif to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 05/19] crypto: introduce crypto wait for async op
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 07/19] crypto: move pub key to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 08/19] crypto: move drbg to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 10/19] crypto: move testmgr to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 09/19] crypto: move gcm to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 12/19] dm: move dm-verity to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 13/19] cifs: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 16/19] crypto: talitos: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 18/19] crypto: mediatek: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 19/19] crypto: adapt api sample to use async. op wait
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• [PATCH v6 17/19] crypto: qce: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 15/19] crypto: tcrypt: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 14/19] ima: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v6 11/19] fscrypt: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH v5 05/19] crypto: introduce crypto wait for async op
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH v5 12/19] dm: move dm-verity to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [dm-devel] [PATCH v5 12/19] dm: move dm-verity to generic async completion
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Warning in raid5-cache.c with NVME journal and DM_MQ_DEFAULT
  • From: Vasco Steinmetz <linux@xxxxxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• [PATCH] md/raid0: attach correct cgroup info in bio
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH] md/raid0: attach correct cgroup info in bio
  • From: Shaohua Li <shli@xxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• [PATCH] Detail: differentiate between container and inactive arrays
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• Re: [PATCH v4] bcache: Don't reinvent the wheel but use existing llist API
  • From: Byungchul Park <byungchul.park@xxxxxxx>
• Re: [PATCH v4] bcache: Don't reinvent the wheel but use existing llist API
  • From: Coly Li <i@xxxxxxx>
• Re: BUG_ON(sh->batch_head) in init_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: BUG_ON(sh->batch_head) in init_stripe()
  • From: Stephane Thiell <sthiell@xxxxxxxxxxxx>
• Re: [PATCH v4] bcache: Don't reinvent the wheel but use existing llist API
  • From: Byungchul Park <byungchul.park@xxxxxxx>
• Re: BUG_ON(sh->batch_head) in init_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: [PATCH 0/2] md: Add support for Multiple PPLs
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Filesystem corruption on RAID1
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• [PATCH 2/2] tests/20raid5journal: fix test_incremental
  • From: Chen Rong <rongx.a.chen@xxxxxxxxx>
• [PATCH 1/2] incremental: fix check journal device
  • From: Chen Rong <rongx.a.chen@xxxxxxxxx>
• Re: Sanity Check: RAID1 with 4 members + Spare
  • From: Benjammin2068 <benjammin2068@xxxxxxxxx>
• Sanity Check: RAID1 with 4 members + Spare
  • From: Benjammin2068 <benjammin2068@xxxxxxxxx>
• Re: [PATCH 0/4] Assorted mdadm patches.
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH V2 8/9] nullb: emulate cache
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH 2/2] dm integrity: use init_completion instead of COMPLETION_INITIALIZER_ONSTACK
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH 2/2] raid5-ppl: Recovery support for multiple partial parity logs
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 1/2] md: Runtime support for multiple ppls
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 0/2] md: Add support for Multiple PPLs
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: [PATCH v2] Monitor: Include containers in spare migration
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [PATCH v2] Monitor: Include containers in spare migration
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• Re: [PATCH v3] Monitor: containers don't have the same sysfs properties as arrays
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [PATCH v3] Monitor: containers don't have the same sysfs properties as arrays
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• Re: [PATCH v2] Monitor: containers don't have the same sysfs properties as arrays
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 0/4] Assorted mdadm patches.
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] imsm: rebuild from 2-disk RAID10
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] Detail: correct output for active arrays
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: BUG_ON(sh->batch_head) in init_stripe()
  • From: Stephane Thiell <sthiell@xxxxxxxxxxxx>
• Re: BUG_ON(sh->batch_head) in init_stripe()
  • From: Stephane Thiell <sthiell@xxxxxxxxxxxx>
• Re: BUG_ON(sh->batch_head) in init_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: BUG_ON(sh->batch_head) in init_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: BUG_ON(sh->batch_head) in init_stripe()
  • From: Stephane Thiell <sthiell@xxxxxxxxxxxx>
• Re: [GIT PULL] MD update for 4.13-rc5
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Unable to remove write journal device
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• [PATCH 2/2] dm integrity: use init_completion instead of COMPLETION_INITIALIZER_ONSTACK
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: BUG_ON(sh->batch_head) in init_stripe()
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH v5 04/19] crypto: marvell/cesa: remove redundant backlog checks on EBUSY
  • From: Boris Brezillon <boris.brezillon@xxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL] MD update for 4.13-rc5
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: [PATCH v5 18/19] crypto: mediatek: move to generic async completion
  • From: Ryder Lee <ryder.lee@xxxxxxxxxxxx>
• Re: [PATCH v5 05/19] crypto: introduce crypto wait for async op
  • From: Jonathan Cameron <Jonathan.Cameron@xxxxxxxxxx>
• [PATCH V2 3/9] nullb: add interface to power on disk
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH V2 1/9] nullb: factor disk parameters
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH V2 2/9] nullb: add configfs interface
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH V2 9/9] nullb: badbblocks support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH V2 8/9] nullb: emulate cache
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH V2 5/9] nullb: support memory backed store
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH V2 7/9] nullb: bandwidth control
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH V2 6/9] nullb: support discard
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH V2 4/9] nullb: use ida to manage index
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH V2 0/9] nullb: extend nullb for destructive tests
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH v5 02/19] crypto: ccp: use -EAGAIN for transient busy indication
  • From: Gary R Hook <gary.hook@xxxxxxx>
• [GIT PULL] MD update for 4.13-rc5
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] raid5: remove raid5_build_block
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH v5 00/19] simplify crypto wait for async op
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 02/19] crypto: ccp: use -EAGAIN for transient busy indication
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 06/19] crypto: move algif to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 04/19] crypto: marvell/cesa: remove redundant backlog checks on EBUSY
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 03/19] crypto: remove redundant backlog checks on EBUSY
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 05/19] crypto: introduce crypto wait for async op
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 08/19] crypto: move drbg to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 09/19] crypto: move gcm to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 11/19] fscrypt: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 10/19] crypto: move testmgr to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 13/19] cifs: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 14/19] ima: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 16/19] crypto: talitos: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 17/19] crypto: qce: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 18/19] crypto: mediatek: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 19/19] crypto: adapt api sample to use async. op wait
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 15/19] crypto: tcrypt: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 12/19] dm: move dm-verity to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 07/19] crypto: move pub key to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v5 01/19] crypto: change transient busy return code to -EAGAIN
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: raid1 lockups on 4.12.x
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: raid1 lockups on 4.12.x
  • From: Simon Kirby <sim@xxxxxxxxxx>
• Re: mdadm will only start root device degraded
  • From: Felix Koop <fdp@xxxxxxxx>
• Re: [PATCH] MD: not clear ->safemode for external metadata array
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: BUG_ON(sh->batch_head) in init_stripe()
  • From: Stephane Thiell <sthiell@xxxxxxxxxxxx>
• mpt3sas + raid10 kicked drives at reboot
  • From: Sarah Newman <srn@xxxxxxxxx>
• Re: force raid reassembly
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• Re: mdadm will only start root device degraded
  • From: Anthony Youngman <antlists@xxxxxxxxxxxxxxx>
• Re: mdadm will only start root device degraded
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: mdadm will only start root device degraded
  • From: Felix Koop <fdp@xxxxxxxx>
• [PATCH] MD: not clear ->safemode for external metadata array
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: mdadm will only start root device degraded
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• [PATCH v4] bcache: Don't reinvent the wheel but use existing llist API
  • From: Byungchul Park <byungchul.park@xxxxxxx>
• Re: md0 device gone, disks busy
  • From: Sarah Newman <srn@xxxxxxxxx>
• md0 device gone, disks busy
  • From: Mr Typo <euroregistrar@xxxxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• migrate from mdadm to HW RAID
  • From: David Zampirolo <davidzampirolo@xxxxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] imsm: rebuild from 2-disk RAID10
  • From: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx>
• Re: [PATCH] mdadm: allow to assemble /dev/md_xxx named arrays.
  • From: Coly Li <colyli@xxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH] Detail: correct output for active arrays
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• [PATCH v2] mdadm: allow to assemble /dev/md_xxx named arrays.
  • From: jcejka@xxxxxxxx
• [PATCH v2] mdopen: prevent named arrays devices from buffer overflow
  • From: jcejka@xxxxxxxx
• [PATCH] raid5: remove raid5_build_block
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 0/2] md/raid6: improvements for ARM/arm64
  • From: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
• Re: [PATCH 0/2] md/raid6: improvements for ARM/arm64
  • From: Catalin Marinas <catalin.marinas@xxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 4/9] md: raid5 nowait support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 3/9] md: raid1 nowait support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: force raid reassembly
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• RE: force raid reassembly
  • From: Bryan Hepworth <bryan.hepworth@xxxxxxxxxxxxxxx>
• Re: [RESEND PATCH] bcache: Don't reinvent the wheel but use existing llist API
  • From: Byungchul Park <byungchul.park@xxxxxxx>
• Re: [RESEND PATCH] bcache: Don't reinvent the wheel but use existing llist API
  • From: Nikolay Borisov <nborisov@xxxxxxxx>
• Re: [MD] Crash with 4.12+ kernel and high disk load -- bisected to 4ad23a976413: MD: use per-cpu counter for writes_pending
  • From: David R <david@xxxxxxxxxxxxxxx>
• [PATCH v2] md/r5cache: call mddev_lock/unlock() in r5c_journal_mode_show
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH v4 02/19] crypto: ccm: use -EAGAIN for transient busy indication
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: [PATCH] Assemble: prevent segfault with faulty "best" devices
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH] md/r5cache: call mddev_lock/unlock() in r5c_journal_mode_show
  • From: Song Liu <songliubraving@xxxxxx>
• Re: force raid reassembly
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• force raid reassembly
  • From: Bryan Hepworth <bryan.hepworth@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/5] block: a virtual block device driver for testing
  • From: Omar Sandoval <osandov@xxxxxxxxxxx>
• Re: [PATCH 0/5] block: a virtual block device driver for testing
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 0/5] block: a virtual block device driver for testing
  • From: Bart Van Assche <Bart.VanAssche@xxxxxxx>
• Re: [PATCH 0/5] block: a virtual block device driver for testing
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 0/5] block: a virtual block device driver for testing
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 4/9] md: raid5 nowait support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 5/9] md: raid10 nowait support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 3/9] md: raid1 nowait support
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH v2] md/bitmap: preserve whole sb_page when initializing bitmap
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 2/5] testb: implement block device operations
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 2/9] md: Add nowait support to md
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 1/9] QUEUE_FLAG_NOWAIT to indicate device supports nowait
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 0/5] block: a virtual block device driver for testing
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: RecovData Handshk error
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] md/bitmap: preserve whole sb_page when initializing bitmap
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH] Assemble: prevent segfault with faulty "best" devices
  • From: Andrea Righi <righi.andrea@xxxxxxxxx>
• Re: [PATCH] md/bitmap: preserve whole sb_page when initializing bitmap
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH v4 02/19] crypto: ccm: use -EAGAIN for transient busy indication
  • From: Gary R Hook <gary.hook@xxxxxxx>
• Re: [md PATCH 1/2] md: always clear ->safemode when md_check_recovery gets the mddev lock.
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH v4 06/19] crypto: move algif to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 00/19] simplify crypto wait for async op
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 01/19] crypto: change transient busy return code to -EAGAIN
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 02/19] crypto: ccm: use -EAGAIN for transient busy indication
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 03/19] crypto: remove redundant backlog checks on EBUSY
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 04/19] crypto: marvell/cesa: remove redundant backlog checks on EBUSY
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 06/19] crypto: move algif to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 09/19] crypto: move gcm to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 07/19] crypto: move pub key to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 10/19] crypto: move testmgr to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 13/19] cifs: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 14/19] ima: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 16/19] crypto: talitos: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 15/19] crypto: tcrypt: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 19/19] crypto: adapt api sample to use async. op wait
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 18/19] crypto: mediatek: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 17/19] crypto: qce: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 12/19] dm: move dm-verity to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 11/19] fscrypt: move to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 08/19] crypto: move drbg to generic async completion
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• [PATCH v4 05/19] crypto: introduce crypto wait for async op
  • From: Gilad Ben-Yossef <gilad@xxxxxxxxxxxxx>
• Re: [MD] Crash with 4.12+ kernel and high disk load -- bisected to 4ad23a976413: MD: use per-cpu counter for writes_pending
  • From: Dominik Brodowski <linux@xxxxxxxxxxxxxxxxxxxx>
• [PATCH v3 34/49] md: raid1: convert to bio_for_each_segment_all_sp()
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [MD] Crash with 4.12+ kernel and high disk load -- bisected to 4ad23a976413: MD: use per-cpu counter for writes_pending
  • From: David R <david@xxxxxxxxxxxxxxx>
• Re: [MD] Crash with 4.12+ kernel and high disk load -- bisected to 4ad23a976413: MD: use per-cpu counter for writes_pending
  • From: Dominik Brodowski <linux@xxxxxxxxxxxxxxxxxxxx>
• Re: [MD] Crash with 4.12+ kernel and high disk load -- bisected to 4ad23a976413: MD: use per-cpu counter for writes_pending
  • From: Dominik Brodowski <linux@xxxxxxxxxxxxxxxxxxxx>
• Re: [MD] Crash with 4.12+ kernel and high disk load -- bisected to 4ad23a976413: MD: use per-cpu counter for writes_pending
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [MD] Crash with 4.12+ kernel and high disk load -- bisected to 4ad23a976413: MD: use per-cpu counter for writes_pending
  • From: David R <david@xxxxxxxxxxxxxxx>
• Re: [MD] Crash with 4.12+ kernel and high disk load -- bisected to 4ad23a976413: MD: use per-cpu counter for writes_pending
  • From: NeilBrown <neilb@xxxxxxxx>
• [md PATCH 2/2] md: fix test in md_write_start()
  • From: NeilBrown <neilb@xxxxxxxx>
• [md PATCH 1/2] md: always clear ->safemode when md_check_recovery gets the mddev lock.
  • From: NeilBrown <neilb@xxxxxxxx>
• [md PATCH 0/2] Fix two bug in the new write_pending counting.
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [MD] Crash with 4.12+ kernel and high disk load -- bisected to 4ad23a976413: MD: use per-cpu counter for writes_pending
  • From: David R <david@xxxxxxxxxxxxxxx>
• Re: [RESEND PATCH] bcache: Don't reinvent the wheel but use existing llist API
  • From: Coly Li <i@xxxxxxx>
• Re: [RESEND PATCH] bcache: Don't reinvent the wheel but use existing llist API
  • From: Byungchul Park <byungchul.park@xxxxxxx>
• Re: [RESEND PATCH] bcache: Don't reinvent the wheel but use existing llist API
  • From: Coly Li <i@xxxxxxx>
• Re: [MD] Crash with 4.12+ kernel and high disk load -- bisected to 4ad23a976413: MD: use per-cpu counter for writes_pending
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [RESEND PATCH] bcache: Don't reinvent the wheel but use existing llist API
  • From: Byungchul Park <byungchul.park@xxxxxxx>