Linux RAID Storage Date Index

• Thread Index

• Re: [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Start reshape failed
  • From: Kev Dorman <kdorman036@xxxxxxxxx>
• Re: [PATCH] drivers: md: use ktime_get_real_seconds()
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] md: avoid warning for 32-bit sector_t
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] raid5-cache: add journal hot add/remove support
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH v2 0/2] Introduce the bulk IV mode for improving the crypto engine efficiency
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH v2 1/2] block: Export the __blk_bios_map_sg() to map one bio
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH v2 2/2] md: dm-crypt: Introduce the bulk IV mode for bulk crypto
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 4/4] mdadm: do not display bitmap info if it is cleared
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 00/17] mdadm: SCSI enclosure based array
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v2 0/2] mdadm: re-add journal to array with bad journal
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] raid5-cache: add journal hot add/remove support
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH] md/raid10: fix data corruption and crash during resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] raid5-cache: add journal hot add/remove support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: core dump on initial sync of raid10 please help
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: Mdadm with data offsets
  • From: "TheGerwazy ." <gerardlesiuk@xxxxxxxxx>
• Re: RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• RE: best base / worst case RAID 5,6 write speeds
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mdadm with data offsets
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: Mdadm with data offsets
  • From: "TheGerwazy ." <gerardlesiuk@xxxxxxxxx>
• Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [PATCH] raid5-cache: add journal hot add/remove support
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• [PATCH v2 2/2] [mdadm] recreate journal in mdadm
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH v2 1/2] add sysfs_array_state to struct mdinfo
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH v2 0/2] mdadm: re-add journal to array with bad journal
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Tommy Apel <tommyapeldk@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [PATCH 1/2] raid5-cache: use a bio_set
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: core dump on initial sync of raid10 please help
  • From: "Micheal Blue" <mblue@xxxxxx>
• Re: [PATCH] md/raid10: fix data corruption and crash during resync
  • From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
• core dump on initial sync of raid10 please help
  • From: "Micheal Blue" <mblue@xxxxxx>
• Re: Mdadm with data offsets
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mdadm with data offsets
  • From: "TheGerwazy ." <gerardlesiuk@xxxxxxxxx>
• [PATCH 0/2] Optimize the dm-crypt for XTS mode
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH 1/2] block: Export the __blk_bios_map_sg() to map one bio
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH 2/2] md: dm-crypt: Optimize the dm-crypt for XTS mode
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: Mdadm with data offsets
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mdadm with data offsets
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Seeking advice to convert RAID5 to RAID10 adding a drive in the process
  • From: "Micheal Blue" <mblue@xxxxxx>
• Mdadm with data offsets
  • From: "TheGerwazy ." <gerardlesiuk@xxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: Reshape stalls and fails when SELinux is enabled
  • From: Enrico Tagliavini <enrico.tagliavini@xxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH v4 0/3] Badblock tracking for gendisks
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Reshape stalls and fails when SELinux is enabled
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: Shaohua Li <shli@xxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: Shaohua Li <shli@xxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• RE: [PATCH 0/3] mdadm: re-add journal to array with bad journal
  • From: Song Liu <songliubraving@xxxxxx>
• Re: RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Re: [PATCH 0/3] mdadm: re-add journal to array with bad journal
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: Reshape stalls and fails when SELinux is enabled
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Reshape stalls and fails when SELinux is enabled
  • From: Edward Kuns <eddie.kuns@xxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: start dm-multipath before mdadm raid
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• start dm-multipath before mdadm raid
  • From: "P. Remek" <p.remek1@xxxxxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: Reshape stalls and fails when SELinux is enabled
  • From: Enrico Tagliavini <enrico.tagliavini@xxxxxxxxx>
• Re: RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: best base / worst case RAID 5,6 write speeds
  • From: Alexander Afonyashin <a.afonyashin@xxxxxxxxxxxxxx>
• best base / worst case RAID 5,6 write speeds
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• RAID 6 "Failed to restore critical section for reshape, sorry." - recovery advice?
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Unable to (un)-grow raid6
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: Shaohua Li <shli@xxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH 2/2] raid5-cache: use a mempool for the metadata block
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 1/2] raid5-cache: use a bio_set
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: two small raid5 cache updates
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v4 0/3] Badblock tracking for gendisks
  • From: Finn Thain <fthain@xxxxxxxxxxxxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 2/2] md: update comment for md_allow_write
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 1/2] md-cluster: update comments for MD_CLUSTER_SEND_LOCKED_ALREADY
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 1/2] [mdadm] fix bug in assemble
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v4 0/3] Badblock tracking for gendisks
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Help Reassembling a raid5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• [PATCH v4 3/3] md: convert to use the generic badblocks code
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v4 2/3] block: Add badblock management for gendisks
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v4 1/3] badblocks: Add core badblock management code
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v4 0/3] Badblock tracking for gendisks
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• Re: dm verity: use sector_div for division
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm verity: use sector_div for division
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: I/O errors without erros from underlying device
  • From: Arkadiusz Miskiewicz <a.miskiewicz@xxxxxxxxx>
