Linux RAID Storage Date Index

• Thread Index

• Re: off - info about servers and linux mail lists
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• off - info about servers and linux mail lists
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Fix apparent cut-and-paste error in super_90_validate
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Small chunk size read performance penalty
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Fix apparent cut-and-paste error in super_90_validate
  • From: Dave Jones <davej@xxxxxxxxxx>
• [PATCH 3/3] raid1: Rewrite the implementation of iobarrier.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 2/3] radi1: Relace raise_barrier/lower_barrrier with freeze_array/unfreeze_array for reconfigure the array.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [PATCH 1/3] raid1: Add a filed freeze_array to indicate whether raid in freeze state.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• [RFC PATCH 0/3 V2] Rewrite the implementation of iobarrier for raid1.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: Recovery of RAID1 fails (added disks stays as spare)
  • From: NeilBrown <neilb@xxxxxxx>
• RE: Recovery of RAID1 fails (added disks stays as spare)
  • From: <Matthias.Blaesing@xxxxxxxxxx>
• Re: Small chunk size read performance penalty
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: Small chunk size read performance penalty
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Small chunk size read performance penalty
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Does the chunk size of RAID5 really mean the "smallest atomic" mass of data?
  • From: NeilBrown <neilb@xxxxxxx>
• Does the chunk size of RAID5 really mean the "smallest atomic" mass of data?
  • From: taejin1999@xxxxxxxxxxxxxxxxx
• Re: Small chunk size read performance penalty
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Small chunk size read performance penalty
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• raid5: a problem of repeat recovery
  • From: wangkaird <wangkaird@xxxxxxxxx>
• Re: Recovery of RAID1 fails (added disks stays as spare)
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 2/6] DDF: export_examine_super_ddf: print MD_DEVICES
  • From: mwilck@xxxxxxxx
• [PATCH 5/6] in_initrd: fix gcc compiler error
  • From: mwilck@xxxxxxxx
• [PATCH 6/6] mdmon: allow disabling "@dmon" command name at compile time
  • From: mwilck@xxxxxxxx
• [PATCH 4/6] DDF: increase default value for safe_mode_delay to 4000ms
  • From: mwilck@xxxxxxxx
• [PATCH 0/6] Fixes for installation of CentOS 6 on DDF BIOS RAID
  • From: mwilck@xxxxxxxx
• [PATCH 1/6] DDF: ddf_activate_spare: fix gcc -O2 uninitialized warning
  • From: mwilck@xxxxxxxx
• [PATCH 3/6] DDF: container_content_ddf: set safe_mode_delay > 0
  • From: mwilck@xxxxxxxx
• Re: Request for help with "1st time through" RAID array renaming
  • From: ariel.work@xxxxxxxxxx
• Re: Problem with disk replacement
  • From: qindehua <qindehua@xxxxxxx>
• Recovery of RAID1 fails (added disks stays as spare)
  • From: <Matthias.Blaesing@xxxxxxxxxx>
• Re: Request for help with "1st time through" RAID array renaming
  • From: ariel.work@xxxxxxxxxx
• Re: Request for help with "1st time through" RAID array renaming
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID problem
  • From: NeilBrown <neilb@xxxxxxx>
• RAID problem
  • From: fixitdad5@xxxxxxxxxxx
• Re: Request for help with "1st time through" RAID array renaming
  • From: ariel.work@xxxxxxxxxx
• Request for help with "1st time through" RAID array renaming
  • From: ariel.work@xxxxxxxxxx
• Re: [BUG] md hang at schedule in md_write_start
  • From: Jack Wang <jinpu.wang@xxxxxxxxxxxxxxxx>
• Re: [BUG] md hang at schedule in md_write_start
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Ed L Cashin <ecashin@xxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [BUG] md hang at schedule in md_write_start
  • From: Jack Wang <jinpu.wang@xxxxxxxxxxxxxxxx>
• Re: [BUG] md hang at schedule in md_write_start
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [BUG] md hang at schedule in md_write_start
  • From: Jack Wang <jinpu.wang@xxxxxxxxxxxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Wes <wt75@xxxxxxxxx>
• [patch 3/3] raid5: relieve lock contention in get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 2/3] wait: add wait_event_cmd()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 1/3] raid5: rename stripe_hash()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 0/3] raid5: relieve lock contention of get_active_stripe()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 2/3 v2] raid5: sysfs entry to control worker thread number
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 3/3 v2] raid5: only wakeup necessary threads
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 1/3 v2] raid5: offload stripe handle to workqueue
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [patch 0/3 v2] raid5: make stripe handling multi-threading
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Recovering from two almost simultaneously failed devices in RAID1
  • From: Carsten Aulbert <Carsten.Aulbert@xxxxxxxxxx>
• Re: Recovering from two almost simultaneously failed devices in RAID1
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Recovering from two almost simultaneously failed devices in RAID1
  • From: Carsten Aulbert <Carsten.Aulbert@xxxxxxxxxx>
• Re: Recovering from two almost simultaneously failed devices in RAID1
  • From: Carsten Aulbert <Carsten.Aulbert@xxxxxxxxxx>
• Recovering from two almost simultaneously failed devices in RAID1
  • From: Carsten Aulbert <Carsten.Aulbert@xxxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• Re: [PATCH 18/22] block: Generic bio chaining
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Ed Cashin <ecashin@xxxxxxxxxx>
• Re: [PATCH 04/22] block: Abstract out bvec iterator
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: raid1 read io balancing algorithm
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: raid1 read io balancing algorithm
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• raid1 read io balancing algorithm
  • From: <struhlo@xxxxxxxxxx>
• Re: RFC: handling of missing disks in DDF
  • From: Martin Wilck <martin.wilck@xxxxxxxxxxxxxx>
