Linux RAID Storage Date Index

• Thread Index

• 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>
• Re: raid1 data corruption during resync
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: ext4 vs btrfs performance on SSD array
  • From: Austin S Hemmelgarn <ahferroin7@xxxxxxxxx>
• Re: ext4 vs btrfs performance on SSD array
  • From: Zack Coffey <clickwir@xxxxxxxxx>
• Re: ext4 vs btrfs performance on SSD array
  • From: "Theodore Ts'o" <tytso@xxxxxxx>
• Re: [RFC]RAID5: batch adjacent full stripe write
  • From: NeilBrown <neilb@xxxxxxx>
• Re: ext4 vs btrfs performance on SSD array
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Converting RAID5 to RAID0
  • From: Michael Muratet <muratetm@xxxxxxxxx>
• Re: Converting RAID5 to RAID0
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Converting RAID5 to RAID0
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• RAID6 rmw - new numbers
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Converting RAID5 to RAID0
  • From: Mike Muratet <muratetm@xxxxxxxxx>
• Re: Seeking help to get a failed RAID5 system back to life
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Seeking help to get a failed RAID5 system back to life
  • From: Fabio Bacigalupo <info1@xxxxxxxxxxxx>
• Installing CentOS7 on to MDADM RAID1 or RAID10
  • From: Maurice Hilarius <maurice@xxxxxxxxxxxx>
• Re: Good hardware for mdadm
  • From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
• Re: Good hardware for mdadm
  • From: Paul van der Vlis <paul@xxxxxxxxxxxxx>
• Re: Good hardware for mdadm
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Good hardware for mdadm
  • From: Paul van der Vlis <paul@xxxxxxxxxxxxx>
• Re: Good hardware for mdadm
  • From: Paul van der Vlis <paul@xxxxxxxxxxxxx>
• Re: Good hardware for mdadm
  • From: Paul van der Vlis <paul@xxxxxxxxxxxxx>
• Re: Good hardware for mdadm
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Good hardware for mdadm
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Good hardware for mdadm
  • From: Adam Talbot <ajtalbot1@xxxxxxxxx>
• Re: Good hardware for mdadm
  • From: Paul van der Vlis <paul@xxxxxxxxxxxxx>
• [PATCH 1/1] Grow: Report when grow needs metadata update
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Good hardware for mdadm
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Good hardware for mdadm
  • From: Paul van der Vlis <paul@xxxxxxxxxxxxx>
• raid1 data corruption during resync
  • From: Eivind Sarto <eivindsarto@xxxxxxxxx>
• Re: Units for mdadm --data-offset ?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Units for mdadm --data-offset ?
  • From: "Patrick J. LoPresti" <lopresti@xxxxxxxxx>
• Re: Seeking help to get a failed RAID5 system back to life
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Seeking help to get a failed RAID5 system back to life
  • From: Fabio Bacigalupo <info1@xxxxxxxxxxxx>
• Re: Seeking help to get a failed RAID5 system back to life
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: NeilBrown <neilb@xxxxxxx>
• Mirroring seek optimization
  • From: Robert Long <boblong@xxxxxxxxxxxxxx>
• Failed drive in RAID10 using Intel IHC
  • From: "Glen Whittenberg" <glenewhittenberg@xxxxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: NeilBrown <neilb@xxxxxxx>
• Seeking help to get a failed RAID5 system back to life
  • From: Fabio Bacigalupo <info1@xxxxxxxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Adam Talbot <ajtalbot1@xxxxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Add BBL to existing array
  • From: Peter Hoeg <peter@xxxxxxxx>
• Re: Add BBL to existing array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Add BBL to existing array
  • From: Peter Hoeg <peter@xxxxxxxx>
• Re: Add BBL to existing array
  • From: NeilBrown <neilb@xxxxxxx>
• Add BBL to existing array
  • From: Peter Hoeg <peter@xxxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: [PATCH] Memory leak once alloc superblock page failed
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: AW: [PATCH v3 5/6] md/raid5: activate raid6 rmw feature
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• AW: [PATCH v3 5/6] md/raid5: activate raid6 rmw feature
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: [PATCH v3 5/6] md/raid5: activate raid6 rmw feature
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: RAID partitions, or RAID disks and partition array?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• [PATCH v3 6/6] md/raid5: introduce configuration option rmw_level
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• [PATCH v3 5/6] md/raid5: activate raid6 rmw feature
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• [PATCH v3 4/6] md/raid6 algorithms: xor_syndrome() for SSE2
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• [PATCH v3 3/6] md/raid6 algorithms: xor_syndrome() for generic int
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• [PATCH v3 2/6] md/raid6 algorithms: improve test program
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• [PATCH v3 1/6] md/raid6 algorithms: delta syndrome functions
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• [PATCH v3 0/6] md/raid6: support read-modify-write
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: NeilBrown <neilb@xxxxxxx>
• RE: Shrinking number of devices on a RAID-10 (near 2) array
  • From: Craig Curtin <craigc@xxxxxxxxxxxxx>