• Re: Help Reassembling a raid5 array
  • From: Andrew Wilkins <andrew.m.wilkins@xxxxxxxxx>
• Re: I/O errors without erros from underlying device
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Help Reassembling a raid5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH v2 0/3] Badblock tracking for gendisks
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• [PATCH v2 3/3] md: convert to use the generic badblocks code
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v2 2/3] block: Add badblock management for gendisks
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v2 0/3] Badblock tracking for gendisks
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• Help Reassembling a raid5 array
  • From: Andrew Wilkins <andrew.m.wilkins@xxxxxxxxx>
• RE: [PATCH 1/2] [mdadm] fix bug in assemble
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 1/2] [mdadm] fix bug in assemble
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH v2 01/18] block_dev: Support checking inode permissions in lookup_bdev()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 00/19] Support fuse mounts in user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 02/18] block_dev: Check permissions towards block device inode when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 05/18] userns: Replace in_userns with current_in_userns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 03/18] fs: Treat foreign mounts as nosuid
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 06/18] Smack: Handle labels consistently in untrusted mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 08/18] cred: Reject inodes with invalid ids in set_create_file_as()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 09/18] fs: Refuse uid/gid changes which don't map into s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 07/18] fs: Check for invalid i_uid in may_follow_link()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 10/18] fs: Update posix_acl support to handle user namespace mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 12/18] fs: Don't remove suid for CAP_FSETID in s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 14/18] capabilities: Allow privileged user in s_user_ns to set security.* xattrs
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 18/18] fuse: Allow user namespace mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 17/18] fuse: Restrict allow_other to the superblock's namespace or a descendant
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 16/18] fuse: Support fuse filesystems outside of init_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 15/18] fuse: Add support for pid namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 13/18] fs: Allow superblock owner to access do_remount_sb()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v2 04/18] selinux: Add support for unprivileged mounts from user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: I/O errors without erros from underlying device
  • From: Arkadiusz Miskiewicz <a.miskiewicz@xxxxxxxxx>
• Re: I/O errors without erros from underlying device
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: I/O errors without erros from underlying device
  • From: Arkadiusz Miskiewicz <a.miskiewicz@xxxxxxxxx>
• Re: I/O errors without erros from underlying device
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• I/O errors without erros from underlying device
  • From: Arkadiusz Miskiewicz <a.miskiewicz@xxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: Unable to (un)-grow raid6
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Unable to (un)-grow raid6
  • From: David Waite <david@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Unable to (un)-grow raid6
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Unable to (un)-grow raid6
  • From: David Waite <david@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [PATCH v2 2/3] block: Add badblock management for gendisks
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: Andreas Dilger <adilger@xxxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH v2 2/3] block: Add badblock management for gendisks
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v2 0/3] Badblock tracking for gendisks
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH 15/19] capabilities: Allow privileged user in s_user_ns to set file caps
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 17/19] fuse: Support fuse filesystems outside of init_user_ns
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 18/19] fuse: Restrict allow_other to the superblock's namespace or a descendant
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 18/19] fuse: Restrict allow_other to the superblock's namespace or a descendant
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 17/19] fuse: Support fuse filesystems outside of init_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 15/19] capabilities: Allow privileged user in s_user_ns to set file caps
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 18/19] fuse: Restrict allow_other to the superblock's namespace or a descendant
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH 17/19] fuse: Support fuse filesystems outside of init_user_ns
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 09/19] fs: Refuse uid/gid changes which don't map into s_user_ns
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 15/19] capabilities: Allow privileged user in s_user_ns to set file caps
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 13/19] fs: Allow superblock owner to access do_remount_sb()
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 12/19] fs: Don't remove suid for CAP_FSETID in s_user_ns
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 11/19] fs: Ensure the mounter of a filesystem is privileged towards its inodes
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 10/19] fs: Update posix_acl support to handle user namespace mounts
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH 09/19] fs: Refuse uid/gid changes which don't map into s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: RAID6 - "Invalid Argument" / "does not have a valid v1.2 superblock" ?!
  • From: Tobias Geiger <tobias.geiger@xxxxxxxxx>
• Re: [PATCH 09/19] fs: Refuse uid/gid changes which don't map into s_user_ns
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 05/19] userns: Replace in_userns with current_in_userns
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 03/19] fs: Treat foreign mounts as nosuid
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 08/19] cred: Reject inodes with invalid ids in set_create_file_as()
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 07/19] fs: Check for invalid i_uid in may_follow_link()
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 02/19] block_dev: Check permissions towards block device inode when mounting
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH 01/19] block_dev: Support checking inode permissions in lookup_bdev()
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [PATCH 17/19] fuse: Support fuse filesystems outside of init_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• [PATCH 1/2] md-cluster: update comments for MD_CLUSTER_SEND_LOCKED_ALREADY
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 2/2] md: update comment for md_allow_write
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Weedy <weedy2887@xxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Zdenek Kabelac <zkabelac@xxxxxxxxxx>
• Reshape stalls and fails when SELinux is enabled
  • From: Enrico Tagliavini <enrico.tagliavini@xxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 1/2] raid5-cache: use a bio_set
  • From: Shaohua Li <shli@xxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [RFC] using mempools for raid5-cache
  • From: Shaohua Li <shli@xxxxxx>