• Re: [PATCH 9/9] Create: set array status to frozen until monitoring starts
  • From: Martin Wilck <martin.wilck@xxxxxxxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: DDF test fails if default udev rules are active
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 9/9] Create: set array status to frozen until monitoring starts
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] tests/10ddf-fail-two-spares: new unit test
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] RAID: add tilegx SIMD implementation of raid6
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RFC: handling of missing disks in DDF
  • From: NeilBrown <neilb@xxxxxxx>
• RFC: handling of missing disks in DDF
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 0/22] Immutable biovecs, block layer changes
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 03/22] bcache: Kill unaligned bvec hack
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 02/22] block: Consolidate duplicated bio_trim() implementations
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 01/22] block: Use rw_copy_check_uvector()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 06/22] block: Convert bio_iovec() to bvec_iter
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 09/22] block: Convert bio_copy_data() to bvec_iter
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 08/22] block: Immutable bio vecs
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 10/22] bio-integrity: Convert to bvec_iter
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 11/22] block: Kill bio_segments()/bi_vcnt usage
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 05/22] dm: Use bvec_iter for dm_bio_record()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 12/22] block: Convert drivers to immutable biovecs
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 15/22] rbd: Refactor bio cloning, don't clone biovecs
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 19/22] block: Rename bio_split() -> bio_pair_split()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 18/22] block: Generic bio chaining
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 17/22] block: Remove bi_idx hacks
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 16/22] dm: Refactor for new bio cloning/splitting
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 13/22] ceph: Convert to immutable biovecs
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 20/22] block: Introduce new bio_split()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 21/22] block: Kill bio_pair_split()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 14/22] block: Kill bio_iovec_idx(), __bio_iovec()
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH 22/22] block: Don't save/copy bvec array anymore, share when cloning
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• [PATCH] tests/10ddf-fail-two-spares: new unit test
  • From: mwilck@xxxxxxxx
• [PATCH] RAID: add tilegx SIMD implementation of raid6
  • From: Ken Steele <ken@xxxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• Re: DDF: regression caused by 273989b9 / ce45c819
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm --fail on RAID0 array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• Re: DDF test fails if default udev rules are active
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 6/9] tests/10ddf-fail-spare: more sophisticated result checks
  • From: mwilck@xxxxxxxx
• [PATCH 9/9] Create: set array status to frozen until monitoring starts
  • From: mwilck@xxxxxxxx
• [PATCH 8/9] DDF: ddf_open_new: check device status for new subarray
  • From: mwilck@xxxxxxxx
• [PATCH 7/9] tests/10ddf-fail-create-race: test handling of fail/create race
  • From: mwilck@xxxxxxxx
• Patches related to current discussion
  • From: mwilck@xxxxxxxx
• mdadm --fail on RAID0 array
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• DDF: regression caused by 273989b9 / ce45c819
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: when md raid1 superblock is bad block, what happens
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• Re: when md raid1 superblock is bad block, what happens
  • From: NeilBrown <neilb@xxxxxxx>
• when md raid1 superblock is bad block, what happens
  • From: Dong Wu <archer.wudong@xxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 5/5] test: allow LVM volumes or RAM disks as test devices
  • From: mwilck@xxxxxxxx
• [PATCH 4/5] DDF: get_extents: don't allocate space on failed disks
  • From: mwilck@xxxxxxxx
• [PATCH 3/5] tests/10ddf-fail-spare: new unit test
  • From: mwilck@xxxxxxxx
• [PATCH 2/5] tests/10ddf-fail-twice: remove hard-coded assumptions
  • From: mwilck@xxxxxxxx
• [PATCH 1/5] tests/env-ddf-template: some helper functions
  • From: mwilck@xxxxxxxx
• Re: Bugreport ddf rebuild problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• when md raid1 superblock is bad block, what happens
  • From: "archer.wudong" <archer.wudong@xxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: question about mdmon --takeover
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bugreport: mdmon will not start with latest git version when using ddf container
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] imsm: fix checking completion of RAID10 resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] mdmon: let mdmon know the layout
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/4] DDF: ddf_process_update: delete removed disks from dlist
  • From: NeilBrown <neilb@xxxxxxx>
• Re: help needed restoring data
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Advice for recovering array containing LUKS encrypted LVM volumes
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Advice for recovering array containing LUKS encrypted LVM volumes
  • From: P Orrifolius <porrifolius@xxxxxxxxx>
• help needed restoring data
  • From: Uwe Wächter <uwe.waechter@xxxxxxxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Sam Bingner <sam@xxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Keld Jørn Simonsen <keld@xxxxxxxxxx>
• Re: [PATCH 3/4] DDF: ddf_process_update: delete removed disks from dlist
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: RFC swap over raid1
  • From: keld@xxxxxxxxxx
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• [PATCH] mdmon: let mdmon know the layout
  • From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
• Re: RFC swap over raid1
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: RFC swap over raid1
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 4/4] tests/10ddf-fail-twice: New unit test
  • From: mwilck@xxxxxxxx
• [PATCH 3/4] DDF: ddf_process_update: delete removed disks from dlist
  • From: mwilck@xxxxxxxx
• [PATCH 2/4] DDF: no need for GET_LAYOUT any more
  • From: mwilck@xxxxxxxx
• [PATCH 1/4] mdmon: always get layout from sysfs
  • From: mwilck@xxxxxxxx
• Re: Bugreport ddf rebuild problems
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: RFC swap over raid1
  • From: Doug Ledford <dledford@xxxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Martin Wilck <mwilck@xxxxxxxx>
• RFC swap over raid1
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Bugreport ddf rebuild problems
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Bugreport ddf rebuild problems
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• RE: [PATCH] imsm: fix checking completion of RAID10 resync
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Tejun Heo <tj@xxxxxxxxxx>
• RE: [PATCH] imsm: fix checking completion of RAID10 resync
  • From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
• Re: Bugreport: mdmon will not start with latest git version when using ddf container
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bugreport: mdmon will not start with latest git version when using ddf container
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Bugreport: mdmon will not start with latest git version when using ddf container
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Bugreport: mdmon will not start with latest git version when using ddf container
  • From: Albert Pauw <albert.pauw@xxxxxxxxx>