• Re: Shrinking number of devices on a RAID-10 (near 2) array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Mirroring seek optimization
  • From: NeilBrown <neilb@xxxxxxx>
• Mirroring seek optimization
  • From: Robert Long <boblong@xxxxxxxxxxxxxx>
• Re: RAID partitions, or RAID disks and partition array?
  • From: Adam Talbot <ajtalbot1@xxxxxxxxx>
• Shrinking number of devices on a RAID-10 (near 2) array
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: RAID partitions, or RAID disks and partition array?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID partitions, or RAID disks and partition array?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID partitions, or RAID disks and partition array?
  • From: Adam Talbot <ajtalbot1@xxxxxxxxx>
• Re: RAID partitions, or RAID disks and partition array?
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• RAID partitions, or RAID disks and partition array?
  • From: Adam Talbot <ajtalbot1@xxxxxxxxx>
• ANNOUNCE: mdadm 3.3.2 - A tool for managing md Soft RAID under Linux
  • From: NeilBrown <neilb@xxxxxxx>
• AW: [PATCH v2 0/6] raid6: support read-modify-write
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: The parallel make patch for mdadm
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH v2 0/6] raid6: support read-modify-write
  • From: NeilBrown <neilb@xxxxxxx>
• Re: The parallel make patch for mdadm
  • From: Samuli Suominen <ssuominen@xxxxxxxxxx>
• performance degrade with RAID6 against RAID0
  • From: "Mandar Joshi" <mandar.joshi@xxxxxxxxxxxxxx>
• Re: Correct RAID options
  • From: Chris Knipe <savage@xxxxxxxxxxxxx>
• Re: [PATCH v1 0/0] raid5: fix init_stripe() inconsistencies
  • From: NeilBrown <neilb@xxxxxxx>
• AW: [PATCH v1 0/0] raid5: fix init_stripe() inconsistencies
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: Correct RAID options
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Correct RAID options
  • From: Chris Schanzle <mdadm@xxxxxxxxxxxxxxxxx>
• AW: [PATCH v2 0/6] raid6: support read-modify-write
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• RE: Correct RAID options
  • From: Craig Curtin <craigc@xxxxxxxxxxxxx>
• Re: [PATCH v1 0/0] raid5: fix init_stripe() inconsistencies
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md: fix for wrong state in superblock issue in assemble process
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Correct RAID options
  • From: Chris Knipe <savage@xxxxxxxxxxxxx>
• RE: Correct RAID options
  • From: Craig Curtin <craigc@xxxxxxxxxxxxx>
• Re: Correct RAID options
  • From: Chris Knipe <savage@xxxxxxxxxxxxx>
• Re: Correct RAID options
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: [PATCH v2 0/6] raid6: support read-modify-write
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Correct RAID options
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• RE: Correct RAID options
  • From: Craig Curtin <craigc@xxxxxxxxxxxxx>
• Correct RAID options
  • From: Chris Knipe <savage@xxxxxxxxxxxxx>
• AW: [PATCH v1 0/8] raid6: support read-modify-write
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• [PATCH v2 6/6] raid5: introduce configuration option rmw_level
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• [PATCH v2 3/6] raid6 algorithms: xor_syndrome() for generic int
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• [PATCH v2 5/6] raid6: activate rmw feature
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• [PATCH v2 4/6] raid6 algorithms: xor_syndrome() for SSE2
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• [PATCH v2 2/6] raid6 algorithms: improve test program
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• [PATCH v2 1/6] raid6 algorithms: delta syndrome functions
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• [PATCH v2 0/6] raid6: support read-modify-write
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: Can I replace raid6 disk using dd?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Can I replace raid6 disk using dd?
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• [GIT PULL REQUEST] bugfixes for md.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH v1 0/8] raid6: support read-modify-write
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Can I replace raid6 disk using dd?
  • From: Killian De Volder <killian.de.volder@xxxxxxxxxxx>
• Re: Full stripe write in RAID6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid5.c internal stripe layout
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Can I replace raid6 disk using dd?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Can I replace raid6 disk using dd?
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Can I replace raid6 disk using dd?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• raid5.c internal stripe layout
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: ALERT: md/raid6 data corruption risk.
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• RE: Full stripe write in RAID6
  • From: "Mandar Joshi" <mandar.joshi@xxxxxxxxxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Adam Talbot <ajtalbot1@xxxxxxxxx>
• [RFC]RAID5: batch adjacent full stripe write
  • From: Shaohua Li <shli@xxxxxxxxxx>
• ALERT: md/raid6 data corruption risk.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: memory leak with linux-3.14.16
  • From: NeilBrown <neilb@xxxxxxx>
• Re: memory leak with linux-3.14.16
  • From: mdraid.pkoch@xxxxxxxx (Peter Koch)