• Re: two small raid5 cache updates
  • From: Shaohua Li <shli@xxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• RAID6 - "Invalid Argument" / "does not have a valid v1.2 superblock" ?!
  • From: Tobias Geiger <tobias.geiger@xxxxxxxxx>
• [PATCH 2/2] raid5-cache: use a mempool for the metadata block
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 1/2] raid5-cache: use a bio_set
  • From: Christoph Hellwig <hch@xxxxxx>
• [RFC] using mempools for raid5-cache
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 2/2] raid5-cache: free meta_page earlier
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 1/2] raid5-cache: simplify r5l_move_io_unit_list
  • From: Christoph Hellwig <hch@xxxxxx>
• two small raid5 cache updates
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 02/19] block_dev: Check permissions towards block device inode when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 01/19] block_dev: Support checking inode permissions in lookup_bdev()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH 00/19] Support fuse mounts in user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 03/19] fs: Treat foreign mounts as nosuid
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 06/19] Smack: Handle labels consistently in untrusted mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 07/19] fs: Check for invalid i_uid in may_follow_link()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 04/19] selinux: Add support for unprivileged mounts from user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 05/19] userns: Replace in_userns with current_in_userns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 10/19] fs: Update posix_acl support to handle user namespace mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 08/19] cred: Reject inodes with invalid ids in set_create_file_as()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 11/19] fs: Ensure the mounter of a filesystem is privileged towards its inodes
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 09/19] fs: Refuse uid/gid changes which don't map into s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 12/19] fs: Don't remove suid for CAP_FSETID in s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• [PATCH 13/19] fs: Allow superblock owner to access do_remount_sb()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 14/19] fs: Permit FIBMAP for users with CAP_SYS_RAWIO in s_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 19/19] fuse: Allow user namespace mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 18/19] fuse: Restrict allow_other to the superblock's namespace or a descendant
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 17/19] fuse: Support fuse filesystems outside of init_user_ns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 16/19] fuse: Add support for pid namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH 15/19] capabilities: Allow privileged user in s_user_ns to set file caps
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Phil Turmel <philip@xxxxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• RE: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Robert Kierski <rkierski@xxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Semyon Enskiy <semyon.enskiy@xxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: RAID 5,6 sequential writing seems slower in newer kernels
  • From: keld@xxxxxxxxxx
• [PATCH 2/3] [mdadm] recreate journal in mdadm
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 0/3] mdadm: re-add journal to array with bad journal
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 1/3] add sysfs_array_state to struct mdinfo
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 16/17] Clear MBR in when Kill superblock
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 11/17] policy: enable enclosure names for domain definitions
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 02/17] mdadm: allow a /dev/disk/by-slot as domain path descriptor
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 10/17] config: ENCLOSURE keyword and enclosure device list expansion
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 15/17] SCSIMODE: configuration file support for mode page settings.
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 06/17] ses: workaround sysfs deprecated
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 17/17] In generated udev rules, skip RAID members
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 05/17] imsm: quiet detail platform
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 12/17] invoke hot-add policy on "change" events
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 14/17] scsi mode sense/select support
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 00/17] mdadm: SCSI enclosure based array
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 01/17] udev rules and infrastructure for /dev/disk/by-slot
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 04/17] fix variable offset when ':' is present in the device name
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 08/17] enclosure detection/enumeration
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 13/17] Toggle enclosure leds in response to raid events
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 03/17] 'act_spare' should be the minimum requirement for dynamic domains
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 07/17] prepare for enclosure platform details
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 09/17] Add --brief support to --enclosure
  • From: Song Liu <songliubraving@xxxxxx>
• RAID 5,6 sequential writing seems slower in newer kernels
  • From: Dallas Clement <dallas.a.clement@xxxxxxxxx>
• Re: [PATCH v2 3/3] md: convert to use the generic badblocks code
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v2 3/3] md: convert to use the generic badblocks code
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH 2/4] mdadm: output info more precisely when change bitmap to none
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 3/4] mdadm: don't show cluster name once the bitmap is cleared
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 4/4] mdadm: do not display bitmap info if it is cleared
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 1/4] mdadm: let cluster raid could also add disk within incremental mode
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [mdadm PATCH] Grow raid disks without backup file fail
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH V3 2/2] md-cluster: Protect communication with mutexes
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 2/3] md-cluster: introduce clear_clusterinfo_from_sb
  • From: Guoqing Jiang <gqJiang@xxxxxxxx>
• Re: [PATCH 2/3] md-cluster: introduce clear_clusterinfo_from_sb
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH V3 2/2] md-cluster: Protect communication with mutexes
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH] dm: constify crypt_iv_operations structures
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH V3 2/2] md-cluster: Protect communication with mutexes
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH Resend V2 2/2] md-cluster: Protect communication with mutexes (fwd)
  • From: Julia Lawall <julia.lawall@xxxxxxx>
