Linux RAID Storage Date Index

• Thread Index

• [PATCH 21/24] Resync start/Finish actions
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 22/24] Suspend writes in RAID1 if within range
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 20/24] Send RESYNCING while performing resync start/stop
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 19/24] Reload superblock if METADATA_UPDATED is received
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 18/24] metadata_update sends message to other nodes
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 17/24] Communication Framework: Sending functions
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 16/24] Communication Framework: Receiving
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 15/24] Perform resync for cluster node failure
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 14/24] Initiate recovery on node failure
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 13/24] Copy set bits from another slot
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 12/24] bitmap_create returns bitmap pointer
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 11/24] Gather on-going resync information of other nodes
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 10/24] Lock bitmap while joining the cluster
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 09/24] Use separate bitmaps for each nodes in the cluster
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 08/24] Add node recovery callbacks
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 07/24] Return MD_SB_CLUSTERED if mddev is clustered
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 06/24] Introduce md_cluster_info
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 05/24] Introduce md_cluster_operations to handle cluster functions
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 04/24] DLM lock and unlock functions
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 03/24] Create a separate module for clustering support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 02/24] Add number of nodes to bitmap structure for clustering
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 01/24] md-cluster: Design Documentation
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 00/24] Clustered MD RAID1
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: Panic doing BLKDISCARD on a raid 5 array on linux 3.17.3
  • From: Anthony Wright <anthony@xxxxxxxxxxxxxxx>
• Re: Panic doing BLKDISCARD on a raid 5 array on linux 3.17.3
  • From: Anthony Wright <anthony@xxxxxxxxxxxxxxx>
• Re: Question about my patch
  • From: Peter Kieser <peter@xxxxxxxxx>
• Re: raid10: 6 out of 8 disks marked as stale on every restart
  • From: Peter Kieser <peter@xxxxxxxxx>
• RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
• Re: Bug#763917: mdadm: rounding errors in human_size()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10: 6 out of 8 disks marked as stale on every restart
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Panic doing BLKDISCARD on a raid 5 array on linux 3.17.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] drivers:md: Remove no longer needed fixme comment in raid5.c
  • From: Valdis.Kletnieks@xxxxxx
• Hung RAID5 array with discard
  • From: Terry Hardie <thardie@xxxxxxxxxxxxxxxx>
• Re: [PATCH] drivers:md: Remove no longer needed fixme comment in raid5.c
  • From: NeilBrown <neilb@xxxxxxx>
• indefinite hang when growing/reshaping
  • From: Chris Murphy <chris@xxxxxxxxxxxxxxxxx>
• Panic doing BLKDISCARD on a raid 5 array on linux 3.17.3
  • From: Anthony Wright <anthony@xxxxxxxxxxxxxxx>
• Expand RAID5 array or switch to RAID10
  • From: George Duffield <forumscollective@xxxxxxxxx>
• RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
• RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Question about my patch
  • From: NeilBrown <neilb@xxxxxxx>
• Re: "bitmap file is out of date, doing full recovery"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: [PATCH] Update CONFIG_DM_CRYPT help-text link
  • From: Loic Pefferkorn <loic@xxxxxxxx>
• [PATCH] Update CONFIG_DM_CRYPT help-text link
  • From: Loic Pefferkorn <loic@xxxxxxxx>
• Re: [PATCH] Update CONFIG_DM_CRYPT help-text link
  • From: NeilBrown <neilb@xxxxxxx>
• RE: udisks error creating watch file in md127 container directory
  • From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
• udisks error creating watch file in md127 container directory
  • From: "John L. Center" <jlcenter@xxxxxxxxxxx>
• Re: RAID1 + power fail + unwanted activation
  • From: Csordás Csaba <cscsordas@xxxxxxxxx>
• Re: Lost raid 5 volume
  • From: "Neil ." <neil.perrie@xxxxxxxxx>
• Re: Lost raid 5 volume
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: "bitmap file is out of date, doing full recovery"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Lost raid 5 volume
  • From: "Neil ." <neil.perrie@xxxxxxxxx>
• [GIT PULL REQUEST] md updates for 3.19
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Lost raid 5 volume
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Lost raid 5 volume
  • From: "Neil ." <neil.perrie@xxxxxxxxx>
• raid10: 6 out of 8 disks marked as stale on every restart
  • From: Peter Kieser <peter@xxxxxxxxx>
• Re: Growing RAID-10 (near-2) array - which kernel needed?
  • From: cvb@xxxxxxxxxxx
• Re: Growing RAID-10 (near-2) array - which kernel needed?
  • From: cvb@xxxxxxxxxxx
• Re: Growing RAID-10 (near-2) array - which kernel needed?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Growing RAID-10 (near-2) array - which kernel needed?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Growing RAID-10 (near-2) array - which kernel needed?
  • From: cvb@xxxxxxxxxxx
• Re: [PATCH] IMSM: do not use comma expression for simple assignments
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: md raid performance with 3-18-rc3
  • From: Manish Awasthi <manish.awasthi@xxxxxxxxxxxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: md raid performance with 3-18-rc3
  • From: Manish Awasthi <manish.awasthi@xxxxxxxxxxxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: Disks never stop spinning
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: Disks never stop spinning
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: Multiple arrays out of devices belonging to single array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bug#763917: mdadm: rounding errors in human_size()
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Multiple arrays out of devices belonging to single array
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: mdadm creates corrupt superblock
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Disks never stop spinning
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Good drive got kicked out - does mdadm assemble across suspend/resume like it does across reboots?
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: pretty unstable raid 5 now
  • From: "Matthew M. Dean" <fireculex@xxxxxxxxx>
• pretty unstable raid 5 now
  • From: "Matthew M. Dean" <fireculex@xxxxxxxxx>
• Re: [dm-devel] The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: zhangxiao <xiao.zhang@xxxxxxxxxxxxx>
• RAID1 + power fail + unwanted activation
  • From: Csordás Csaba <cscsordas@xxxxxxxxx>
• Re: The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [dm-devel] The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: stray raid10 with 9 hdd with -n3 layout
  • From: Klaus Thorn <klaus@xxxxxxxxxxxxxxxxx>