• Re: memory leak with linux-3.14.16
  • From: NeilBrown <neilb@xxxxxxx>
• Re: memory leak with linux-3.14.16
  • From: mdraid.pkoch@xxxxxxxx (Peter Koch)
• Re: memory leak with linux-3.14.16
  • From: NeilBrown <neilb@xxxxxxx>
• memory leak with linux-3.14.16
  • From: mdraid.pkoch@xxxxxxxx (Peter Koch)
• Re: RAID10-shrink does not work
  • From: mdraid.pkoch@xxxxxxxx (Peter Koch)
• Re: Unable to re-add a disk after a reboot.
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Unable to re-add a disk after a reboot.
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Unable to re-add a disk after a reboot.
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Unable to re-add a disk after a reboot.
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Unable to re-add a disk after a reboot.
  • From: NeilBrown <neilb@xxxxxxx>
• Unable to re-add a disk after a reboot.
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Adam Talbot <ajtalbot1@xxxxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Adam Talbot <ajtalbot1@xxxxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Adam Talbot <ajtalbot1@xxxxxxxxx>
• Re: How to use --freeze-reshape and is it safe?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: How to use --freeze-reshape and is it safe?
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: How to use --freeze-reshape and is it safe?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bigger stripe size
  • From: NeilBrown <neilb@xxxxxxx>
• AW: Bigger stripe size
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: How to use --freeze-reshape and is it safe?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Raid5 to raid6 reshape or recreate?
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: How to use --freeze-reshape and is it safe?
  • From: NeilBrown <neilb@xxxxxxx>
• How to use --freeze-reshape and is it safe?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Bigger stripe size
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 to raid6 reshape or recreate?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Raid5 to raid6 reshape or recreate?
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Raid5 to raid6 reshape or recreate?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Adam Talbot <ajtalbot1@xxxxxxxxx>
• [PATCH v1 0/0] raid5: fix init_stripe() inconsistencies
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: Raid5 to raid6 reshape or recreate?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Raid5 to raid6 reshape or recreate?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Adam Talbot <ajtalbot1@xxxxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• Re: RAID6 - RMW logic
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Making spare device into active
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Can Jeuleers <can.jeuleers@xxxxxxxxx>
• Re: Clone failed
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
• Re: Sleepy drives and MD RAID 6
  • From: Adam Talbot <ajtalbot1@xxxxxxxxx>
• Sleepy drives and MD RAID 6
  • From: Adam Talbot <ajtalbot1@xxxxxxxxx>
• Reads from write-mostly HDD instead from _non_ write-mostly SDD as expected?
  • From: Mateusz Korniak <mateusz-lists@xxxxxxxxxxxxxx>
• Re: Mdadm misuse or bug ? mdadm: Cannot find 8:18: No such file or directory
  • From: Killian De Volder <killian.de.volder@xxxxxxxxxxx>
• [GIT PULL REQUEST] md updates for 3.17
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID10-shrink does not work
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Clone failed
  • From: NeilBrown <neilb@xxxxxxx>
• Clone failed
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Mdadm misuse or bug ? mdadm: Cannot find 8:18: No such file or directory
  • From: NeilBrown <neilb@xxxxxxx>
• add vs. re-add
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• AW: RAID6 - RMW logic
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• RAID10-shrink does not work
  • From: mdraid.pkoch@xxxxxxxx (Peter Koch)
• [PATCH v1 8/8] raid6 algorithms: xor_syndrome() for SSE2
  • From: <stockhausen@xxxxxxxxxxx>
• [PATCH v1 7/8] raid6 algorithms: xor_syndrome() for generic int
  • From: <stockhausen@xxxxxxxxxxx>
• [PATCH v1 6/8] raid6: activate rmw feature
  • From: <stockhausen@xxxxxxxxxxx>
• [PATCH v1 5/8] async_pq: add logic for improved rmw syndrome calculation
  • From: <stockhausen@xxxxxxxxxxx>
• [PATCH v1 4/8] raid6 algorithms: show xor_syndrome() benchmarks on startup
  • From: <stockhausen@xxxxxxxxxxx>
• [PATCH v1 3/8] raid6 algorithms: improve test program
  • From: <stockhausen@xxxxxxxxxxx>
• [PATCH v1 2/8] raid6 algorithms: delta syndrome dummy functions
  • From: <stockhausen@xxxxxxxxxxx>
• [PATCH v1 1/8] raid5: introduce configuration option rmw_level
  • From: <stockhausen@xxxxxxxxxxx>
• [PATCH v1 0/8] raid6: support read-modify-write
  • From: <stockhausen@xxxxxxxxxxx>
• Re: Making spare device into active
  • From: Patrik Horník <patrik@xxxxxx>
• Re: Mdadm misuse or bug ? mdadm: Cannot find 8:18: No such file or directory
  • From: Killian De Volder <killian.de.volder@xxxxxxxxxxx>