• [PATCH Resend V2 1/2] md-cluster: Defer MD reloading to mddev->thread
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH Resend V2 2/2] md-cluster: Protect communication with mutexes
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [dm-devel] [PATCH] dm-ioctl: fix 4-characters indentations
  • From: Minfei Huang <mnfhuang@xxxxxxxxx>
• Reply Me For Details
  • From: "HS09912HH3" <akva@xxxxxxxx>
• [md:for-next 7/8] drivers/md/md.c:6594:6: error: expected ';' before 'rv'
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• Re: [PATCH 2/3] md-cluster: introduce clear_clusterinfo_from_sb
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 2/3] md-cluster: introduce clear_clusterinfo_from_sb
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Semyon Enskiy <semyon.enskiy@xxxxxxxxx>
• [PATCH v2 3/3] md: convert to use the generic badblocks code
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v2 2/3] block: Add badblock management for gendisks
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v2 1/3] badblocks: Add core badblock management code
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH v2 0/3] Badblock tracking for gendisks
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH 2/3] block: Add badblock management for gendisks
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: [PATCH 2/3] block: Add badblock management for gendisks
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Semyon Enskiy <semyon.enskiy@xxxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Semyon Enskiy <semyon.enskiy@xxxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH 2/3] block: Add badblock management for gendisks
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Semyon Enskiy <semyon.enskiy@xxxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Semyon Enskiy <semyon.enskiy@xxxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH] dm-ioctl: fix 4-characters indentations
  • From: Geliang Tang <geliangtang@xxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Semyon Enskiy <semyon.enskiy@xxxxxxxxx>
• [PATCH] md: dm-bufio: Use BUG_ON instead of if BUG
  • From: Anup Limbu <anuplimbu14@xxxxxxxxx>
• Re: [PATCH 2/3] block: Add badblock management for gendisks
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 2/3] block: Add badblock management for gendisks
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH 1/3] badblocks: Add core badblock management code
  • From: Jens Axboe <axboe@xxxxxx>
• Re: [PATCH 2/3] block: Add badblock management for gendisks
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: [PATCH 2/3] block: Add badblock management for gendisks
  • From: "Verma, Vishal L" <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH 2/3] block: Add badblock management for gendisks
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• mdadm and size differences
  • From: Marco De Vitis <starless@xxxxxxx>
• Re: raid10 resync hangs in 4.2.6, 4.3
  • From: Andre Tomt <andre@xxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Semyon Enskiy <semyon.enskiy@xxxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Semyon Enskiy <semyon.enskiy@xxxxxxxxx>
• Recovering RAID5 with 2, actually 1, faulty disks.
  • From: Semyon Enskiy <semyon.enskiy@xxxxxxxxx>
• [PATCH] md: avoid warning for 32-bit sector_t
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: raid10 resync hangs in 4.2.6, 4.3
  • From: Andre Tomt <andre@xxxxxxxx>
• Re: raid10 resync hangs in 4.2.6, 4.3
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: raid10 resync hangs in 4.2.6, 4.3
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH] mdadm: check bitmap first when reshape raid1 to raid0
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: raid10 resync hangs in 4.2.6, 4.3
  • From: Andre Tomt <andre@xxxxxxxx>
• [PATCH 0/3] Badblock tracking for gendisks
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH 3/3] md: convert to use the generic badblocks code
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH 2/3] block: Add badblock management for gendisks
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• [PATCH 1/3] badblocks: Add core badblock management code
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• Re: raid10 resync hangs in 4.2.6, 4.3
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• raid10 resync hangs in 4.2.6, 4.3
  • From: Andre Tomt <andre@xxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: Ubuntu crashed during RAID6 grow
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH 3/3] md-cluster: update the documentation
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 2/3] md-cluster: introduce clear_clusterinfo_from_sb
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 1/3] md-cluster: append some actions when change bitmap from clustered to none
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [v2 PATCH 2/5] md-cluster: Protect communication with mutexes
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [v2 PATCH] md-cluster: Defer MD reloading to mddev->thread
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: Ubuntu crashed during RAID6 grow
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Ubuntu crashed during RAID6 grow
  • From: Nathan Peterson <nathan@xxxxxxxxxxx>
• [RFC PATCH] block: introduce poison tracking for block devices
  • From: Vishal Verma <vishal.l.verma@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Octavian Purdila <octavian.purdila@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: "Richard W.M. Jones" <rjones@xxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Colin Walters <walters@xxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: "Serge E. Hallyn" <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: James Morris <jmorris@xxxxxxxxx>