• Re: md raid performance with 3-18-rc3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md raid performance with 3-18-rc3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: LVM RAID1 syncing component
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: zhangxiao <xiao.zhang@xxxxxxxxxxxxx>
• Re: The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: zhangxiao <xiao.zhang@xxxxxxxxxxxxx>
• Re: The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: NeilBrown <neilb@xxxxxxx>
• The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: zhangxiao <xiao.zhang@xxxxxxxxxxxxx>
• Re: LVM RAID1 syncing component
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 5/8 v2] dm: replace memset by memzero_explicit
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] Grow: Fix wrong 'goto' in set_new_data_offset
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: NeilBrown <neilb@xxxxxxx>
• Re: LVM RAID1 syncing component
  • From: NeilBrown <neilb@xxxxxxx>
• Re: LVM RAID1 syncing component
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: LVM RAID1 syncing component
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: [PATCH 5/8 v2] dm: replace memset by memzero_explicit
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: [patch] dm space map metadata: fix sm_bootstrap_get_nr_blocks()
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: upgrading a RAID array in-place with larger drives. request for review of my approach?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: upgrading a RAID array in-place with larger drives. request for review of my approach?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: upgrading a RAID array in-place with larger drives. request for review of my approach?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: upgrading a RAID array in-place with larger drives. request for review of my approach?
  • From: terrygalant@xxxxxxxxxxxx
• Re: upgrading a RAID array in-place with larger drives. request for review of my approach?
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• upgrading a RAID array in-place with larger drives. request for review of my approach?
  • From: terrygalant@xxxxxxxxxxxx
• [PATCH 0/8] replace memset by memzero_explicit
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH 5/8 v2] dm: replace memset by memzero_explicit
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH 0/8] replace memset by memzero_explicit
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH 5/8] dm: replace memset by memzero_explicit
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [no subject]
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: LVM RAID1 syncing component
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Re:
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• [patch] dm space map metadata: fix sm_bootstrap_get_nr_blocks()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: mdadm raid5 single drive fail, single drive out of sync terror
  • From: "Robison, Jon (CMG-Atlanta)" <narfman0@xxxxxxxxx>
• [PATCH] Grow: Fix wrong 'goto' in set_new_data_offset
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: One question about man mdadm
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: One question about man mdadm
  • From: Carsten Aulbert <Carsten.Aulbert@xxxxxxxxxx>
• Re: One question about man mdadm
  • From: XiaoNi <xni@xxxxxxxxxx>
• One question about man mdadm
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Raid 10 far 2 layout clarification.
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• Re:
  • From: NeilBrown <neilb@xxxxxxx>
• Re: LVM RAID1 syncing component
  • From: NeilBrown <neilb@xxxxxxx>
• [no subject]
  • From: Travis Williams <travis@xxxxxxxxx>
• Raid 10 far 2 layout clarification.
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• Re: mdadm raid5 single drive fail, single drive out of sync terror
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: mdadm raid5 single drive fail, single drive out of sync terror
  • From: "Robison, Jon (CMG-Atlanta)" <narfman0@xxxxxxxxx>
• Re: mdadm raid5 single drive fail, single drive out of sync terror
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: mdadm raid5 single drive fail, single drive out of sync terror
  • From: Phil Turmel <philip@xxxxxxxxxx>
• mdadm raid5 single drive fail, single drive out of sync terror
  • From: Jon Robison <narfman0@xxxxxxxxx>
• Re: LVM RAID1 syncing component
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: Is it possible to grow a (far) RAID 10?
  • From: cvb@xxxxxxxxxxx
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: LVM RAID1 syncing component
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Is it possible to grow a (far) RAID 10?
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] Change way of printing name of a process
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: Is it possible to grow a (far) RAID 10?
  • From: cvb@xxxxxxxxxxx
• Is it possible to grow a (far) RAID 10?
  • From: Carsten Aulbert <Carsten.Aulbert@xxxxxxxxxx>
• LVM RAID1 syncing component
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: homehost and 0.90 format
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 - won't rebuild - assigns all added disks as spares
  • From: Jonathan Molyneux <jonathan@xxxxxxxxxxxxxxxxxxxx>
• RE: homehost and 0.90 format
  • From: "Boylan, Ross" <Ross.Boylan@xxxxxxxx>
• Re: homehost and 0.90 format
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD component device renaming with udev and MD on full disk
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD RAID5 hang on make_request
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md raid performance with 3-18-rc3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 - won't rebuild - assigns all added disks as spares
  • From: NeilBrown <neilb@xxxxxxx>
• raid10 - won't rebuild - assigns all added disks as spares
  • From: Jonathan Molyneux <jonathan@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/5] imsm: support for OROMs shared by multiple HBAs
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm creates corrupt superblock
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: NeilBrown <neilb@xxxxxxx>
• md raid performance with 3-18-rc3
  • From: Manish Awasthi <manish.awasthi@xxxxxxxxxxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• MD RAID5 hang on make_request
  • From: Henry Cai <henryplusplus@xxxxxxxxx>
• MD component device renaming with udev and MD on full disk
  • From: Jason Keltz <jas@xxxxxxxxxxxx>
• Re: degraded raid troubleshooting
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH v2 5/5] imsm: use efivarfs interface for reading UEFI variables
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: [PATCH 1/5] imsm: support for OROMs shared by multiple HBAs
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: mdadm creates corrupt superblock
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• degraded raid troubleshooting
  • From: Stephen Burke <steve.burke.56@xxxxxxxxx>
• Re: [PATCH 5/5] imsm: use efivarfs interface for reading UEFI variables
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/5] imsm: support for OROMs shared by multiple HBAs
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm creates corrupt superblock
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 1/1] dm: Deletion of unnecessary checks before two function calls
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH 1/1] bcache: Deletion of an unnecessary check before the function call "kobject_put"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: Re-assemble RAID6 from SW to HW RAID
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• [PATCH 5/5] imsm: use efivarfs interface for reading UEFI variables
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH 3/5] imsm: add support for NVMe devices
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH 4/5] imsm: detail-platform improvements
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH 2/5] imsm: support for second and combined AHCI controllers in UEFI mode
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH 1/5] imsm: support for OROMs shared by multiple HBAs
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH 0/5] imsm: support for NVMe devices and AHCI spanning
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: mdadm creates corrupt superblock
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: Re-assemble RAID6 from SW to HW RAID
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: Re-assemble RAID6 from SW to HW RAID
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re[2]: Raid 6 Fail Event
  • From: "Justin Stephenson" <justin@xxxxxxxxxxxxxxxxx>