• Re: Mdadm misuse or bug ? mdadm: Cannot find 8:18: No such file or directory
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Mdadm misuse or bug ? mdadm: Cannot find 8:18: No such file or directory
  • From: Killian De Volder <killian.de.volder@xxxxxxxxxxx>
• Re: Mdadm misuse or bug ? mdadm: Cannot find 8:18: No such file or directory
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID10-reshape crashed due to memory allocation problem
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Making spare device into active
  • From: NeilBrown <neilb@xxxxxxx>
• Mdadm misuse or bug ? mdadm: Cannot find 8:18: No such file or directory
  • From: Killian De Volder <killian.de.volder@xxxxxxxxxxx>
• Making spare device into active
  • From: Patrik Horník <patrik@xxxxxx>
• Fwd: Making spare device into active
  • From: Patrik Horník <patrik@xxxxxx>
• parallel access to RAID10-array
  • From: mdraid.pkoch@xxxxxxxx (Peter Koch)
• parallel access to RAID10-array
  • From: mdraid.pkoch@xxxxxxxx (Peter Koch)
• RAID10-reshape crashed due to memory allocation problem
  • From: mdraid.pkoch@xxxxxxxx (Peter Koch)
• RAID10-reshape crashed due to memory allocation problem
  • From: mdraid.pkoch@xxxxxxxx (Peter Koch)
• Re: [PATCH] Recovery speed is wrong
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: After reshaping raid1 to raid0 with bitmap, then stop md panic
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: After reshaping raid1 to raid0 with bitmap, then stop md panic
  • From: NeilBrown <neilb@xxxxxxx>
• Add drives and restripe performance
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: RAID10-reshape crashed due to memory allocation problem
  • From: NeilBrown <neilb@xxxxxxx>
• Re: need expert advice for growing raid10-array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Recovery speed is wrong
  • From: NeilBrown <neilb@xxxxxxx>
• RAID10-reshape crashed due to memory allocation problem
  • From: mdraid.pkoch@xxxxxxxx (Peter Koch)
• Re: Status of Tripe Parity RAID
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• [PATCH] Recovery speed is wrong
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: After reshaping raid1 to raid0 with bitmap, then stop md panic
  • From: NeilBrown <neilb@xxxxxxx>
• Re: One patch just review the code
  • From: NeilBrown <neilb@xxxxxxx>
• Re: One patch just review the code
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: After reshaping raid1 to raid0 with bitmap, then stop md panic
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Are we forced to use bad blocks list?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re[3]: Found duplicate PV: using /dev/sda3 not /dev/md1
  • From: Rainer Fügenstein <rfu@xxxxxxxxxx>
• [PATCH] IMSM: do not use comma expression for simple assignments
  • From: Jürg Billeter <j@xxxxxxxxx>
• need expert advice for growing raid10-array
  • From: mdraid.pkoch@xxxxxxxx (Peter Koch)
• stray raid10 with 9 hdd with -n3 layout
  • From: luvar@xxxxxxxxxxxx
• Re: Full stripe write in RAID6
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Full stripe write in RAID6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: One patch just review the code
  • From: NeilBrown <neilb@xxxxxxx>
• Re: After reshaping raid1 to raid0 with bitmap, then stop md panic
  • From: NeilBrown <neilb@xxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Full stripe write in RAID6
  • From: "Mandar Joshi" <mandar.joshi@xxxxxxxxxxxxxx>
• One patch just review the code
  • From: Xiao Ni <xni@xxxxxxxxxx>
• After reshaping raid1 to raid0 with bitmap, then stop md panic
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] V2 cast print arguments in super-ddf.c
  • From: NeilBrown <neilb@xxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• [PATCH] V2 cast print arguments in super-ddf.c
  • From: Michel Normand <normand@xxxxxxxxxxxxxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: Are we forced to use bad blocks list?
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• [PATCH] cast print arguments in super-ddf.c
  • From: Michel Normand <normand@xxxxxxxxxxxxxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: NeilBrown <neilb@xxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Are we forced to use bad blocks list?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 - RMW logic
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Status of Tripe Parity RAID
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 1/2 v2]RAID5: make stripe size configurable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: NeilBrown <neilb@xxxxxxx>
• raid5: introduce rmw_level option
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Status of Tripe Parity RAID
  • From: Ronny Egner <ronnyegner@xxxxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/5] Add __designated_init, wrapping __attribute__((designated_init))
  • From: josh@xxxxxxxxxxxxxxxx