• [PATCH 2/2] mdadm: output info more precisely when change bitmap
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 1/2] mdadm: let cluster raid could also add disk within incremental mode
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: RAID 6 Reshape Woes
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID 6 Reshape Woes
  • From: Francisco Parada <cisco@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID 6 Reshape Woes
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Serge Hallyn <serge.hallyn@xxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: bfields@xxxxxxxxxxxx (J. Bruce Fields)
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Nikolay Borisov <kernel@xxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: [PATCH v3 7/7] Smack: Handle labels consistently in untrusted mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 7/7] Smack: Handle labels consistently in untrusted mounts
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH v3 6/7] userns: Replace in_userns with current_in_userns
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH v3 5/7] selinux: Add support for unprivileged mounts from user namespaces
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH v3 4/7] fs: Treat foreign mounts as nosuid
  • From: James Morris <jmorris@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Octavian Purdila <octavian.purdila@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Richard Weinberger <richard@xxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Octavian Purdila <octavian.purdila@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Richard Weinberger <richard.weinberger@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 7/7] Smack: Handle labels consistently in untrusted mounts
  • From: Casey Schaufler <casey@xxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: "Serge E. Hallyn" <serge@xxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/7] User namespace mount updates
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [PATCH v3 2/7] block_dev: Check permissions towards block device inode when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v3 3/7] mtd: Check permissions towards mtd block device inode when mounting
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v3 0/7] User namespace mount updates
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v3 1/7] block_dev: Support checking inode permissions in lookup_bdev()
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v3 4/7] fs: Treat foreign mounts as nosuid
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v3 6/7] userns: Replace in_userns with current_in_userns
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v3 7/7] Smack: Handle labels consistently in untrusted mounts
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• [PATCH v3 5/7] selinux: Add support for unprivileged mounts from user namespaces
  • From: Seth Forshee <seth.forshee@xxxxxxxxxxxxx>
• Re: Reconstruct a RAID 6 that has failed in a non typical manner
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID5 hangs in break_stripe_batch_list
  • From: Martin Svec <martin.svec@xxxxxxxx>
• Re: Reconstruct a RAID 6 that has failed in a non typical manner
  • From: Marc Pinhede <marc.pinhede@xxxxxxxx>
• Re: WD Red vs Black drives for RAID1
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: RAID5 hangs in break_stripe_batch_list
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: WD Red vs Black drives for RAID1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: WD Red vs Black drives for RAID1
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: WD Red vs Black drives for RAID1
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: WD Red vs Black drives for RAID1
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: WD Red vs Black drives for RAID1
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: WD Red vs Black drives for RAID1
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: WD Red vs Black drives for RAID1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: WD Red vs Black drives for RAID1
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: WD Red vs Black drives for RAID1
  • From: "Jens-U. Mozdzen" <jmozdzen@xxxxxx>
• Re: WD Red vs Black drives for RAID1
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: WD Red vs Black drives for RAID1
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: WD Red vs Black drives for RAID1
  • From: "Jens-U. Mozdzen" <jmozdzen@xxxxxx>
• Re: WD Red vs Black drives for RAID1
  • From: Another Sillyname <anothersname@xxxxxxxxxxxxxx>
• WD Red vs Black drives for RAID1
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• RAID5 hangs in break_stripe_batch_list
  • From: Martin Svec <martin.svec@xxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH] drivers: md: use ktime_get_real_seconds()
  • From: Deepa Dinamani <deepa.kernel@xxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: Raid server Motherboard recommendation.
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Raid server Motherboard recommendation.
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Problem w/ commit ac8fa4196d20 on older, slower hardware
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Problem w/ commit ac8fa4196d20 on older, slower hardware
  • From: Joshua Kinard <kumba@xxxxxxxxxx>
• Re: [PATCH 1/6] md-cluster: Protect communication with mutexes
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Raid server Motherboard recommendation.
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• RE: Raid server Motherboard recommendation.
  • From: Michael Munger <michael@xxxxxxxxxxxxxxxxxxx>
• Re: Raid server Motherboard recommendation.
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: Raid server Motherboard recommendation.
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• badblocks seem to be causing problems with raid6 - badblocks list replicating all all drives
  • From: matt@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Jan Kara <jack@xxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Mark Brown <broonie@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Jan Kara <jack@xxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: Raid server Motherboard recommendation.
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Raid server Motherboard recommendation.
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: [PATCH 1/2] block: Introduce BIO_ENDIO_FREE for bio flags
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Raid server Motherboard recommendation.
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/2] block: Introduce BIO_ENDIO_FREE for bio flags
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• Re: [RFC PATCH 00/32] separate operations from flags in the bio/request structs
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 00/32] separate operations from flags in the bio/request structs
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Buffer I/O errors & Kernel OOPS with RAID6
  • From: matt@xxxxxxxxxxxxxxxxxxx
• Re: [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH 1/2] block: Introduce BIO_ENDIO_FREE for bio flags
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH 2/2] md: dm-crypt: Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• [PATCH 0/2] Introduce the request handling for dm-crypt
  • From: Baolin Wang <baolin.wang@xxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 00/32] separate operations from flags in the bio/request structs
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• Re: Offline array, events count mismatch
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Offline array, events count mismatch
  • From: Guillaume Paumier <guillaume.paumier@xxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• Re: [PATCH 1/8] block/genhd.c: Add error handling
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• Re: RESYNC Bug ? [was Re: Stop resync operation]
  • From: d4lamar <d4lamar@xxxxxxxxx>