• Re: Re-assemble RAID6 from SW to HW RAID
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re-assemble RAID6 from SW to HW RAID
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Raid 6 Fail Event
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Does order/ sequence of SATA drives matter?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Does order/ sequence of SATA drives matter?
  • From: forumscollective@xxxxxxxxx
• Re[2]: Raid 6 Fail Event
  • From: "Justin Stephenson" <justin@xxxxxxxxxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: NeilBrown <neilb@xxxxxxx>
• [PULL REQUEST] md bug fix for 3.18
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid 6 Fail Event
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Raid 6 Fail Event
  • From: "Justin Stephenson" <justin@xxxxxxxxxxxxxxxxx>
• Re: failed RAID 5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: failed RAID 5 array
  • From: Wolfgang Denk <wd@xxxxxxx>
• Re: failed RAID 5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: failed RAID 5 array
  • From: DeadManMoving <sequel@xxxxxxxxxxxx>
• Re: failed RAID 5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: failed RAID 5 array
  • From: DeadManMoving <sequel@xxxxxxxxxxxx>
• Re: failed RAID 5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: failed RAID 5 array
  • From: DeadManMoving <sequel@xxxxxxxxxxxx>
• Re: Disks never stop spinning
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Disks never stop spinning
  • From: Patrick Gautschi <patrick@xxxxxxxxxxxx>
• Re: md with shared disks
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Disks never stop spinning
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: failed RAID 5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: md with shared disks
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: md with shared disks
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: md with shared disks
  • From: Anton Ekermans <antone@xxxxxxxxxx>
• failed RAID 5 array
  • From: DeadManMoving <sequel@xxxxxxxxxxxx>
• Re: RAID 6 (containing LUKS dm-crypt) recovery help.
  • From: pg@xxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• homehost and 0.90 format
  • From: "Boylan, Ross" <Ross.Boylan@xxxxxxxx>
• Re: md with shared disks
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Disks never stop spinning
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: md with shared disks
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Jason Keltz <jas@xxxxxxxxxxxx>
• Re: --no-degraded does not work
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• md with shared disks
  • From: Anton Ekermans <antone@xxxxxxxxxx>
• What is the correct way of making image copy of a member disk in md array?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Trying to get POLICY working
  • From: NeilBrown <neilb@xxxxxxx>
• Re: --no-degraded does not work
  • From: NeilBrown <neilb@xxxxxxx>
• --no-degraded does not work
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: RAID 6 (containing LUKS dm-crypt) recovery help.
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Raid5 drive fail during grow and no backup
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 6 (containing LUKS dm-crypt) recovery help.
  • From: xar <xar@xxxxxxxxx>
• Re: RAID 6 (containing LUKS dm-crypt) recovery help.
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• RAID 6 (containing LUKS dm-crypt) recovery help.
  • From: xar <xar@xxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Vince <stuff@xxxxxxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Vince <stuff@xxxxxxxxxxxxxx>
• Re: mdadm named array (metadata 1.2) and udev when assembling an array in initramfs
  • From: Stephen Kent <smkent@xxxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: "bitmap file is out of date, doing full recovery"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: mdadm named array (metadata 1.2) and udev when assembling an array in initramfs
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Maintenance Checklist (sanity check request)
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• Re: [PATCH] mdadm: fix --detail for cases where device count > max_devices/2
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Fake RAID 10 on ASRock Z97 Extreme3 with Slackware 14.1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Fake RAID 10 on ASRock Z97 Extreme3 with Slackware 14.1
  • From: gornea <gornea@xxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Vince <stuff@xxxxxxxxxxxxxx>
• Re: Trying to get POLICY working
  • From: Caspar Smit <c.smit@xxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm named array (metadata 1.2) and udev when assembling an array in initramfs
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm named array (metadata 1.2) and udev when assembling an array in initramfs
  • From: Stephen Kent <smkent@xxxxxxxxxx>
• Re: Trying to get POLICY working
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm named array (metadata 1.2) and udev when assembling an array in initramfs
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: micah <micah@xxxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Phil Turmel <philip@xxxxxxxxxx>
• mdadm named array (metadata 1.2) and udev when assembling an array in initramfs
  • From: Stephen Kent <smkent@xxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Trying to get POLICY working
  • From: NeilBrown <neilb@xxxxxxx>
• Re: question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Trying to get POLICY working
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Trying to get POLICY working
  • From: Caspar Smit <c.smit@xxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Raid5 drive fail during grow and no backup
  • From: Vince <stuff@xxxxxxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• [PATCH] mdadm: fix --detail for cases where device count > max_devices/2
  • From: Or Sagi <ors@xxxxxxxxxxx>
• Re: Fwd: I will pay money for the correct RAID recovery instructions
  • From: Ian Young <ian@xxxxxxxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Grub2/raid quickie ...
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Grub2/raid quickie ...
  • From: NeilBrown <neilb@xxxxxxx>
• Grub2/raid quickie ...
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: micah <micah@xxxxxxxxxx>
• Re: mdadm creates corrupt superblock
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
  • From: Jason Keltz <jas@xxxxxxxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: micah <micah@xxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
  • From: Jason Keltz <jas@xxxxxxxxxxxx>
• Re: [PATCH] Grow: fix resize of array component size to > 32bits
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Grow: fix resize of array component size to > 32bits
  • From: Justin Maggard <jmaggard10@xxxxxxxxx>
• Re: "bitmap file is out of date, doing full recovery"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Very small bug on assemble --force
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help with raid1 to raid5 reshape after crash
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Grow: fix resize of array component size to > 32bits
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm creates corrupt superblock
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Very small bug on assemble --force
  • From: NeilBrown <neilb@xxxxxxx>