• question about mdmon --takeover
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: Reshape/Grow to fewer but bigger devices
  • From: Christian Nilsson <nikize@xxxxxxxxx>
• Re: Reshape/Grow to fewer but bigger devices
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] tests/env-ddf-template: helper for new unit test
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] tests/env-ddf-template: helper for new unit test
  • From: mwilck@xxxxxxxx
• Re: [PATCH 06/10] monitor: read_and_act: log status when called
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Reshape/Grow to fewer but bigger devices
  • From: NeilBrown <neilb@xxxxxxx>
• Re: ddf: remove failed devices that are no longer in use ?!?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 00/10] Two bug fixes and a lot of debug code
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 06/10] monitor: read_and_act: log status when called
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Reshape/Grow to fewer but bigger devices
  • From: Christian Nilsson <nikize@xxxxxxxxx>
• Re: [PATCH] imsm: fix checking completion of RAID10 resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Avoid double close()
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 09/10] mdmon: manage_member: fix race condition during slow meta data writes
  • From: mwilck@xxxxxxxx
• [PATCH 10/10] tests/10ddf-create-fail-rebuild: new unit test for DDF
  • From: mwilck@xxxxxxxx
• [PATCH 07/10] mdmon: wait_and_act: fix debug message for SIGUSR1
  • From: mwilck@xxxxxxxx
• [PATCH 05/10] DDF: ddf_set_disk: add some debug messages
  • From: mwilck@xxxxxxxx
• [PATCH 06/10] monitor: read_and_act: log status when called
  • From: mwilck@xxxxxxxx
• [PATCH 08/10] mdmon: manage_member: debug messages for array state
  • From: mwilck@xxxxxxxx
• [PATCH 03/10] DDF: ddf_process_update: log offsets for conf changes
  • From: mwilck@xxxxxxxx
• [PATCH 04/10] DDF: load_ddf_header: more error logging
  • From: mwilck@xxxxxxxx
• [PATCH 01/10] DDF: ddf_activate_spare: bugfix for 62ff3c40
  • From: mwilck@xxxxxxxx
• [PATCH 02/10] DDF: log disk status changes more nicely
  • From: mwilck@xxxxxxxx
• [PATCH 00/10] Two bug fixes and a lot of debug code
  • From: mwilck@xxxxxxxx
• Re: Suspicious test failure - mdmon misses recovery events on loop devices
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: ddf: remove failed devices that are no longer in use ?!?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH] Avoid double close()
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: [patch 3/3] raid5: only wakeup necessary threads
  • From: Tejun Heo <tj@xxxxxxxxxx>
• [PATCH] imsm: fix checking completion of RAID10 resync
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [patch 3/3] raid5: only wakeup necessary threads
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [patch 3/3] raid5: only wakeup necessary threads
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [patch 1/3] raid5: offload stripe handle to workqueue
  • From: Tejun Heo <tj@xxxxxxxxxx>
• [patch 3/3] raid5: only wakeup necessary threads
  • From: shli@xxxxxxxxxx
• [patch 2/3] raid5: sysfs entry to control worker thread number
  • From: shli@xxxxxxxxxx
• [patch 1/3] raid5: offload stripe handle to workqueue
  • From: shli@xxxxxxxxxx
• [patch 0/3] raid5: make stripe handling multi-threading
  • From: shli@xxxxxxxxxx
• Re: Recovery possible after partial reshape failure?
  • From: Veedar Hokstadt <veedar@xxxxxxxxx>
• Re: ddf: remove failed devices that are no longer in use ?!?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/4] Basic hotspare handling for RAID10
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Suspicious test failure - mdmon misses recovery events on loop devices
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Mdadm server eating drives
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Suspicious test failure - mdmon misses recovery events on loop devices
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Suspicious test failure - mdmon misses recovery events on loop devices
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• RE: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Suspicious test failure - mdmon misses recovery events on loop devices
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [patch]raid5: fix stripe release order
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md/raid5: raid5d livelocks after drive failure during resync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: md/raid5: raid5d livelocks after drive failure during resync
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Marcus Sorensen <shadowsor@xxxxxxxxx>
• Re: Recovery help? 4-disk RAID5 double-failure, but good disks have event count mismatch.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Wes <wt75@xxxxxxxxx>
• Recovery help? 4-disk RAID5 double-failure, but good disks have event count mismatch.
  • From: Richard Michael <rmichael@xxxxxxxxxxxxxxxx>
• ddf: remove failed devices that are no longer in use ?!?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Suspicious test failure - mdmon misses recovery events on loop devices
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: mdadm -Db switches array to write-pending?!
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm -Db switches array to write-pending?!
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• RE: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PULL REQUEST] 2 more bug fixes for md in 3.11
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• RE: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Bill Davidsen <davidsen@xxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 1/4] DDF: find_vdcr: fix minor bug in debug message
  • From: mwilck@xxxxxxxx
• [PATCH 4/4] DDF: ddf_activate_spare: fix metadata update for SVDs
  • From: mwilck@xxxxxxxx
• [PATCH 3/4] DDF: ddf_activate_spare: only activate good drives
  • From: mwilck@xxxxxxxx
• [PATCH 2/4] DDF: ddf_activate_spare: Add RAID10 code
  • From: mwilck@xxxxxxxx
• [PATCH 0/4] Basic hotspare handling for RAID10
  • From: mwilck@xxxxxxxx
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Wes <wt75@xxxxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Wes <wt75@xxxxxxxxx>
• Re: raid10 centos5 vs. centos6 300% worse random write performance
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• raid10 centos5 vs. centos6 300% worse random write performance
  • From: Wes <wt75@xxxxxxxxx>
• [patch]raid5: fix stripe release order
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Preparing for mdadm-3.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problem with disk replacement
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problem with disk replacement
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Problem with disk replacement
  • From: qindehua <qindehua@xxxxxxx>