• Re: RESYNC Bug ? [was Re: Stop resync operation]
  • From: Anugraha Sinha <asinha.mailinglist@xxxxxxxxx>
• RESYNC Bug ? [was Re: Stop resync operation]
  • From: d4lamar <d4lamar@xxxxxxxxx>
• Re: [PATCH 1/8] block/genhd.c: Add error handling
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/8] block/genhd.c: Add error handling
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 4/6] md-cluster: Defer MD reloading to mddev->thread
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 1/6] md-cluster: Protect communication with mutexes
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 6/6] md-cluster: Allow spare devices to be marked as faulty
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 5/6] md-cluster: Fix the remove sequence with the new MD reload code
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 4/6] md-cluster: Defer MD reloading to mddev->thread
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 3/8] block/floppy.c: handle blk_register_region() return value
  • From: Grant Grundler <grundler@xxxxxxxxxxxx>
• Re: [PATCH 3/6] md-cluster: remove a disk asynchronously from cluster environment
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 2/6] md-cluster: Avoid the resync ping-pong
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 1/6] md-cluster: Protect communication with mutexes
  • From: NeilBrown <neilb@xxxxxxxx>
• raid6 didnt syncing - Bug?
  • From: Dragon <Sunghost@xxxxxx>
• Re: RAID6 reshape stalls immediately
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID6 reshape stalls immediately
  • From: Peter Chubb <peter.chubb@xxxxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Fwd: Re: broken raid level 5 array caused by user error
  • From: Jan Kasper <cubical@xxxxxxxxxxxxxx>
• Re: Buffer I/O errors & Kernel OOPS with RAID6
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID6 reshape stalls immediately
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID6 reshape stalls immediately
  • From: Anugraha Sinha <asinha.mailinglist@xxxxxxxxx>
• Re: broken raid level 5 array caused by user error
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Buffer I/O errors & Kernel OOPS with RAID6
  • From: matt@xxxxxxxxxxxxxxxxxxx
• broken raid level 5 array caused by user error
  • From: Mathias Mueller <raidfail@xxxxxx>
• [PATCH 2/8] mmc: handle add_disk() return value
  • From: Vishnu Pratap Singh <vishnu.ps@xxxxxxxxxxx>
• Re: Offline array, events count mismatch
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Offline array, events count mismatch
  • From: Guillaume Paumier <guillaume.paumier@xxxxxxxxx>
• Re: [PATCH 5/8] zram: handle add_disk() & blk_register_region() return value
  • From: Sergey Senozhatsky <sergey.senozhatsky.work@xxxxxxxxx>
• [GIT PULL REQUET] on config fix for md
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: RAID 6 Not Mounting (Block device is empty)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 6 Not Mounting (Block device is empty)
  • From: Francisco Parada <cisco@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID 6 Not Mounting (Block device is empty)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 6 Not Mounting (Block device is empty)
  • From: Francisco Parada <cisco@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID 6 Not Mounting (Block device is empty)
  • From: Francisco Parada <cisco@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID 6 Not Mounting (Block device is empty)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 6 Not Mounting (Block device is empty)
  • From: Francisco Parada <cisco@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID6 reshape stalls immediately
  • From: Peter Chubb <peter.chubb@xxxxxxxxxxxx>
• Re: RAID 6 Not Mounting (Block device is empty)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 6 Not Mounting (Block device is empty)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 6 Not Mounting (Block device is empty)
  • From: Francisco Parada <cisco@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID 6 Not Mounting (Block device is empty)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• RAID 6 Not Mounting (Block device is empty)
  • From: Francisco Parada <cisco@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 00/32] separate operations from flags in the bio/request structs
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 32/32] block: remove __REQ op defs and reduce bi_op/bi_rw sizes
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH 19/32] block: add helper to get data dir from op
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [RESEND RFC PATCH 00/32] separate operations from flags in the bio/request structs
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH] bcache: Really show state of work pending bit
  • From: Jiri Kosina <jikos@xxxxxxxxxx>
• [PATCH] md: MD_RAID456 now depends on LIBCRC32C
  • From: Guenter Roeck <linux@xxxxxxxxxxxx>
• Re: [PATCH 2/8] mmc: handle add_disk() return value
  • From: Ulf Hansson <ulf.hansson@xxxxxxxxxx>
• Re: RAID6 reshape stalls immediately
  • From: Anugraha Sinha <asinha.mailinglist@xxxxxxxxx>
• Re: RAID6 reshape stalls immediately
  • From: Anugraha Sinha <asinha.mailinglist@xxxxxxxxx>
• Re: [PATCH 3/8] block/floppy.c: handle blk_register_region() return value
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [PATCH 8/8] ide/ide-probe.c: handle blk_register_region() return value
  • From: Vishnu Pratap Singh <vishnu.ps@xxxxxxxxxxx>
• [PATCH 7/8] cdrom/gdrom.c: handle add_disk() return value
  • From: Vishnu Pratap Singh <vishnu.ps@xxxxxxxxxxx>