• Re: can i recover an all spare raid10 array ?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• RE: can i recover an all spare raid10 array ?
  • From: Roland RoLaNd <r_o_l_a_n_d@xxxxxxxxxxx>
• Re: can i recover an all spare raid10 array ?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• RE: can i recover an all spare raid10 array ?
  • From: Roland RoLaNd <r_o_l_a_n_d@xxxxxxxxxxx>
• Re: can i recover an all spare raid10 array ?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• FW: can i recover an all spare raid10 array ?
  • From: Roland RoLaNd <r_o_l_a_n_d@xxxxxxxxxxx>
• FW: can i recover an all spare raid10 array ?
  • From: Roland RoLaNd <r_o_l_a_n_d@xxxxxxxxxxx>
• mdadm creates corrupt superblock
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: can i recover an all spare raid10 array ?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• can i recover an all spare raid10 array ?
  • From: Roland RoLaNd <r_o_l_a_n_d@xxxxxxxxxxx>
• Very small bug on assemble --force
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: micah <micah@xxxxxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• RAID1 removing failed disk returns EBUSY
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Raid1 element stuck in (S) state
  • From: micah anderson <micah@xxxxxxxxxx>
• Re: storage with "very high Average Read/Write Request Time"
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• storage with "very high Average Read/Write Request Time"
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• [PATCH] Grow: fix resize of array component size to > 32bits
  • From: Justin Maggard <jmaggard10@xxxxxxxxx>
• Help with raid1 to raid5 reshape after crash
  • From: <shane-kernel@xxxxxx>
• Re: "bitmap file is out of date, doing full recovery"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Problem with a dgaded array (not related to my last question)
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: Kernel says there is not a valid superblock, but there is
  • From: Phillip Susi <phillsusi@xxxxxxxxx>
• Re: dm raid: pointer math issue in super_sync()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm raid: pointer math issue in super_sync()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: dm raid: pointer math issue in super_sync()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [patch] dm raid: pointer math issue in super_sync()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [patch] DM RAID: fix a couple integer overflows
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: How do I set 'write-behind' on existing array?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Kernel says there is not a valid superblock, but there is
  • From: NeilBrown <neilb@xxxxxxx>
• Re: question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
  • From: Jason Keltz <jas@xxxxxxxxxxxx>
• question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
  • From: Jason Keltz <jas@xxxxxxxxxxxx>
• Kernel says there is not a valid superblock, but there is
  • From: Phillip Susi <phillsusi@xxxxxxxxx>
• How do I set 'write-behind' on existing array?
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: Multiple drive failure after stupid mistake. Help needed
  • From: Per-Ola Stenborg <per-ola@xxxxxxxxxxx>
• Re: Multiple drive failure after stupid mistake. Help needed
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Multiple drive failure after stupid mistake. Help needed
  • From: Per-Ola Stenborg <per-ola@xxxxxxxxxxx>
• Re: Multiple drive failure after stupid mistake. Help needed
  • From: Per-Ola Stenborg <per-ola@xxxxxxxxxxx>
• Re: Multiple drive failure after stupid mistake. Help needed
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Multiple drive failure after stupid mistake. Help needed
  • From: Per-Ola Stenborg <per-ola@xxxxxxxxxxx>
• Re: migrate to bad block list
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Fwd: I will pay money for the correct RAID recovery instructions
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Fwd: I will pay money for the correct RAID recovery instructions
  • From: Another Sillyname <anothersname@xxxxxxxxxxxxxx>
• Re: I will pay money for the correct RAID recovery instructions
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: I will pay money for the correct RAID recovery instructions
  • From: Ian Young <ian@xxxxxxxxxxxxxxx>
• Re: I will pay money for the correct RAID recovery instructions
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• I will pay money for the correct RAID recovery instructions
  • From: Ian Young <ian@xxxxxxxxxxxxxxx>
• Re: Preventing automatic start of ARRAY on Kubuntu
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Preventing automatic start of ARRAY on Kubuntu
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: migrate to bad block list
  • From: NeilBrown <neilb@xxxxxxx>
• [GIT PULL REQUEST] md updates for 3.18
  • From: NeilBrown <neilb@xxxxxxx>
• migrate to bad block list
  • From: Michael Ryan <mryan@xxxxxxxxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• [GIT PULL] LLVMLinux patches for v3.18
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] lib/raid6: Add log level to printks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] lib/raid6: Add log level to printks
  • From: Anton Blanchard <anton@xxxxxxxxx>
• mdadm: /dev/sdX2 has wrong raid level.
  • From: Weedy <weedy2887@xxxxxxxxx>
• Re: mdadm --grow with --backup-file does not create backupfile?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: mdadm --grow with --backup-file does not create backupfile?
  • From: NeilBrown <neilb@xxxxxxx>
• mdadm --grow with --backup-file does not create backupfile?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: "bitmap file is out of date, doing full recovery"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Is it safe to shutdown while mdadm --grow is in progress.
  • From: NeilBrown <neilb@xxxxxxx>
• "bitmap file is out of date, doing full recovery"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Good drive got kicked out - does mdadm assemble across suspend/resume like it does across reboots?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Is it safe to shutdown while mdadm --grow is in progress.
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Is it safe to shutdown while mdadm --grow is in progress.
  • From: NeilBrown <neilb@xxxxxxx>
• Is it safe to shutdown while mdadm --grow is in progress.
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• [PATCH] monitor: fix nullptr dereference when get_md_name() returns NULL
  • From: Sergey Vidishev <sergeyv@xxxxxxxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Extremely High mismatch_cnt on RAID1 system
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: writing zeros to bad sector results in persistent read error
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: writing zeros to bad sector results in persistent read error
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Bad sequential performance of RAID5 with a lot of disk seeks
  • From: XiaoNi <xni@xxxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: auto assemble in read-only mode?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: UEFI and mdadm questions.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Extremely High mismatch_cnt on RAID1 system
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: Extremely High mismatch_cnt on RAID1 system
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• Re: Extremely High mismatch_cnt on RAID1 system
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: auto assemble in read-only mode?
  • From: Errol Neal <eneal@xxxxxxxxxxxxxxxxx>