• Re: Help creating filesystem (xfs) and partitioning
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Help creating filesystem (xfs) and partitioning
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: shown disk sizes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: shown disk sizes
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: shown disk sizes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: shown disk sizes
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: Should "mdadm --add" complain if the new device appears to have a filesystem on it?
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: shown disk sizes
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: shown disk sizes
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Should "mdadm --add" complain if the new device appears to have a filesystem on it?
  • From: Christian Iversen <chrivers@xxxxxxxxxxxxxx>
• MD array keeps resyncing after rebooting
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Should "mdadm --add" complain if the new device appears to have a filesystem on it?
  • From: Holger Kiehl <Holger.Kiehl@xxxxxx>
• Re: [PATCH 2/2 v2] md: set write-intent bit first in sync-bitmap for rwm in non-insync region.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2 v2] md: add sync-bitmap to only resync WRITTEN data when adding new disk in raid array.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC/PATCH 0/6] DDF: safe big-endian types
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problem with disk replacement
  • From: NeilBrown <neilb@xxxxxxx>
• Should "mdadm --add" complain if the new device appears to have a filesystem on it?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problem with disk replacement
  • From: qindehua <qindehua@xxxxxxx>
• [PATCH v2] mdadm: add sync-bitmap to only resync WRITTEN data when adding new disk in raid array.
  • From: Robin Dong <robin.k.dong@xxxxxxxxx>
• [PATCH 2/2 v2] md: set write-intent bit first in sync-bitmap for rwm in non-insync region.
  • From: Robin Dong <robin.k.dong@xxxxxxxxx>
• [PATCH 1/2 v2] md: add sync-bitmap to only resync WRITTEN data when adding new disk in raid array.
  • From: Robin Dong <robin.k.dong@xxxxxxxxx>
• Re: Problem with disk replacement
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 1/6] DDF: add endian-safe typedefs
  • From: mwilck@xxxxxxxx
• [PATCH 2/6] DDF: convert big endian to be32 type
  • From: mwilck@xxxxxxxx
• [PATCH 4/6] DDF: convert big-endian __u16 to be16 type
  • From: mwilck@xxxxxxxx
• [PATCH 5/6] DDF: add_other_bvd: fix endianness bug
  • From: mwilck@xxxxxxxx
• [PATCH 3/6] DDF: convert big-endian __u64 to be64 type
  • From: mwilck@xxxxxxxx
• [PATCH 6/6] DDF: ddf_set_disk: fix minor endianness bug
  • From: mwilck@xxxxxxxx
• [RFC/PATCH 0/6] DDF: safe big-endian types
  • From: mwilck@xxxxxxxx
• Re: How does md(adm) work with fake-raid ?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: How does md(adm) work with fake-raid ?
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• 3.10.1: echo repair > sync_action causes hang on RAID-1 (2 x SSD)
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: --assemble --scan --no-degrades assembles+run degraded RAID1?
  • From: NeilBrown <neilb@xxxxxxx>
• --assemble --scan --no-degrades assembles+run degraded RAID1?
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• [PATCH 6/6] tests/10ddf-geometry: new unit test
  • From: mwilck@xxxxxxxx
• [PATCH 2/6] DDF: kill_subarray_ddf: fix case without mdmon running
  • From: mwilck@xxxxxxxx
• [PATCH 5/6] test: increase number of devices to 13
  • From: mwilck@xxxxxxxx
• [PATCH 4/6] tests/10ddf-create: create RAID5 first
  • From: mwilck@xxxxxxxx
• [PATCH 1/6] DDF: err_bad_md_layout: fix return value
  • From: mwilck@xxxxxxxx
• [PATCH 3/6] DDF: getinfo_super_ddf_bvd: fix offset calculation for SVDs
  • From: mwilck@xxxxxxxx
• [PATCH 0/6] More DDF fixes and unit tests
  • From: mwilck@xxxxxxxx
• Re: How does md(adm) work with fake-raid ?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: How does md(adm) work with fake-raid ?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: How does md(adm) work with fake-raid ?
  • From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
• Re: How does md(adm) work with fake-raid ?
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: How does md(adm) work with fake-raid ?
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• md raid across physical servers?
  • From: Miles Fidelman <mfidelman@xxxxxxxxxxxxxxxx>
• Re: How does md(adm) work with fake-raid ?
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• Re: How does md(adm) work with fake-raid ?
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Disks supporting ERC?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Disks supporting ERC?
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: Hlep hardware selection
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• [PULL REQUEST] 3 md bug fixes for 3.11 (and 3.10.y)
  • From: NeilBrown <neilb@xxxxxxx>
• Hlep hardware selection
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• How does md(adm) work with fake-raid ?
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: [PATCH 05/27] DDF: Implement store_super_ddf
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 3/3] DDF: factor out writing super block to single disk
  • From: mwilck@xxxxxxxx
• [PATCH 2/3] DDF: make "null_aligned" a static buffer
  • From: mwilck@xxxxxxxx
• [PATCH 1/3] DDF: increase seq number in ddf_set_updates_pending
  • From: mwilck@xxxxxxxx
• Problem with disk replacement
  • From: qindehua <13691222965@xxxxxxx>
• Problem with disk replacement
  • From: Qin Dehua <qindehua@xxxxxxxxx>
• md/raid5: raid5d livelocks after drive failure during resync
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• write-mostly vs. write-behind
  • From: Michael Heide <lkml662@xxxxxxxxx>
• Re: shown disk sizes
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: shown disk sizes
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: shown disk sizes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm -Db switches array to write-pending?!
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: RAID1 repair GPF crash w/3.10-rc7
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: Backup file size when migrating from raid5 to raid6?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Scrubbing "check" not working for RAID10 in 3.10-rc1+
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• shown disk sizes
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: Backup file size when migrating from raid5 to raid6?
  • From: Boyan Alexiev <alexiev@xxxxxxxxxxxx>