• [PATCH 6/8] md/md.c: handle blk_register_region() return value
  • From: Vishnu Pratap Singh <vishnu.ps@xxxxxxxxxxx>
• [PATCH 5/8] zram: handle add_disk() & blk_register_region() return value
  • From: Vishnu Pratap Singh <vishnu.ps@xxxxxxxxxxx>
• [PATCH 4/8] block/loop.c: handle add_disk() & blk_register_region() return value
  • From: Vishnu Pratap Singh <vishnu.ps@xxxxxxxxxxx>
• [PATCH 3/8] block/floppy.c: handle blk_register_region() return value
  • From: Vishnu Pratap Singh <vishnu.ps@xxxxxxxxxxx>
• [PATCH 2/8] mmc: handle add_disk() return value
  • From: Vishnu Pratap Singh <vishnu.ps@xxxxxxxxxxx>
• [PATCH 1/8] block/genhd.c: Add error handling
  • From: Vishnu Pratap Singh <vishnu.ps@xxxxxxxxxxx>
• Stop resync operation
  • From: d4lamar <d4lamar@xxxxxxxxx>
• [PATCH 6/6] md-cluster: Allow spare devices to be marked as faulty
  • From: rgoldwyn@xxxxxxx
• [PATCH 5/6] md-cluster: Fix the remove sequence with the new MD reload code
  • From: rgoldwyn@xxxxxxx
• [PATCH 4/6] md-cluster: Defer MD reloading to mddev->thread
  • From: rgoldwyn@xxxxxxx
• [PATCH 3/6] md-cluster: remove a disk asynchronously from cluster environment
  • From: rgoldwyn@xxxxxxx
• [PATCH 2/6] md-cluster: Avoid the resync ping-pong
  • From: rgoldwyn@xxxxxxx
• [PATCH 1/6] md-cluster: Protect communication with mutexes
  • From: rgoldwyn@xxxxxxx
• Re: [PATCH] raid5-cache: add crc32c Kconfig dependency
  • From: Neil Brown <neilb@xxxxxxxx>
• Re: [PATCH] md/raid5: remove redundant check in stripe_add_to_batch_list()
  • From: Neil Brown <neilb@xxxxxxxx>
• Re: raid6 stuck at reshape
  • From: Иван Исаев <1@xxxxxxxxxx>
• Re: looking for good reference on storage configuration
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: looking for good reference on storage configuration
  • From: Ladislav Mate <ladislav.mate@xxxxxxxxx>
• Re: [dm-devel] [PATCH 19/32] block: add helper to get data dir from op
  • From: Mike Christie <mchristi@xxxxxxxxxx>
• Re: [RESEND RFC PATCH 00/32] separate operations from flags in the bio/request structs
  • From: Bob Peterson <rpeterso@xxxxxxxxxx>
• Re: Reconstruct a RAID 6 that has failed in a non typical manner
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Reconstruct a RAID 6 that has failed in a non typical manner
  • From: Clement Parisot <clement.parisot@xxxxxxxx>
• Re: Advice requested re: hard drive setup for RAID arrays
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• RAID6 reshape stalls immediately
  • From: Peter Chubb <peter.chubb@xxxxxxxxxxxx>
• Re: [dm-devel] [PATCH 19/32] block: add helper to get data dir from op
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: [PATCH] md/raid10: fix data corruption and crash during resync
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [RESEND RFC PATCH 00/32] separate operations from flags in the bio/request structs
  • From: mchristi@xxxxxxxxxx
• [PATCH 01/32] block/fs: add REQ_OP definitions.
  • From: mchristi@xxxxxxxxxx
• [PATCH 02/32] block/fs/mm: prepare submit_bio_wait users for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 05/32] drbd: prepare drbd for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 03/32] dio/btrfs: prep dio->submit_bio users for bi_rw split.
  • From: mchristi@xxxxxxxxxx
• [PATCH 06/32] xen blkback: prepare for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 04/32] block: prepare blkdev_issue_discard for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 07/32] dm: prepare for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 08/32] target: prepare for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 09/32] btrfs: prepare for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 10/32] f2fs: prepare for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 14/32] block/fs/mm: pass in op and flags to submit_bio
  • From: mchristi@xxxxxxxxxx
• [PATCH 15/32] btrfs: prepare for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 13/32] mm: prepare for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 16/32] block/fs/md: pass in op and flags to submit_bh
  • From: mchristi@xxxxxxxxxx
• [PATCH 17/32] block: add operation field to bio struct
  • From: mchristi@xxxxxxxxxx
• [PATCH 12/32] xfs: prepare for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 11/32] gfs2: prepare for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 18/32] drbd: set bio bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 19/32] block: add helper to get data dir from op
  • From: mchristi@xxxxxxxxxx
• [PATCH 20/32] md: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 21/32] bcache: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 25/32] block: add operation field to request struct
  • From: mchristi@xxxxxxxxxx
• [PATCH 24/32] dm: pass dm stats data dir instead of bi_rw
  • From: mchristi@xxxxxxxxxx