• Re: Bad sequential performance of RAID5 with a lot of disk seeks
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Bad sequential performance of RAID5 with a lot of disk seeks
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: Bad sequential performance of RAID5 with a lot of disk seeks
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Bad sequential performance of RAID5 with a lot of disk seeks
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: Bad sequential performance of RAID5 with a lot of disk seeks
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: auto assemble in read-only mode?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: auto assemble in read-only mode?
  • From: Errol Neal <eneal@xxxxxxxxxxxxxxxxx>
• Bad sequential performance of RAID5 with a lot of disk seeks
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: Cancelling not pausing array check
  • From: Patrik Horník <patrik@xxxxxx>
• Re: Cancelling not pausing array check
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Cancelling not pausing array check
  • From: Patrik Horník <patrik@xxxxxx>
• Re: UEFI and mdadm questions.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Cancelling not pausing array check
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Cancelling not pausing array check
  • From: Patrik Horník <patrik@xxxxxx>
• Re: Cancelling not pausing array check
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Hot replacing device in RAID 6
  • From: Patrik Horník <patrik@xxxxxx>
• Cancelling not pausing array check
  • From: Patrik Horník <patrik@xxxxxx>
• auto assemble in read-only mode?
  • From: Errol Neal <eneal@xxxxxxxxxxxxxxxxx>
• Re: UEFI and mdadm questions.
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: UEFI and mdadm questions.
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: MD Raid1 hangs system on read error (3.10)
  • From: Matthijs Kooijman <matthijs@xxxxxxxx>
• Re: MD Raid1 hangs system on read error (3.10)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 2 disk raid 5 failure
  • From: NeilBrown <neilb@xxxxxxx>
• Re: not enough operational mirrors
  • From: Ian Young <ian@xxxxxxxxxxxxxxx>
• Re: UEFI and mdadm questions.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Hot replacing device in RAID 6
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: UEFI and mdadm questions.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Hot replacing device in RAID 6
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Hot replacing device in RAID 6
  • From: Patrik Horník <patrik@xxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• Re: Please advise, strange "not enough to start the array while not clean"
  • From: Patrik Horník <patrik@xxxxxx>
• Re: 2 disk raid 5 failure
  • From: Jean-Paul Sergent <jpsergent@xxxxxxxxx>
• Re: 2 disk raid 5 failure
  • From: NeilBrown <neilb@xxxxxxx>
• MD Raid1 hangs system on read error (3.10)
  • From: Matthijs Kooijman <matthijs@xxxxxxxx>
• Re: 2 disk raid 5 failure
  • From: Jean-Paul Sergent <jpsergent@xxxxxxxxx>
• Re: 2 disk raid 5 failure
  • From: Jean-Paul Sergent <jpsergent@xxxxxxxxx>
• Re: 2 disk raid 5 failure
  • From: NeilBrown <neilb@xxxxxxx>
• 2 disk raid 5 failure
  • From: Jean-Paul Sergent <jpsergent@xxxxxxxxx>
• Re: raid6 appears not-degraded just after creation
  • From: Anssi Hannula <anssi.hannula@xxxxxx>
• Re: build-sys: do not depend on check_rundir for executables
  • From: NeilBrown <neilb@xxxxxxx>
• raid6 appears not-degraded just after creation
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• build-sys: do not depend on check_rundir for executables
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Extremely High mismatch_cnt on RAID1 system
  • From: Dennis Grant <reccedg@xxxxxxxxx>
• [GIT PULL REQUEST] one last-minute update for md/raid5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: UEFI and mdadm questions.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: [dm-devel] dm-raid: add RAID discard support
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: dm-raid: add RAID discard support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-log-userspace: fix memory leak on failure path in dm_ulog_tfr_init()
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: dm-raid: add RAID discard support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Why MD often doesn't correct read errors?
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: [dm-devel] dm-raid: add RAID discard support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: UEFI and mdadm questions.
  • From: Anthonys Lists <antlists@xxxxxxxxxxxxxxx>
• [PATCH] dm-log-userspace: fix memory leak on failure path in dm_ulog_tfr_init()
  • From: Alexey Khoroshilov <khoroshilov@xxxxxxxxx>
• UEFI and mdadm questions.
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: Andrei Banu <andrei.banu@xxxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• raid1 - ssd, doubts
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: NeilBrown <neilb@xxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: dmadm question
  • From: NeilBrown <neilb@xxxxxxx>
• Re: dmadm question
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: NeilBrown <neilb@xxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: NeilBrown <neilb@xxxxxxx>
• BOUNTY REQUEST: Patch to RAID1/mdadm to DISABLE/ENABLE ALL SYNC ACTIONS, RECOVERY, etc
  • From: Errol Neal <eneal@xxxxxxxxxxxxxxxxx>
• Re: [RESEND PATCH] drivers/md: Use rcu_dereference() for accessing rcu pointer
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• [RESEND PATCH] drivers/md: Use rcu_dereference() for accessing rcu pointer
  • From: Pranith Kumar <bobby.prani@xxxxxxxxx>
• [PATCH] drivers/md: Use rcu_dereference() for accessing rcu pointer
  • From: Pranith Kumar <bobby.prani@xxxxxxxxx>
• Re: [PATCH] dm: sparse: Annotate field with __rcu for checking
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• [PATCH] md, sysfs, LLVMLinux: Remove nested function from bcache sysfs
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL REQUEST] late md/raid1 bug fixes for 3.17
  • From: NeilBrown <neilb@xxxxxxx>
• Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• Re: [GIT PULL REQUEST] late md/raid1 bug fixes for 3.17
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• RE: [PATCH] md: avoid potential long delay under pers_lock
  • From: Chao Yu <chao2.yu@xxxxxxxxxxx>
• RE: [PATCH] md: avoid potential long delay under pers_lock
  • From: Chao Yu <chao2.yu@xxxxxxxxxxx>