• Re: RAID1 repair GPF crash w/3.10-rc7
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD RAID 1 fail/remove/add corruption in 3.10
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD RAID 1 fail/remove/add corruption in 3.10
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD RAID 1 fail/remove/add corruption in 3.10
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: 3.10: discard/trim support on md-raid1?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 3.10: discard/trim support on md-raid1?
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: MD RAID 1 fail/remove/add corruption in 3.10
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• MD RAID 1 fail/remove/add corruption in 3.10
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: 3.10: discard/trim support on md-raid1?
  • From: David Lang <david@xxxxxxx>
• Re: 3.10: discard/trim support on md-raid1?
  • From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
• Re: 3.10: discard/trim support on md-raid1?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Scrubbing "check" not working for RAID10 in 3.10-rc1+
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovery possible after partial reshape failure?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovery possible after partial reshape failure?
  • From: Veedar Hokstadt <veedar@xxxxxxxxx>
• Re: Scrubbing "check" not working for RAID10 in 3.10-rc1+
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: Scrubbing "check" not working for RAID10 in 3.10-rc1+
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: [PATCH 05/27] DDF: Implement store_super_ddf
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm -Db switches array to write-pending?!
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] block: add bio_rewind() to reset bio_vec
  • From: NeilBrown <neilb@xxxxxxx>
• LVM mirroring versus MD Raid 1
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Recovery possible after partial reshape failure?
  • From: Sam Bingner <sam@xxxxxxxxxxx>
• Recovery possible after partial reshape failure?
  • From: Veedar Hokstadt <veedar@xxxxxxxxx>
• Re: 3.10: discard/trim support on md-raid1?
  • From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
• 3.10: discard/trim support on md-raid1?
  • From: "Justin Piszcz" <jpiszcz@xxxxxxxxxxxxxxx>
• Re: [patch -next] bcache: check for allocation failures
  • From: Kent Overstreet <kmo@xxxxxxxxxxxxx>
• mdadm -Db switches array to write-pending?!
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 05/27] DDF: Implement store_super_ddf
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Query regarding disk failure
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Query regarding disk failure
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Query regarding disk failure
  • From: Priya Kamala <priya.kamala@xxxxxxxxxxxxxxxxxx>
• Re: Query regarding disk failure
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Query regarding disk failure
  • From: Priya Kamala <priya.kamala@xxxxxxxxxxxxxxxxxx>
• Re: Query regarding disk failure
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Query regarding disk failure
  • From: Priya Kamala <priya.kamala@xxxxxxxxxxxxxxxxxx>
• Re: Query regarding disk failure
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Query regarding disk failure
  • From: Priya Kamala <priya.kamala@xxxxxxxxxxxxxxxxxx>
• Re: Re-shape raid0 acts up
  • From: Sam Bingner <sam@xxxxxxxxxxx>
• Re-shape raid0 acts up
  • From: Ole Tange <tange@xxxxxxxxxx>
• Re: Determining if a stripe/RAID0 has failed
  • From: Curtis <serverascode@xxxxxxxxx>
• Re: Determining if a stripe/RAID0 has failed
  • From: NeilBrown <neilb@xxxxxxx>
• Determining if a stripe/RAID0 has failed
  • From: Curtis <serverascode@xxxxxxxxx>
• Re: Extending a 4×3Tb RAID10
  • From: NeilBrown <neilb@xxxxxxx>
• Extending a 4×3Tb RAID10
  • From: martin f krafft <madduck@xxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] md: raid1: use bio_rewind() before bio_copy_data()
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 39/39] DDF: ddf_process_update: Fix updates for SVDs
  • From: mwilck@xxxxxxxx
• [PATCH 38/39] DDF: ddf_process_update: some more debug messages
  • From: mwilck@xxxxxxxx
• [PATCH 37/39] DDF: guid_str: more readable output
  • From: mwilck@xxxxxxxx
• [PATCH 36/39] DDF: ddf_process_update: add debug messages fore adding VDs
  • From: mwilck@xxxxxxxx
• [PATCH 35/39] DDF: add debug message in add_super_ddf_bvd
  • From: mwilck@xxxxxxxx
• [PATCH 34/39] DDF: fix endianness of refnum in debug messages
  • From: mwilck@xxxxxxxx
• [PATCH 33/39] DDF: getinfo_super_ddf_bvd: fix raid_disk calculation
  • From: mwilck@xxxxxxxx
• [PATCH 32/39] DDF: getinfo_super_ddf_bvd: identify disk by refnum
  • From: mwilck@xxxxxxxx
• [PATCH 31/39] DDF: implement kill_subarray
  • From: mwilck@xxxxxxxx
• [PATCH 30/39] DDF: write_init_super_ddf: don't zero superblocks for subarrays
  • From: mwilck@xxxxxxxx
• [PATCH 29/39] Monitor: Don't write metadata in inactive array state
  • From: mwilck@xxxxxxxx
• [PATCH 28/39] test/10-ddf-create: fix comments
  • From: mwilck@xxxxxxxx
• Fixes for the DDF patch series
  • From: mwilck@xxxxxxxx
• Re: [PATCH 11/27] DDF: layout_ddf2md: new DDF->md RAID layout conversion
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 07/27] DDF: find_vdcr: account for secondary RAID level
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 03/27] DDF: load_ddf_headers: use secondary header as fallback
  • From: Martin Wilck <mwilck@xxxxxxxx>
• [PATCH 2/2] md: raid1: use bio_rewind() before bio_copy_data()
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• [PATCH 1/2] block: add bio_rewind() to reset bio_vec
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: RAID1 repair GPF crash w/3.10-rc7
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: DDF/RAID10 patch series
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 11/27] DDF: layout_ddf2md: new DDF->md RAID layout conversion
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 12/27] DDF: layout_md2ddf: new md->DDF layout conversion
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 07/27] DDF: find_vdcr: account for secondary RAID level
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 05/27] DDF: Implement store_super_ddf
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 03/27] DDF: load_ddf_headers: use secondary header as fallback
  • From: NeilBrown <neilb@xxxxxxx>