• Re: [PATCH 1/5] Add __designated_init, wrapping __attribute__((designated_init))
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/5] raid: Require designated initialization of structures
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [PATCH 2/5] raid: Require designated initialization of structures
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 1/5] Add __designated_init, wrapping __attribute__((designated_init))
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• [PATCH 2/5] raid: Require designated initialization of structures
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• [PATCH 3/5] fs: Require designated initialization of structures
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• [PATCH 4/5] ftrace: Require designated initialization of structures
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• [PATCH 5/5] include/linux/interrupt.h: Require designated initialization of structures
  • From: Josh Triplett <josh@xxxxxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH] dm bufio: fully initialize shrinker
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• [PATCH] dm bufio: fully initialize shrinker
  • From: Greg Thelen <gthelen@xxxxxxxxxx>
• Are we forced to use bad blocks list?
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• AW: RAID6 - RMW logic
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: RAID6 - RMW logic
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 - RMW logic
  • From: NeilBrown <neilb@xxxxxxx>
• RAID6 - RMW logic
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: On URE and RAID rebuild - again!
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• On URE and RAID rebuild - again!
  • From: Gionatan Danti <g.danti@xxxxxxxxxx>
• Re: [PATCH] md/raid1: always set MD_RECOVERY_INTR flag in raid1 error handler to avoid potential data corruption
  • From: NeilBrown <neilb@xxxxxxx>
• AW: Crash during recover
  • From: "Matthias Appel" <appel.matthias@xxxxxxxxx>
• Re: Crash during recover
  • From: NeilBrown <neilb@xxxxxxx>
• Crash during recover
  • From: "Matthias Appel" <appel.matthias@xxxxxxxxx>
• Re: [PATCH] md/raid1: always set MD_RECOVERY_INTR flag in raid1 error handler to avoid potential data corruption
  • From: jiao hui <jiaohui@xxxxxxxxxxxxx>
• Re: changing to fewer larger disks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md/raid1: always set MD_RECOVERY_INTR flag in raid1 error handler to avoid potential data corruption
  • From: NeilBrown <neilb@xxxxxxx>
• changing to fewer larger disks
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [PATCH] md/raid1: always set MD_RECOVERY_INTR flag in raid1 error handler to avoid potential data corruption
  • From: jiao hui <jiaohui@xxxxxxxxxxxxx>
• [PATCH] md/raid1: always set MD_RECOVERY_INTR flag in raid1 error handler to avoid potential data corruption
  • From: jiao hui <jiaohui@xxxxxxxxxxxxx>
• Re: Fedora 20 RAID 6 errors on rebuild / check / repair
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Re: udev 215 creates inactive MD devices upon stopping them
  • From: NeilBrown <neilb@xxxxxxx>
• Re: udev 215 creates inactive MD devices upon stopping them
  • From: Kay Sievers <kay@xxxxxxxx>
• Re: Problem with RAID-5 not adding disks
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Fedora 20 RAID 6 errors on rebuild / check / repair
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Re: Problem with RAID-5 not adding disks
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Problem with RAID-5 not adding disks
  • From: Theophanis Kontogiannis <tkonto@xxxxxxxxx>
• Re: udev 215 creates inactive MD devices upon stopping them
  • From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: Problem with RAID-5 not adding disks
  • From: Theophanis Kontogiannis <tkonto@xxxxxxxxx>
• udev 215 creates inactive MD devices upon stopping them
  • From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• 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: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: Fedora 20 RAID 6 errors on rebuild / check / repair
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• Re: Fedora 20 RAID 6 errors on rebuild / check / repair
  • From: Kay Diederichs <kay.diederichs@xxxxxxxxxxxxxxx>
• Fedora 20 RAID 6 errors on rebuild / check / repair
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Re: Problem with RAID-5 not adding disks
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Problem with RAID-5 not adding disks
  • From: Theophanis Kontogiannis <tkonto@xxxxxxxxx>
• [patch 1/2 v2]RAID5: make stripe size configurable
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 2/2 v2]raid5: add a sysfs entry to change stripe size
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Problem with RAID-5 not adding disks
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Problem with RAID-5 not adding disks
  • From: Theophanis Kontogiannis <tkonto@xxxxxxxxx>
• Re: Booting after Debian upgrade: /dev/md5 does not exist
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Booting after Debian upgrade: /dev/md5 does not exist
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Booting after Debian upgrade: /dev/md5 does not exist
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: SOLVED Booting after Debian upgrade: /dev/md5 does not exist
  • From: Ron Leach <ronleach@xxxxxxxxx>
• Re: Booting after Debian upgrade: /dev/md5 does not exist
  • From: Ron Leach <ronleach@xxxxxxxxx>
• Re: Booting after Debian upgrade: /dev/md5 does not exist
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Booting after Debian upgrade: /dev/md5 does not exist
  • From: Ron Leach <ronleach@xxxxxxxxx>
• The problem that trim is malfunction at the present of DM-layer
  • From: Chia-Hung Chang <fredchang.tc@xxxxxxxxx>
• Re: Booting after Debian upgrade: /dev/md5 does not exist
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Booting after Debian upgrade: /dev/md5 does not exist
  • From: Ron Leach <ronleach@xxxxxxxxx>