• Re: [PATCH] md: avoid potential long delay under pers_lock
  • From: NeilBrown <neilb@xxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] dm: sparse: Annotate field with __rcu for checking
  • From: Pranith Kumar <bobby.prani@xxxxxxxxx>
• Re: [PATCH] md: avoid potential long delay under pers_lock
  • From: Henrique de Moraes Holschuh <hmh@xxxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• [PATCH] md: avoid potential long delay under pers_lock
  • From: Chao Yu <chao2.yu@xxxxxxxxxxx>
• Re: Moving root to raid, weird raid behaviour
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Moving root to raid, weird raid behaviour
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: More 'D' state processes
  • From: Pavel Hofman <pavel.hofman@xxxxxxxxxxx>
• Re: [PATCH 0/5] Fixes for RAID1 resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/5] Fixes for RAID1 resync
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• [GIT PULL REQUEST] late md/raid1 bug fixes for 3.17
  • From: NeilBrown <neilb@xxxxxxx>
• Re: not enough operational mirrors
  • From: Ian Young <ian@xxxxxxxxxxxxxxx>
• Re: [PATCH v4 11/12] security, crypto: LLVMLinux: Remove VLAIS from ima_crypto.c
  • From: Dmitry Kasatkin <d.kasatkin@xxxxxxxxxxx>
• Re: Moving root to raid, weird raid behaviour
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• behind_writes
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• [PATCH v4 05/12] crypto: LLVMLinux: Remove VLAIS from crypto/n2_core.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 02/12] btrfs: LLVMLinux: Remove VLAIS
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 06/12] crypto: LLVMLinux: Remove VLAIS from crypto/omap_sham.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 07/12] crypto: LLVMLinux: Remove VLAIS from crypto/.../qat_algs.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 03/12] crypto: LLVMLinux: Remove VLAIS from crypto/ccp/ccp-crypto-sha.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 08/12] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 04/12] crypto: LLVMLinux: Remove VLAIS from crypto/mv_cesa.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 09/12] crypto: LLVMLinux: Remove VLAIS usage from crypto/hmac.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 11/12] security, crypto: LLVMLinux: Remove VLAIS from ima_crypto.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 12/12] crypto: LLVMLinux: Remove VLAIS usage from crypto/testmgr.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 10/12] crypto: LLVMLinux: Remove VLAIS usage from libcrc32c.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v4 00/12] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
  • From: behanw@xxxxxxxxxxxxxxxxxx
• raid sync speed
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• Re: not enough operational mirrors
  • From: Ian Young <ian@xxxxxxxxxxxxxxx>
• Re: Moving root to raid, weird raid behaviour
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid5 missing disks during chunk size grow
  • From: NeilBrown <neilb@xxxxxxx>
• Re: not enough operational mirrors
  • From: NeilBrown <neilb@xxxxxxx>
• Re: not enough operational mirrors
  • From: Ian Young <ian@xxxxxxxxxxxxxxx>
• Moving root to raid, weird raid behaviour
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: not enough operational mirrors
  • From: Ian Young <ian@xxxxxxxxxxxxxxx>
• Re: raid5 missing disks during chunk size grow
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: raid5 missing disks during chunk size grow
  • From: Martin Senebald <martin@xxxxxxxxxxx>
• Re: raid5 missing disks during chunk size grow
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: raid5 missing disks during chunk size grow
  • From: Martin Senebald <martin@xxxxxxxxxxx>
• Re: raid5 missing disks during chunk size grow
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• raid5 missing disks during chunk size grow
  • From: Martin Senebald <martin@xxxxxxxxxxx>
• Re: Please advise, strange "not enough to start the array while not clean"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Please advise, strange "not enough to start the array while not clean"
  • From: Patrik Horník <patrik@xxxxxx>
• Re: Please advise, strange "not enough to start the array while not clean"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Please advise, strange "not enough to start the array while not clean"
  • From: Patrik Horník <patrik@xxxxxx>
• Re: not enough operational mirrors
  • From: NeilBrown <neilb@xxxxxxx>
• not enough operational mirrors
  • From: Ian Young <ian@xxxxxxxxxxxxxxx>
• Re: What happens with array when external write-intent bitmap fails?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: read error recovery threshold
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Please advise, strange "not enough to start the array while not clean"
  • From: NeilBrown <neilb@xxxxxxx>
• Please advise, strange "not enough to start the array while not clean"
  • From: Patrik Horník <patrik@xxxxxx>
• Re: Raid 1 vs Raid 10 single thread performance
  • From: keld@xxxxxxxxxx
• Re: frequent disk activity with mdadm-3.3
  • From: Marco Schindler <marco.schindler@xxxxxxxxx>
• Re: frequent disk activity with mdadm-3.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: frequent disk activity with mdadm-3.3
  • From: Marco Schindler <marco.schindler@xxxxxxxxx>