• Re: some general questions on RAID
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: some general questions on RAID
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: some general questions on RAID
  • From: NeilBrown <neilb@xxxxxxx>
• Re: some general questions on RAID
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm ignoring X as it reports Y as failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm ignoring X as it reports Y as failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Extending an existing RAID (10) array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: some general questions on RAID
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: some general questions on RAID
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: some general questions on RAID
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: some general questions on RAID
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: some general questions on RAID
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Extending an existing RAID (10) array
  • From: Christian <CvB@xxxxxxxxxxx>
• mdadm ignoring X as it reports Y as failed
  • From: "Marek Jaros" <mjaros1@xxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Re: some general questions on RAID
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: some general questions on RAID (OT)
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: some general questions on RAID
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Aren't 2TB+ disk sizes supposed to be standardized?
  • From: Kai Stian Olstad <kai.stian.olstad@xxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: some general questions on RAID (OT)
  • From: Sam Bingner <sam@xxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: some general questions on RAID
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: some general questions on RAID (OT)
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Aren't 2TB+ disk sizes supposed to be standardized?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• [patch -next] bcache: check for allocation failures
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Aren't 2TB+ disk sizes supposed to be standardized?
  • From: Tudor Holton <tudor@xxxxxxxxxxxxxxxxx>
• Re: some general questions on RAID
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: some general questions on RAID
  • From: Sam Bingner <sam@xxxxxxxxxxx>
• Re: some general questions on RAID
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: some general questions on RAID
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: some general questions on RAID
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: question about the best suited RAID level/layout
  • From: Phil Turmel <philip@xxxxxxxxxx>
• some general questions on RAID
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• question about the best suited RAID level/layout
  • From: Christoph Anton Mitterer <calestyo@xxxxxxxxxxxx>
• Re: DDF/RAID10 patch series
  • From: NeilBrown <neilb@xxxxxxx>
• [PULL REQUEST] md updates for 3.10
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Mdadm server eating drives
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID1 repair GPF crash w/3.10-rc7
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Extending an existing RAID (10) array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID1 repair GPF crash w/3.10-rc7
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• [PATCH 19/27] DDF: add_to_super_ddf: Use same amount of workspace as other disks
  • From: mwilck@xxxxxxxx
• [PATCH 02/27] DDF: check_secondary: fix treatment of missing BVDs
  • From: mwilck@xxxxxxxx
• [PATCH 12/27] DDF: layout_md2ddf: new md->DDF layout conversion
  • From: mwilck@xxxxxxxx
• [PATCH 03/27] DDF: load_ddf_headers: use secondary header as fallback
  • From: mwilck@xxxxxxxx
• [PATCH 16/27] DDF: use LBA_OFFSET macro instead of lba_offset field
  • From: mwilck@xxxxxxxx
• [PATCH 09/27] DDF: get_svd_state: Status logic for secondary RAID level
  • From: mwilck@xxxxxxxx
• [PATCH 26/27] DDF: ddf_process_update: Fix vlist treatment for SVDs
  • From: mwilck@xxxxxxxx
• [PATCH 14/27] DDF: init_super_ddf_bvd: initialize other bvds
  • From: mwilck@xxxxxxxx
• [PATCH 13/27] DDF: Simplify allocation of "other BVDs"
  • From: mwilck@xxxxxxxx
• [PATCH 10/27] DDF: allow empty slots in virt disk table
  • From: mwilck@xxxxxxxx
• [PATCH 08/27] DDF: ddf_set_disk: move status logic to separate function
  • From: mwilck@xxxxxxxx
• [PATCH 05/27] DDF: Implement store_super_ddf
  • From: mwilck@xxxxxxxx
• [PATCH 24/27] DDF: ddf_set_array_state: more meaningful output
  • From: mwilck@xxxxxxxx
• [PATCH 06/27] DDF: ddf_open_new: implement minimal consistency check
  • From: mwilck@xxxxxxxx
• [PATCH 11/27] DDF: layout_ddf2md: new DDF->md RAID layout conversion
  • From: mwilck@xxxxxxxx
• [PATCH 04/27] DDF: handle "open flag" according to spec
  • From: mwilck@xxxxxxxx
• [PATCH 27/27] tests/10ddf-create: add RAID 10 array
  • From: mwilck@xxxxxxxx
• [PATCH 25/27] DDF: ddf_process_update: handle update of conf records for SVD
  • From: mwilck@xxxxxxxx
• [PATCH 22/27] DDF: getinfo_super_ddf_bvd: lba_offset calculation for RAID10
  • From: mwilck@xxxxxxxx
• [PATCH 23/27] DDF: guid_str: convenience function to print GUID for debugging
  • From: mwilck@xxxxxxxx
• [PATCH 21/27] DDF: add_to_super_ddf_bvd: use get_svd_state()
  • From: mwilck@xxxxxxxx
• [PATCH 20/27] DDF: add_to_super_ddf: RAID10 changes
  • From: mwilck@xxxxxxxx
• [PATCH 18/27] DDF: add_to_super_ddf: allow empty slots in phys disk table
  • From: mwilck@xxxxxxxx
• [PATCH 17/27] DDF: get_extents: support secondary RAID level
  • From: mwilck@xxxxxxxx
• [PATCH 15/27] DDF: validate_geometry_ddf: support RAID10
  • From: mwilck@xxxxxxxx
• [PATCH 07/27] DDF: find_vdcr: account for secondary RAID level
  • From: mwilck@xxxxxxxx
• [PATCH 01/27] DDF (cleanup): use a common macro for failed searches
  • From: mwilck@xxxxxxxx
• DDF/RAID10 patch series
  • From: mwilck@xxxxxxxx