• Re: Possible leak during reshaping layout
  • From: Kenny Root <kenny@xxxxxxxxx>
• RE: [PATCH] IMSM: move "validate_container_imsm" to be included in mdassemble
  • From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
• Re: [PATCH] IMSM: move "validate_container_imsm" to be included in mdassemble
  • From: Samuli Suominen <ssuominen@xxxxxxxxxx>
• Re: Drive replace question
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Possible leak during reshaping layout
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] IMSM: move "validate_container_imsm" to be included in mdassemble
  • From: NeilBrown <neilb@xxxxxxx>
• dm-cache-policy-mq.c
  • From: Nick Krause <xerofoify@xxxxxxxxx>
• Possible leak during reshaping layout
  • From: Kenny Root <kenny@xxxxxxxxx>
• Re: Two Questions about Linux MD
  • From: NeilBrown <neilb@xxxxxxx>
• Fwd: Re: Two Questions about Linux MD
  • From: Killian De Volder <killian.de.volder@xxxxxxxxxxx>
• Re: Two Questions about Linux MD
  • From: Killian De Volder <killian.de.volder@xxxxxxxxxxx>
• RE: [REGRESSION] mdadm git fails to compile with "make mdassemble" after 0c21b485e4beb7bcfe631412a231f7c1ea1067bc
  • From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
• [PATCH] IMSM: move "validate_container_imsm" to be included in mdassemble
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Two Questions about Linux MD
  • From: Henry Cai <henryplusplus@xxxxxxxxx>
• [REGRESSION] mdadm git fails to compile with "make mdassemble" after 0c21b485e4beb7bcfe631412a231f7c1ea1067bc
  • From: Samuli Suominen <ssuominen@xxxxxxxxxx>
• Re: [PATCH] Parallel make bug in Makefile of mdadm-3.3.1 (corrupted udev rules and/or systemd services)
  • From: Samuli Suominen <ssuominen@xxxxxxxxxx>
• Re: Unable to reduce raid size.
  • From: Killian De Volder <killian.de.volder@xxxxxxxxxxx>
• Re: Unable to reduce raid size.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Unable to reduce raid size.
  • From: Killian De Volder <killian.de.volder@xxxxxxxxxxx>
• Re: Unable to reduce raid size.
  • From: NeilBrown <neilb@xxxxxxx>
• Unable to reduce raid size.
  • From: Killian De Volder <killian.de.volder@xxxxxxxxxxx>
• Re: [PATCH] Parallel make bug in Makefile of mdadm-3.3.1 (corrupted udev rules and/or systemd services)
  • From: Samuli Suominen <ssuominen@xxxxxxxxxx>
• Re: [PATCH] Parallel make bug in Makefile of mdadm-3.3.1 (corrupted udev rules and/or systemd services)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Parallel make bug in Makefile of mdadm-3.3.1 (corrupted udev rules and/or systemd services)
  • From: Samuli Suominen <ssuominen@xxxxxxxxxx>
• [PATCH] Parallel make bug in Makefile of mdadm-3.3.1 (corrupted udev rules and/or systemd services)
  • From: Samuli Suominen <ssuominen@xxxxxxxxxx>
• Re: [PATCH] Grow: Do not try to restart if reshape is running
  • From: NeilBrown <neilb@xxxxxxx>
• [patch 1/1] raid0: prevent unaligned discard requests
  • From: Eivind Sarto <eivindsarto@xxxxxxxxx>
• [PATCH] Grow: Do not try to restart if reshape is running
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• re: raid5: offload stripe handle to workqueue
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: How to fix this superblock?
  • From: Pete <psid@xxxxxxxxxxxxxxxx>
• Re: Identify actual drives/partitions behind RAID
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Identify actual drives/partitions behind RAID
  • From: Sachin Garg <sgarg.bugreporter@xxxxxxxxx>
• Re: RAID6 questions (mdadm 3.2.6/3.3.x)
  • From: Vlad Dobrotescu <vlad@xxxxxxxxxxxxx>
• Re: RAID6 questions (mdadm 3.2.6/3.3.x)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 questions (mdadm 3.2.6/3.3.x)
  • From: Vlad Dobrotescu <vlad@xxxxxxxxxxxxx>
• Re: Fwd: Recovering RAID5 array from multiple disk failure with different partition sizes
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID6 questions (mdadm 3.2.6/3.3.x)
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID6 questions (mdadm 3.2.6/3.3.x)
  • From: Vlad Dobrotescu <vlad@xxxxxxxxxxxxx>
• Re: RAID6 questions (mdadm 3.2.6/3.3.x)
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Partitioning on top of raid mirror device questions.
  • From: "Wilson, Jonathan" <i400s@xxxxxxxxxxx>
• Re: RAID6 questions (mdadm 3.2.6/3.3.x)
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: RAID6 questions (mdadm 3.2.6/3.3.x)
  • From: Vlad Dobrotescu <vlad@xxxxxxxxxxxxx>