• Re: frequent disk activity with mdadm-3.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/5] Fixes for RAID1 resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: grub-probe: "found two disks with the index 3 for RAID md2" after changing superblock 0.9 to 1.0
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1_end_read_request does not retry failed READ from a recovering drive
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1_end_read_request does not retry failed READ from a recovering drive
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [PATCH v3 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: Add disks and convert level 0 to level 5
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Add disks and convert level 0 to level 5
  • From: Michael Muratet <muratetm@xxxxxxxxx>
• Re: [PATCH v3 02/12] btrfs: LLVMLinux: Remove VLAIS
  • From: Chris Mason <clm@xxxxxx>
• Re: [PATCH v3 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: Dmitry Kasatkin <d.kasatkin@xxxxxxxxxxx>
• Re: [PATCH v3 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/5] Fixes for RAID1 resync
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• What happens with array when external write-intent bitmap fails?
  • From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
• Re: Raid 1 vs Raid 10 single thread performance
  • From: keld@xxxxxxxxxx
• Re: Raid 1 vs Raid 10 single thread performance
  • From: Bostjan Skufca <bostjan@xxxxxx>
• Re: grub-probe: "found two disks with the index 3 for RAID md2" after changing superblock 0.9 to 1.0
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: grub-probe: "found two disks with the index 3 for RAID md2" after changing superblock 0.9 to 1.0
  • From: NeilBrown <neilb@xxxxxxx>
• Re: grub-probe: "found two disks with the index 3 for RAID md2" after changing superblock 0.9 to 1.0
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• read error recovery threshold
  • From: Eric Mei <meijia@xxxxxxxxx>
• Re: [PATCH v3 11/12] security, crypto: LLVMLinux: Remove VLAIS from ima_crypto.c
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 11/12] security, crypto: LLVMLinux: Remove VLAIS from ima_crypto.c
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: dmadm question
  • From: "Luke Odom" <luke@xxxxxxxxxxxx>
• Re: frequent disk activity with mdadm-3.3
  • From: Marco Schindler <marco.schindler@xxxxxxxxx>
• Re: [dm-devel] [PATCH v3 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH v3 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: Michał Mirosław <mirqus@xxxxxxxxx>
• Re: Speeding up reading with RAID1 and --write-mostly
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• [PATCH v3 00/12] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 01/12] crypto: LLVMLinux: Add macro to remove use of VLAIS in crypto code
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 03/12] crypto: LLVMLinux: Remove VLAIS from crypto/ccp/ccp-crypto-sha.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 02/12] btrfs: LLVMLinux: Remove VLAIS
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 04/12] crypto: LLVMLinux: Remove VLAIS from crypto/mv_cesa.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 05/12] crypto: LLVMLinux: Remove VLAIS from crypto/n2_core.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 06/12] crypto: LLVMLinux: Remove VLAIS from crypto/omap_sham.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 08/12] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 09/12] crypto: LLVMLinux: Remove VLAIS usage from crypto/hmac.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 07/12] crypto: LLVMLinux: Remove VLAIS from crypto/.../qat_algs.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 10/12] crypto: LLVMLinux: Remove VLAIS usage from libcrc32c.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 11/12] security, crypto: LLVMLinux: Remove VLAIS from ima_crypto.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH v3 12/12] crypto: LLVMLinux: Remove VLAIS usage from crypto/testmgr.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• Re: grub-probe: "found two disks with the index 3 for RAID md2" after changing superblock 0.9 to 1.0
  • From: NeilBrown <neilb@xxxxxxx>
• grub-probe: "found two disks with the index 3 for RAID md2" after changing superblock 0.9 to 1.0
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Speeding up reading with RAID1 and --write-mostly
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Status of discard support in MD RAID
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Status of discard support in MD RAID
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Status of discard support in MD RAID
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Status of discard support in MD RAID
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/5] Fixes for RAID1 resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: seems like a deadlock in workqueue when md do a flush
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: dmadm question
  • From: NeilBrown <neilb@xxxxxxx>
• Re: frequent disk activity with mdadm-3.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Question about RAID1 plug/unplug code
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• seems like a deadlock in workqueue when md do a flush
  • From: Vaughan Cao <vaughan.cao@xxxxxxxxxx>
• Re: Status of discard support in MD RAID
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Speeding up reading with RAID1 and --write-mostly
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Re: Speeding up reading with RAID1 and --write-mostly
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Speeding up reading with RAID1 and --write-mostly
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Re: frequent disk activity with mdadm-3.3
  • From: Marco Schindler <marco.schindler@xxxxxxxxx>
• Re: Status of discard support in MD RAID
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Status of discard support in MD RAID
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Status of discard support in MD RAID
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Raid 1 vs Raid 10 single thread performance
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Question about RAID1 plug/unplug code
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Howto start reshape from 100% when change readonly raid to readwrite
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Status of discard support in MD RAID
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Status of discard support in MD RAID
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: frequent disk activity with mdadm-3.3
  • From: Marco Schindler <marco.schindler@xxxxxxxxx>
• Re: frequent disk activity with mdadm-3.3
  • From: NeilBrown <neilb@xxxxxxx>
• frequent disk activity with mdadm-3.3
  • From: Marco Schindler <marco.schindler@xxxxxxxxx>
• Re: access to old raid1 partitions after reinstall on two new disks
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/5] Fixes for RAID1 resync
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• access to old raid1 partitions after reinstall on two new disks
  • From: system.admin@xxxxxx
• Re: [patch v2 0/6] raid5: automatically batch adjacent full stripe write
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Question about RAID1 plug/unplug code
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Add disks and convert level 0 to level 5
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: [patch v2 0/6] raid5: automatically batch adjacent full stripe write
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid 1 vs Raid 10 single thread performance
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid 1 vs Raid 10 single thread performance
  • From: Bostjan Skufca <bostjan@xxxxxx>
• Re: Raid 1 vs Raid 10 single thread performance
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid 1 vs Raid 10 single thread performance
  • From: Bostjan Skufca <bostjan@xxxxxx>
• Re: [PATCH 0/5] Fixes for RAID1 resync
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Howto start reshape from 100% when change readonly raid to readwrite
  • From: Apple Yin <bravery.apple@xxxxxxxxx>
• Re: Raid 1 vs Raid 10 single thread performance
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Add disks and convert level 0 to level 5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Boot option raid=parttitionable and autodetection
  • From: NeilBrown <neilb@xxxxxxx>
• Boot option raid=parttitionable and autodetection
  • From: Bostjan Skufca <bostjan@xxxxxx>
• Raid 1 vs Raid 10 single thread performance
  • From: Bostjan Skufca <bostjan@xxxxxx>
• Add disks and convert level 0 to level 5
  • From: Michael Muratet <muratetm@xxxxxxxxx>
• [patch v2 6/6] raid5: handle expansion/resync case with stripe batching
  • From: shli@xxxxxxxxxx
• [patch v2 5/6] raid5: handle io error of batch list
  • From: shli@xxxxxxxxxx
• [patch v2 4/6] RAID5: batch adjacent full stripe write
  • From: shli@xxxxxxxxxx
• [patch v2 3/6] raid5: track overwrite disk count
  • From: shli@xxxxxxxxxx
• [patch v2 2/6] raid5: add a new flag to track if a stripe can be batched
  • From: shli@xxxxxxxxxx