• Re: Mdadm server eating drives
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• Extending an existing RAID (10) array
  • From: cvb@xxxxxxxxxxx
• Re: Mdadm server eating drives
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] MD: Remember the last sync operation that was performed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Mdadm server eating drives
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] select_devices: fix scanning of container members with dev list
  • From: NeilBrown <neilb@xxxxxxx>
• RAID1 repair GPF crash w/3.10-rc7
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• Re: Preparing for mdadm-3.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] mdadm.8.in: Fix typo: previous -> previously
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] mdadm.8.in: Fix typo: previous -> previously
  • From: Wieland Hoffmann <themineo@xxxxxxxxx>
• Re: Re: [PATCH v1] md: add sync-bitmap to only resync WRITTEN data when adding new disk in raid array.
  • From: majianpeng <majianpeng@xxxxxxxxx>
• Re: [PATCH 0/6] raid6check fixes
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: bug in kernel 3.2 (up to date Debian wheezy)
  • From: Nicolas Jungers <nicolas@xxxxxxxxxxx>
• Re: RAID1 growth of version 1.1/1.2 metadata violates least surprise.
  • From: "Dr. Greg Wettstein" <greg@xxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/6] raid6check fixes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/6] raid6check fixes
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• [PATCH] Detail: Add container device to device list
  • From: mwilck@xxxxxxxx
• Re: [PATCH 1/2] select_devices: fix scanning of container members with dev list
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: Preparing for mdadm-3.3
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 1/2] select_devices: fix scanning of container members with dev list
  • From: Martin Wilck <mwilck@xxxxxxxx>
• bug in kernel 3.2 (up to date Debian wheezy)
  • From: Nicolas Jungers <nicolas@xxxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Nicolas Jungers <nicolas@xxxxxxxxxxx>
• Re: [PATCH 0/6] raid6check fixes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Mdadm server eating drives
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• Re: [Trivial PATCH] removing doubled description for sync_max, merging it within sync_min/sync_max
  • From: NeilBrown <neilb@xxxxxxx>
• [Trivial PATCH] removing doubled description for sync_max, merging it within sync_min/sync_max
  • From: CoolCold <coolthecold@xxxxxxxxx>
• Re: [PATCH v1] md: add sync-bitmap to only resync WRITTEN data when adding new disk in raid array.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] MD: Remember the last sync operation that was performed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/6] raid6check fixes
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• [PATCH v1] md: add sync-bitmap to only resync WRITTEN data when adding new disk in raid array.
  • From: Robin Dong <robin.k.dong@xxxxxxxxx>
• [PATCH v1] mdadm: add sync-bitmap to only resync WRITTEN data when adding new disk in raid array.
  • From: Robin Dong <robin.k.dong@xxxxxxxxx>
• Re: Preparing for mdadm-3.3
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Scrubbing "check" not working for RAID10 in 3.10-rc1+
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] MD: Remember the last sync operation that was performed
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Scrubbing "check" not working for RAID10 in 3.10-rc1+
  • From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
• Re: [PATCH 0/6] raid6check fixes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Preparing for mdadm-3.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Preparing for mdadm-3.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/6] raid6check fixes
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Preparing for mdadm-3.3
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Preparing for mdadm-3.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID1 growth of version 1.1/1.2 metadata violates least surprise.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Problem with Raid1 when all drives failed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/6] raid6check fixes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/6] Makefile: Allow the user to pass EXTRA_CFLAGS
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] Detail: deterministic ordering in --brief --verbose
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] select_devices: fix scanning of container members with dev list
  • From: NeilBrown <neilb@xxxxxxx>
• Snapshotting RAID1
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: RAID6 growing interrupted, array won't assemble or resume growing
  • From: Nic Wolfe <nic@xxxxxxxxxxx>
• Re: Delete and re-purpose a mdadm raid partition
  • From: Jonathan Wilson <piercing_male@xxxxxxxxxxx>
• [PATCH 2/2] Detail: deterministic ordering in --brief --verbose
  • From: mwilck@xxxxxxxx
• [PATCH 1/2] select_devices: fix scanning of container members with dev list
  • From: mwilck@xxxxxxxx
• Re: [PATCH 2/2] Detail: deterministic ordering in --brief --verbose
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: [PATCH 0/6] raid6check fixes
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Growing a 5-drive RAID6 - some initial questions
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Growing a 5-drive RAID6 - some initial questions
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Delete and re-purpose a mdadm raid partition
  • From: Jonathan Wilson <piercing_male@xxxxxxxxxxx>
• Re: Proper way to delete an old RAID1?
  • From: Caspar Smit <c.smit@xxxxxxxxxx>
• Re: Problem with Raid1 when all drives failed
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Bug: Different data offsets while reshaping scrambles data
  • From: Benjamin Meier <post@xxxxxxxxxxxxxxxx>
• Problem with Raid1 when all drives failed
  • From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
• Re: RAID6 growing interrupted, array won't assemble or resume growing
  • From: Nic Wolfe <nic@xxxxxxxxxxx>
• Growing a 5-drive RAID6 - some initial questions
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: RAID6 growing interrupted, array won't assemble or resume growing
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH 2/6] Makefile: Allow the user to pass EXTRA_CFLAGS
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
• Re: RAID6 growing interrupted, array won't assemble or resume growing
  • From: Nic Wolfe <nic@xxxxxxxxxxx>
• Re: Optimal value for bitmap-chunk option
  • From: Roman Mamedov <rm@xxxxxxxxxx>
• Re: [PATCH 0/6] raid6check fixes
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/6] Makefile: Allow the user to pass EXTRA_CFLAGS
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Proper way to delete an old RAID1?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Proper way to delete an old RAID1?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Proper way to delete an old RAID1?
  • From: Caspar Smit <c.smit@xxxxxxxxxx>
• Re: Proper way to delete an old RAID1?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Proper way to delete an old RAID1?
  • From: Caspar Smit <c.smit@xxxxxxxxxx>