• Re: RAID6 questions (mdadm 3.2.6/3.3.x)
  • From: Vlad Dobrotescu <vlad@xxxxxxxxxxxxx>
• Re: RAID6 questions (mdadm 3.2.6/3.3.x)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 questions (mdadm 3.2.6/3.3.x)
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• RAID6 questions (mdadm 3.2.6/3.3.x)
  • From: Vlad Dobrotescu <vlad@xxxxxxxxxxxxx>
• Drive replace question
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• Re: Partitioning on top of raid mirror device questions.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Fwd: Recovering RAID5 array from multiple disk failure with different partition sizes
  • From: Florian Spickenreither <florian.spickenreither@xxxxxxxxx>
• Re: [patch 1/2]RAID5: make stripe size configurable
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Partitioning on top of raid mirror device questions.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Partitioning on top of raid mirror device questions.
  • From: Wilson Jonathan <i400s@xxxxxxxxxxx>
• Re: [patch 1/2]RAID5: make stripe size configurable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: no automatic resync after device disconnect then reconnect
  • From: NeilBrown <neilb@xxxxxxx>
• Re: no automatic resync after device disconnect then reconnect
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: no automatic resync after device disconnect then reconnect
  • From: NeilBrown <neilb@xxxxxxx>
• Re: no automatic resync after device disconnect then reconnect
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• no automatic resync after device disconnect then reconnect
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: dm: fix an error code in local_init()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [patch] dm: fix an error code in local_init()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] Forbid merging with partially assembled IMSM array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Grow: Do not use grow-continue unit file if reshape is starting
  • From: NeilBrown <neilb@xxxxxxx>
• [patch 2/2]raid5: add a sysfs entry to change stripe size
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 1/2]RAID5: make stripe size configurable
  • From: Shaohua Li <shli@xxxxxxxxxx>
• RE: [PATCH] Grow: Do not use grow-continue unit file if reshape is starting
  • From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
• Re: Re[6]: RAID 6 crashes system when being accessed
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: [PATCH] Grow: Do not use grow-continue unit file if reshape is starting
  • From: NeilBrown <neilb@xxxxxxx>
• Re[6]: RAID 6 crashes system when being accessed
  • From: "Justin Stephenson" <justin@xxxxxxxxxxxxxxxxx>
• RE: Poor performance with raid 0 with 2 devices at partition level
  • From: Stephen Thomas <scjthm@xxxxxxxx>
• Poor performance with raid 0 with 2 devices at partition level
  • From: Stephen Thomas <scjthm@xxxxxxxx>
• Re: Re[4]: RAID 6 crashes system when being accessed
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re[4]: RAID 6 crashes system when being accessed
  • From: "Justin Stephenson" <justin@xxxxxxxxxxxxxxxxx>
• Re: Re[2]: RAID 6 crashes system when being accessed
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re[2]: RAID 6 crashes system when being accessed
  • From: "Justin Stephenson" <justin@xxxxxxxxxxxxxxxxx>
• Showing my appreciation for your past effort-kindly claim your ATM CARD !!
  • From: Andre Lampard <alampard03@xxxxxxxxx>
• Re: RAID 6 crashes system when being accessed
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• RAID 6 crashes system when being accessed
  • From: "Justin Stephenson" <justin@xxxxxxxxxxxxxxxxx>
• [PATCH] Grow: Do not use grow-continue unit file if reshape is starting
  • From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
• [GIT PULL REQUEST] two minor bugfixes for md in 3.16.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: Pedro Teixeira <finas@xxxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: Pedro Teixeira <finas@xxxxxxxx>
• Re: PATCH: RAID10-layout-descriptions
  • From: keld@xxxxxxxxxx
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: Pedro Teixeira <finas@xxxxxxxx>
• Re: PATCH: RAID10-layout-descriptions
  • From: NeilBrown <neilb@xxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: Pedro Teixeira <finas@xxxxxxxx>
• Fwd: strange problem with raid6 read errors on active non-degraded array
  • From: Pedro Teixeira <finas@xxxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: Lars Täuber <taeuber@xxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: Pedro Teixeira <finas@xxxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: Pedro Teixeira <finas@xxxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: Pedro Teixeira <finas@xxxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: Pedro Teixeira <finas@xxxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: Pedro Teixeira <finas@xxxxxxxx>
• Re: strange problem with raid6 read errors on active non-degraded array
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• strange problem with raid6 read errors on active non-degraded array
  • From: Pedro Teixeira <finas@xxxxxxxx>
• Re: raid5 (re)-add recovery data corruption
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid5 (re)-add recovery data corruption
  • From: Bill <billstuff2001@xxxxxxxxxxxxx>
• RE: [PATCH] Forbid merging with partially assembled IMSM array
  • From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