• [patch v2 1/6] raid5: use flex_array for scribble data
  • From: shli@xxxxxxxxxx
• [patch v2 0/6] raid5: automatically batch adjacent full stripe write
  • From: shli@xxxxxxxxxx
• Re: Question about RAID1 plug/unplug code
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Question about RAID1 plug/unplug code
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• [PATCH 5/5] md/raid1: update next_resync under resync_lock.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 4/5] md/raid1: Don't use next_resync to determine how far resync has progressed
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 3/5] md/raid1: make sure resync waits for conflicting writes to complete.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 2/5] md/raid1: clean up request counts properly in close_sync()
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 1/5] md/raid1: be more cautious where we read-balance during resync.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 0/5] Fixes for RAID1 resync
  • From: NeilBrown <neilb@xxxxxxx>
• AW: raid5: direct IO and md_wakeup_thread
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: [PATCH] Create.c: Try few more times to stop array after failed creation
  • From: NeilBrown <neilb@xxxxxxx>
• RE: [PATCH] Create.c: Try few more times to stop array after failed creation
  • From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
• Re: Question about RAID1 plug/unplug code
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Question about RAID1 plug/unplug code
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: RAID456 direct I/O write performance
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Mirroring seek optimization resend
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Question about RAID1 plug/unplug code
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1 data corruption during resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID0 size over 2 TB
  • From: "azurIt" <azurit@xxxxxxxx>
• Re: RAID0 size over 2 TB
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID0 size over 2 TB
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID0 size over 2 TB
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Mirroring seek optimization resend
  • From: Robert Long <boblong@xxxxxxxxxxxxxx>
• Fwd: raid1 data corruption during resync
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Question about RAID1 plug/unplug code
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: RAID0 size over 2 TB
  • From: "azurIt" <azurit@xxxxxxxx>
• Re: RAID0 size over 2 TB
  • From: "azurIt" <azurit@xxxxxxxx>
• Re: RAID0 size over 2 TB
  • From: NeilBrown <neilb@xxxxxxx>
• AW: raid5: direct IO and md_wakeup_thread
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: RAID0 size over 2 TB
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: RAID0 size over 2 TB
  • From: "azurIt" <azurit@xxxxxxxx>
• Re: raid1_end_read_request does not retry failed READ from a recovering drive
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID0 size over 2 TB
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid5: direct IO and md_wakeup_thread
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Create.c: Try few more times to stop array after failed creation
  • From: NeilBrown <neilb@xxxxxxx>
• raid1_end_read_request does not retry failed READ from a recovering drive
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [PATCH v2] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: RAID0 size over 2 TB - RAID1
  • From: "azurIt" <azurit@xxxxxxxx>
• RAID0 size over 2 TB
  • From: "azurIt" <azurit@xxxxxxxx>
• AW: AW: RAID456 direct I/O write performance
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: [PATCH v2] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• [PATCH v2] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt
  • From: behanw@xxxxxxxxxxxxxxxxxx
• AW: AW: RAID456 direct I/O write performance
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• raid5: direct IO and md_wakeup_thread
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: ext4 vs btrfs performance on SSD array
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: ext4 vs btrfs performance on SSD array
  • From: Jeff Moyer <jmoyer@xxxxxxxxxx>
• Re: ext4 vs btrfs performance on SSD array
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• [PATCH] Create.c: Try few more times to stop array after failed creation
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: AW: RAID456 direct I/O write performance
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• AW: RAID456 direct I/O write performance
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• RAID456 direct I/O write performance
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: RAID6 rmw - new numbers
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1 data corruption during resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1 data corruption during resync
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Will the write request starve?
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Will the write request starve?
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH] Monitor.c (trivial) Remove bedside manner in email text.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/1] Grow: Report when grow needs metadata update
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1 data corruption during resync
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: raid1 data corruption during resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1 data corruption during resync
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [RFC]RAID5: batch adjacent full stripe write
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: raid1 data corruption during resync
  • From: Eivind Sarto <eivindsarto@xxxxxxxxx>
• Re: ext4 vs btrfs performance on SSD array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1 data corruption during resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH RFC 5/6] apparmor: LLVMLinux: Remove VLAIS
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH RFC 5/6] apparmor: LLVMLinux: Remove VLAIS
  • From: John Johansen <john.johansen@xxxxxxxxxxxxx>
• Re: [PATCH RFC 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH RFC 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
  • From: Marcel Holtmann <marcel@xxxxxxxxxxxx>
• [PATCH RFC 0/6] LLVMLinux: Patches to enable the kernel to be compiled with clang/LLVM
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH RFC 5/6] apparmor: LLVMLinux: Remove VLAIS
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH RFC 1/6] crypto, dm: LLVMLinux: Remove VLAIS usage from dm-crypt
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH RFC 2/6] crypto: LLVMLinux: Remove VLAIS usage from crypto/hmac.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH RFC 6/6] btrfs: LLVMLinux: Remove VLAIS
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH RFC 3/6] crypto: LLVMLinux: Remove VLAIS usage from libcrc32c.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• [PATCH RFC 4/6] crypto: LLVMLinux: Remove VLAIS usage from crypto/testmgr.c
  • From: behanw@xxxxxxxxxxxxxxxxxx
• Re: raid1 data corruption during resync
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: raid1 data corruption during resync
  • From: Eivind Sarto <eivindsarto@xxxxxxxxx>
• [PATCH] Monitor.c (trivial) Remove bedside manner in email text.
  • From: Phil Kauffman <kauffman@xxxxxxxxxxxxxxx>
• Re: raid1 data corruption during resync
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• mdadm patch Monitor.c
  • From: Phil Kauffman <kauffman@xxxxxxxxxxxxxxx>
• Re: raid1 data corruption during resync
  • From: Eivind Sarto <eivindsarto@xxxxxxxxx>
• Re: raid1 data corruption during resync
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: raid1 data corruption during resync
  • From: Eivind Sarto <eivindsarto@xxxxxxxxx>
• Re: ext4 vs btrfs performance on SSD array
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: ext4 vs btrfs performance on SSD array
  • From: Jan Kara <jack@xxxxxxx>