• Proper way to delete an old RAID1?
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: [PATCH 0/6] raid6check fixes
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Set AUTOCHECK=false
  • From: Роман Алексеев <r.alekseev@xxxxxxxxx>
• Optimal value for bitmap-chunk option
  • From: Роман Алексеев <r.alekseev@xxxxxxxxx>
• [PATCH 0/6] raid6check fixes
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
• [PATCH 3/6] raid6check: Fix memory leaks detected by valgrind
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
• [PATCH 6/6] raid6check: Check return value of lseek64()
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
• [PATCH 5/6] raid6check: Fix compiler warnings.
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
• [PATCH 2/6] Makefile: Allow the user to pass EXTRA_CFLAGS
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
• [PATCH 4/6] raid6check: Use enums for repair type
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
• [PATCH 1/6] raid6check: Fix build of raid6check
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
• Re: RAID 5: low sequential write performance?
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: RAID 5: low sequential write performance?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID 5: low sequential write performance?
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• UDEV Rule for Timeouts
  • From: Sam Bingner <sam@xxxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• Re: RAID 5: low sequential write performance?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: RAID 5: low sequential write performance?
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: RAID 5: low sequential write performance?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: mdadm --assemble considers event count for spares
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID 5: low sequential write performance?
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: RAID 5: low sequential write performance?
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Please assist with missing RAID 5 array.
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Please assist with missing RAID 5 array.
  • From: Christopher Caruk <caruk@xxxxxxxxxxxx>
• RAID 5: low sequential write performance?
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• [Trivial PATCH 00/33] Remove uses of typedef ctl_table
  • From: Joe Perches <joe@xxxxxxxxxxx>
• [Trivial PATCH 13/33] md: Convert use of typedef ctl_table to struct ctl_table
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• Re: [PULL REQUEST] md bug fixes for 3.10-rc and -stable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID-10 keeps aborting
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: [PULL REQUEST] md bug fixes for 3.10-rc and -stable
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PULL REQUEST] md bug fixes for 3.10-rc and -stable
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH linux-next v2] DM RAID: validate_raid_redundancy: Silence uninitialized variable warning
  • From: Tim Gardner <tim.gardner@xxxxxxxxxxxxx>
• Re: [PATCH linux-next v2] DM RAID: validate_raid_redundancy: Silence uninitialized variable warning
  • From: Tommi Rantala <tt.rantala@xxxxxxxxx>
• Re: Fwd: Help with failed RAID-5 -> 6 migration
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID-10 keeps aborting
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID-10 keeps aborting
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID-10 keeps aborting
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: [PATCH] scsi: Check if the device support WRITE_SAME_10
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Fwd: Help with failed RAID-5 -> 6 migration
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Mdadm server eating drives
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: Mdadm server eating drives
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Mdadm server eating drives
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: NeilBrown <neilb@xxxxxxx>
• Re: BUG - raid 1 deadlock on handle_read_error / wait_barrier
  • From: NeilBrown <neilb@xxxxxxx>
• Re: BUG - raid 1 deadlock on handle_read_error / wait_barrier
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAD1 doesn't fail WRITE that was written only on a rebuilding drive
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID-10 keeps aborting
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: Prevent Autodetection
  • From: Richard Laager <rlaager@xxxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: Fwd: mismatches in raid1, clarification please
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Fwd: mismatches in raid1, clarification please
  • From: Andrew Brooks <arb@xxxxxxxxxxxxxxxx>
• Re: Fwd: mismatches in raid1, clarification please
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Fwd: mismatches in raid1, clarification please
  • From: Andrew Brooks <arb@xxxxxxxxxxxxxxxx>
• Re: Help with failed RAID-5 -> 6 migration
  • From: "Vanhorn, Mike" <michael.vanhorn@xxxxxxxxxx>
• Re: Fwd: Help with failed RAID-5 -> 6 migration
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Prevent Autodetection
  • From: Dmitrijs Ledkovs <xnox@xxxxxxxxxx>
• Re: Prevent Autodetection
  • From: Richard Laager <rlaager@xxxxxxxxxx>
• Prevent Autodetection
  • From: Richard Laager <rlaager@xxxxxxxxxx>
• Re: Fwd: Help with failed RAID-5 -> 6 migration
  • From: Keith Phillips <spootsy.ootsy@xxxxxxxxx>
• Re: Fwd: Help with failed RAID-5 -> 6 migration
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Enlarging device of linear array
  • From: Ramon Hofer <ramonhofer@xxxxxxxxxx>
• Fwd: Help with failed RAID-5 -> 6 migration
  • From: Keith Phillips <spootsy.ootsy@xxxxxxxxx>
• Re: RAID-10 keeps aborting
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: Is this expected RAID10 performance?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Is this expected RAID10 performance?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: SSD + Rust as raid1
  • From: Dominic Raferd <dominic@xxxxxxxxxxxxxxx>
• Re: Is this expected RAID10 performance?
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Is this expected RAID10 performance?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Is this expected RAID10 performance?
  • From: Steve Bergman <sbergman27@xxxxxxxxx>
• Re: Is this expected RAID10 performance?
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: Is this expected RAID10 performance?
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: Is this expected RAID10 performance?
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: Is this expected RAID10 performance?
  • From: Steve Bergman <sbergman27@xxxxxxxxx>
• Re: Is this expected RAID10 performance?
  • From: Steve Bergman <sbergman27@xxxxxxxxx>
• Re: Is this expected RAID10 performance?
  • From: Steve Bergman <sbergman27@xxxxxxxxx>
• Re: Is this expected RAID10 performance?
  • From: Eric Sandeen <sandeen@xxxxxxxxxxx>
• Re: Is this expected RAID10 performance?
  • From: Ric Wheeler <rwheeler@xxxxxxxxxx>
• Re: Is this expected RAID10 performance?
  • From: Steve Bergman <sbergman27@xxxxxxxxx>