• Re: [dm-devel] [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: raid5 (re)-add recovery data corruption
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid5 (re)-add recovery data corruption
  • From: NeilBrown <neilb@xxxxxxx>
• Re: writing zeros to bad sector results in persistent read error
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: writing zeros to bad sector results in persistent read error
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: RAID newbie, 1 vs 5, chunk sizes
  • From: Nuno Magalhães <nunomagalhaes@xxxxxxxxx>
• Re: writing zeros to bad sector results in persistent read error
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: raid5 (re)-add recovery data corruption
  • From: Bill <billstuff2001@xxxxxxxxxxxxx>
• Re: Understanding raid array status: Active vs Clean
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Understanding raid array status: Active vs Clean
  • From: George Duffield <forumscollective@xxxxxxxxx>
• [PATCH] dm-io: Fix a race condition in the wake up code for sync_io
  • From: Minfei Huang <huangminfei@xxxxxxxxx>
• Re: dm-io: Prevent the danging point of the sync io callback function
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [dm-devel] [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: dm-io: Prevent the danging point of the sync io callback function
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [dm-devel] [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [dm-devel] [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Deadlock/high load
  • From: Alin Dobre <alin.dobre@xxxxxxxxxxxxxxxx>
• Re: [dm-devel] [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• [PATCH] dm-io: Prevent the danging point of the sync io callback function
  • From: Minfei Huang <huangminfei@xxxxxxxxx>
• Re: sd_setup_discard_cmnd: BUG: unable to handle kernel NULL pointer dereference at (null)
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: sd_setup_discard_cmnd: BUG: unable to handle kernel NULL pointer dereference at (null)
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: [PATCH] Forbid merging with partially assembled IMSM array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: sd_setup_discard_cmnd: BUG: unable to handle kernel NULL pointer dereference at (null)
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: sd_setup_discard_cmnd: BUG: unable to handle kernel NULL pointer dereference at (null)
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• Re: Fwd: Adding a new drive to an array
  • From: George Duffield <forumscollective@xxxxxxxxx>
• Re: Fwd: Adding a new drive to an array
  • From: George Duffield <forumscollective@xxxxxxxxx>
• Re: [RFC PATCH 0/4] md/mdadm: introduce request function mode support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: sd_setup_discard_cmnd: BUG: unable to handle kernel NULL pointer dereference at (null)
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Fwd: Adding a new drive to an array
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Fwd: Adding a new drive to an array
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Restoring a RAID 10 disk array
  • From: Theodotos Andreou <theo@xxxxxxxxxxxx>
• Fwd: Adding a new drive to an array
  • From: George Duffield <forumscollective@xxxxxxxxx>
• Restoring a RAID 10 disk array
  • From: Theodotos Andreou <theo@xxxxxxxxxxxx>
• Re: raid5 (re)-add recovery data corruption
  • From: Bill <billstuff2001@xxxxxxxxxxxxx>
• Re: sd_setup_discard_cmnd: BUG: unable to handle kernel NULL pointer dereference at (null)
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• Re: Understanding raid array status: Active vs Clean
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid5 (re)-add recovery data corruption
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Adding a new drive to an array
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Adding a new drive to an array
  • From: George Duffield <forumscollective@xxxxxxxxx>
• Re: Understanding raid array status: Active vs Clean
  • From: George Duffield <forumscollective@xxxxxxxxx>
• Re: sd_setup_discard_cmnd: BUG: unable to handle kernel NULL pointer dereference at (null)
  • From: Stefan Priebe <s.priebe@xxxxxxxxxxxx>
• raid5 (re)-add recovery data corruption
  • From: Bill <billstuff2001@xxxxxxxxxxxxx>
• Re: md kernel thread hung in raid1_add_disk
  • From: Matthias Eble <psychotrahe@xxxxxxxxx>
• Re: sd_setup_discard_cmnd: BUG: unable to handle kernel NULL pointer dereference at (null)
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• Re: sd_setup_discard_cmnd: BUG: unable to handle kernel NULL pointer dereference at (null)
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: sd_setup_discard_cmnd: BUG: unable to handle kernel NULL pointer dereference at (null)
  • From: Lars Ellenberg <lars.ellenberg@xxxxxxxxxx>
• Re: sd_setup_discard_cmnd: BUG: unable to handle kernel NULL pointer dereference at (null)
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Failed RAID5 & recovery advise
  • From: Henry Golas <henry.golas@xxxxxxxxxxx>
• sd_setup_discard_cmnd: BUG: unable to handle kernel NULL pointer dereference at (null)
  • From: Stefan Priebe - Profihost AG <s.priebe@xxxxxxxxxxxx>
• Re: RAID newbie, 1 vs 5, chunk sizes
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• Re: mismatches after growing raid1 and re-adding a failed drive
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: RAID newbie, 1 vs 5, chunk sizes
  • From: Roman Mamedov <rm@xxxxxxxxxxx>