• [PATCH 26/32] ide cd: do not set REQ_WRITE on requests.
  • From: mchristi@xxxxxxxxxx
• [PATCH 22/32] block/fs/drivers: set bi_op to REQ_OP
  • From: mchristi@xxxxxxxxxx
• [PATCH 23/32] block/fs: pass in op and flags to ll_rw_block
  • From: mchristi@xxxxxxxxxx
• [PATCH 27/32] cfq/cgroup: pass operation and flags seperately
  • From: mchristi@xxxxxxxxxx
• [PATCH 28/32] block/fs/drivers: use bio/rq_data_dir helpers
  • From: mchristi@xxxxxxxxxx
• [PATCH 29/32] block/drivers: rm request cmd_flags REQ_OP use
  • From: mchristi@xxxxxxxxxx
• [PATCH 30/32] drbd: don't use bi_rw for operations
  • From: mchristi@xxxxxxxxxx
• [PATCH 32/32] block: remove __REQ op defs and reduce bi_op/bi_rw sizes
  • From: mchristi@xxxxxxxxxx
• [PATCH 31/32] block/fs/driver: rm bio bi_rw REQ_OP use
  • From: mchristi@xxxxxxxxxx
• Re: Advice requested re: hard drive setup for RAID arrays
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Advice requested re: hard drive setup for RAID arrays
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Advice requested re: hard drive setup for RAID arrays
  • From: Edward Kuns <eddie.kuns@xxxxxxxxx>
• Re: Advice requested re: hard drive setup for RAID arrays
  • From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 00/32] separate operations from flags in the bio/request structs
  • From: Mike Christie <michaelc@xxxxxxxxxxx>
• Re: [dm-devel] [RFC PATCH 00/32] separate operations from flags in the bio/request structs
  • From: Bart Van Assche <bart.vanassche@xxxxxxxxxxx>
• Re: Advice requested re: hard drive setup for RAID arrays
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH 03/32] dio/btrfs: prep dio->submit_bio users for bi_rw split.
  • From: mchristi@xxxxxxxxxx
• [PATCH 02/32] block/fs/mm: prepare submit_bio_wait users for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 01/32] block/fs: add REQ_OP definitions.
  • From: mchristi@xxxxxxxxxx
• [RFC PATCH 00/32] separate operations from flags in the bio/request structs
  • From: mchristi@xxxxxxxxxx
• [PATCH 05/32] drbd: prepare drbd for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 04/32] block: prepare blkdev_issue_discard for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 08/32] target: prepare for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 07/32] dm: prepare for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 09/32] btrfs: prepare for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH 06/32] xen blkback: prepare for bi_rw split
  • From: mchristi@xxxxxxxxxx
• [PATCH] md/raid10: fix data corruption and crash during resync
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: Advice requested re: hard drive setup for RAID arrays
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Advice requested re: hard drive setup for RAID arrays
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Advice requested re: hard drive setup for RAID arrays
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Advice requested re: hard drive setup for RAID arrays
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: raid6 stuck at reshape
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Fwd: raid6 stuck at reshape
  • From: Иван Исаев <1@xxxxxxxxxx>
• Re: raid6 stuck at reshape
  • From: Xiao Ni <xni@xxxxxxxxxx>
• raid6 stuck at reshape
  • From: Иван Исаев <1@xxxxxxxxxx>
• Re: Advice requested
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Advice requested
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: How to recover after md crash during reshape? - SOLVED/SUMMARY
  • From: Andras Tantos <andras@xxxxxxxxxxxxxxxx>
• Re: Advice requested
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Advice requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Advice requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Advice requested
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Failed Raid 5 due to OS mbr written on one of the array drives
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Failed Raid 5 due to OS mbr written on one of the array drives
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Failed Raid 5 due to OS mbr written on one of the array drives
  • From: Nicolas Tellier <telliern@xxxxxxxxx>
• [PATCH] raid5-cache: add crc32c Kconfig dependency
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: Advice requested
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Advice requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Advice requested
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Advice requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Advice requested
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Advice requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Advice requested
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Advice requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: performance issue
  • From: Neil Brown <neilb@xxxxxxxx>
• Re: Advice requested
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Advice requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Advice requested
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• [PATCH] mdadm: check bitmap first when reshape raid1 to raid0
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Advice requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Advice requested
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: performance issue
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• Re: Failed Raid 5 due to OS mbr written on one of the array drives
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Failed Raid 5 due to OS mbr written on one of the array drives
  • From: Nicolas Tellier <telliern@xxxxxxxxx>
• Re: [PATCH] mdadm: check bitmap first when reshape raid1 to raid0
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Advice requested
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH] mdadm: check bitmap first when reshape raid1 to raid0
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [PATCH] md/raid5: remove redundant check in stripe_add_to_batch_list()
  • From: Roman Gushchin <klamm@xxxxxxxxxxxxxx>
• [GIT PULL REQUEST] md updates for 4.4
  • From: Neil Brown <neil@xxxxxxxxxx>
• Re: Advice requested
  • From: Phil Turmel <philip@xxxxxxxxxx>