Linux RAID Storage Date Index

• Thread Index

• Re: mdsadm -A won't assemble my array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: mdsadm -A won't assemble my array
  • From: "G. Michael Carter" <mikey@xxxxxxxxxxxxxxx>
• mdsadm -A won't assemble my array
  • From: "G. Michael Carter" <mikey@xxxxxxxxxxxxxxx>
• Re: Upgrading storage server
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Upgrading storage server
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Re: raid md126, md127 problem after reboot, howto fix?
  • From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: raid md126, md127 problem after reboot, howto fix?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• [PATCH RESEND] Monitor: fix for regression with container devices
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: raid md126, md127 problem after reboot, howto fix?
  • From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: raid md126, md127 problem after reboot, howto fix?
  • From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Re: RAID1 might_sleep() warning on 3.19-rc7
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: RAID1 might_sleep() warning on 3.19-rc7
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid md126, md127 problem after reboot, howto fix?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• raid md126, md127 problem after reboot, howto fix?
  • From: Marc Widmer <metafor@xxxxxxxxx>
• Re: md resync ignoring unreadable sectors
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• An old "write-mostly" read balance issue
  • From: Dark Penguin <darkpenguin@xxxxxxxxx>
• Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: md resync ignoring unreadable sectors
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: md resync ignoring unreadable sectors
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: md resync ignoring unreadable sectors
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: md resync ignoring unreadable sectors
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: md resync ignoring unreadable sectors
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: md resync ignoring unreadable sectors
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• md resync ignoring unreadable sectors
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: RAID1 might_sleep() warning on 3.19-rc7
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 00/24] Clustered MD RAID1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md: 'array_size' sysfs attribute
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] drivers: md: md-thin: remove duplication with time_after
  • From: Pierre Chevalier <pierrechevalier83@xxxxxxxxx>
• Re: RAID1 might_sleep() warning on 3.19-rc7
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] drivers: md: remove duplication with time_after
  • From: Pierre Chevalier <pierrechevalier83@xxxxxxxxx>
• RAID1 might_sleep() warning on 3.19-rc7
  • From: Tony Battersby <tonyb@xxxxxxxxxxxxxxx>
• re: md: 'array_size' sysfs attribute
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: Can't reshape raid0 to raid10
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: BUG drivers/md/md.c: data-offset reshape renders array unloadable
  • From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
• Re: BUG drivers/md/md.c: data-offset reshape renders array unloadable
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid5 Unplug the disk
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid1 narrow_write_error with 4K disks, sd "bad block number requested" messages
  • From: NeilBrown <neilb@xxxxxxx>
• Re: unsynchronized raid10 with different events count
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Off-Topic Write cache disabling?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Array died during grow; now resync stopped
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Off-Topic Write cache disabling?
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
• Re: Off-Topic Write cache disabling?
  • From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
• Aw: Re: Array died during grow; now resync stopped
  • From: "Jörg Habenicht" <j.habenicht@xxxxxx>
• Re: Array died during grow; now resync stopped
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Can't reshape raid0 to raid10
  • From: NeilBrown <neilb@xxxxxxx>
• RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
• Re: Off-Topic Write cache disabling?
  • From: Weedy <weedy2887@xxxxxxxxx>
• Re: Off-Topic Write cache disabling?
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• [md PATCH 26/26] md: wakeup thread upon rdev_dec_pending()
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 25/26] md: make reconfig_mutex optional for writes to md sysfs files.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 24/26] md: move mddev_lock and related to md.h
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 23/26] md: use mddev->lock to protect updates to resync_{min, max}.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 22/26] md: minor cleanup in safe_delay_store.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 21/26] md: move GET_BITMAP_FILE ioctl out from mddev_lock.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 20/26] md: tidy up set_bitmap_file
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 19/26] md: remove unnecessary 'buf' from get_bitmap_file.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 18/26] md: remove mddev_lock from rdev_attr_show()
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 17/26] md: remove mddev_lock() from md_attr_show()
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 16/26] md/raid5: use ->lock to protect accessing raid5 sysfs attributes.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 15/26] md: remove need for mddev_lock() in md_seq_show()
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 14/26] md/bitmap: protect clearing of ->bitmap by mddev->lock
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 13/26] md: protect ->pers changes with mddev->lock
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 12/26] md: level_store: group all important changes into one place.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 11/26] md: rename ->stop to ->free
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 10/26] md: split detach operation out from ->stop.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 09/26] md/linear: remove rcu protections in favour of suspend/resume
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 08/26] md: make merge_bvec_fn more robust in face of personality changes.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 07/26] md: make ->congested robust against personality changes.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 06/26] md: rename mddev->write_lock to mddev->lock
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 05/26] md/raid5: need_this_block: tidy/fix last condition.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 04/26] md/raid5: need_this_block: start simplifying the last two conditions.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 03/26] md/raid5: separate out the easy conditions in need_this_block.
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 02/26] md/raid5: separate large if clause out of fetch_block().
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 01/26] md: do_release_stripe(): No need to call md_wakeup_thread() twice
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH 00/26] Pending md patches.
  • From: NeilBrown <neilb@xxxxxxx>
• [GIT PULL REQUEST] 2 fixes for md in 3.19
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Off-Topic Write cache disabling?
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Re: Off-Topic Write cache disabling?
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Off-Topic Write cache disabling?
  • From: Weedy <weedy2887@xxxxxxxxx>
• Re: update mdadm version to 3.3.2 in Centos 6.4
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Aw: Re: Array died during grow; now resync stopped
  • From: "Jörg Habenicht" <j.habenicht@xxxxxx>
• Re: Can't reshape raid0 to raid10
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: NeilBrown <neilb@xxxxxxx>
• Fwd: update mdadm version to 3.3.2 in Centos 6.4
  • From: alpha lin <lin.alpha@xxxxxxxxx>
• Re: [PATCH 2/3] md/bitmap: Delete an unnecessary check before the function call "kfree"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Array died during grow; now resync stopped
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH 2/3] md/bitmap: Delete an unnecessary check before the function call "kfree"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH 1/3] dm snapshot: Deletion of unnecessary checks before the function call "vfree"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH 0/3] md: Deletion of a few unnecessary checks
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• update mdadm version to 3.3.2 in Centos 6.4
  • From: alpha lin <lin.alpha@xxxxxxxxx>
• Array died during grow; now resync stopped
  • From: Jörg Habenicht <j.habenicht@xxxxxx>
• RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [dm-devel] [PATCH] md: fix raid5 livelock
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md: do_release_stripe(): No need to call md_wakeup_thread() twice
  • From: NeilBrown <neilb@xxxxxxx>
• Re: unsynchronized raid10 with different events count
  • From: LuVar <luvar@xxxxxxxxxxxx>
• Re: unsynchronized raid10 with different events count
  • From: LuVar <luvar@xxxxxxxxxxxx>
• unsynchronized raid10 with different events count
  • From: LuVar <luvar@xxxxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [PATCH] md: do_release_stripe(): No need to call md_wakeup_thread() twice
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: [PATCH] md: fix raid5 livelock
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: superfluous md_wakeup_thread()
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [dm-devel] [PATCH] md: fix raid5 livelock
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• raid1 narrow_write_error with 4K disks, sd "bad block number requested" messages
  • From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: NeilBrown <neilb@xxxxxxx>
• Re: superfluous md_wakeup_thread()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] IMSM: Clear migration record on disks more often
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid5 Unplug the disk
  • From: John Drescher <drescherjm@xxxxxxxxx>
• Re: [dm-devel] [patch] dm cache: fix up IS_ERR vs NULL confusion
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• raid5 Unplug the disk
  • From: "lilofile" <lilofile@xxxxxxxxxx>
• [patch] dm cache: fix up IS_ERR vs NULL confusion
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [PATCH] md: fix raid5 livelock
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Monitor Queue Depth for RAID-5 md device
  • From: NeilBrown <neilb@xxxxxxx>
• Monitor Queue Depth for RAID-5 md device
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• [PATCH] md: fix raid5 livelock
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Monitor Queue Depth for RAID-5 md device
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Re: BUG drivers/md/md.c: data-offset reshape renders array unloadable
  • From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
• Re: BUG drivers/md/md.c: data-offset reshape renders array unloadable
  • From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
• BUG drivers/md/md.c: data-offset reshape renders array unloadable
  • From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• All drive in Raid 5 are in 'spare' mode
  • From: Dush <tomdush@xxxxxxxxx>
• Re: mdadm RAID6 "active" with spares and failed disks; need help
  • From: Valentijn <v@xxxxxxxxxxxxxxxx>
• Re: [dm-devel] livelock on MD RAID5
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: kernel refuses devices mdadm -E accepts
  • From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
• Expanding partitions -> missing md on kernel load
  • From: Scott Tablett <scott.tablett@xxxxxxxxxx>
• BUG in "RAID5: batch adjacent full stripe write" - commit 1b8035b0a84a69b3148bbfa1df1350501d0b0869
  • From: Sushma Gurram <Sushma.Gurram@xxxxxxxxxxx>
• Re: mdadm RAID6 "active" with spares and failed disks; need help
  • From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
• RE: BUG in "RAID5: batch adjacent full stripe write" - commit 1b8035b0a84a69b3148bbfa1df1350501d0b0869
  • From: Sushma Gurram <Sushma.Gurram@xxxxxxxxxxx>
• RE: BUG in "RAID5: batch adjacent full stripe write" - commit 1b8035b0a84a69b3148bbfa1df1350501d0b0869
  • From: Sushma Gurram <Sushma.Gurram@xxxxxxxxxxx>
• Re: kernel refuses devices mdadm -E accepts
  • From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
• RE: RAID 6 recovery issue
  • From: "Graham Mitchell" <gmitch@xxxxxxxxxxx>
• Re: kernel refuses devices mdadm -E accepts
  • From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
• Re: kernel refuses devices mdadm -E accepts
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: kernel refuses devices mdadm -E accepts
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 6 recovery issue
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• RAID 6 recovery issue
  • From: "Graham Mitchell" <gmitch@xxxxxxxxxxx>
• [PATCH] IMSM: Clear migration record on disks more often
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: [dm-devel] [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [dm-devel] [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Is it possible to use bad_blocks to simulate write_error and activate hot-replace?
  • From: Apple Yin <bravery.apple@xxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Xiao Ni <xni@xxxxxxxxxx>
• livelock on MD RAID5
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: kernel refuses devices mdadm -E accepts
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• kernel refuses devices mdadm -E accepts
  • From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Corrupted Cisco NSS4000 raid
  • From: Valentijn Sessink <v@xxxxxxxxxxxxxxxx>
• Corrupted Cisco NSS4000 raid
  • From: Jan Hejl <jh@xxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: XiaoNi <xni@xxxxxxxxxx>
• RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
• Re: mdadm RAID6 "active" with spares and failed disks; need help
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• [PATCH v2 6/9] md/raid5: get rid of bio_fits_rdev()
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• [PATCH v2 7/9] block: kill merge_bvec_fn() completely
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• [PATCH v2 5/7] md/raid10: make sync_request_write() call bio_copy_data()
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• Re: mdadm RAID6 "active" with spares and failed disks; need help
  • From: Valentijn Sessink <v@xxxxxxxxxxxxxxxx>
• Re: mdadm RAID6 "active" with spares and failed disks; need help
  • From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
• [PATCH] dm mpath: simplify failure path of dm_miltipath_init()
  • From: Johannes Thumshirn <morbidrsa@xxxxxxxxx>
• superfluous md_wakeup_thread()
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• raid5 hard lockup
  • From: Terry Hardie <thardie@xxxxxxxxxxxxxxxx>
• Neil Brown is on leave
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Unable to make mdadm from git (fatal error: ansidecl.h)
  • From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
• Unable to make mdadm from git (fatal error: ansidecl.h)
  • From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
• Re: mdadm RAID6 "active" with spares and failed disks; need help
  • From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
• Re: md raid performance with 3-18-rc3
  • From: Manish Awasthi <manish.awasthi@xxxxxxxxxxxxxxxxxx>
• Re: Reassembling RAID1 after good drive was offline [newbie]
  • From: Aryeh Leib Taurog <vim@xxxxxxxxxxxxx>
• [PATCH] [md] raid5: check faulty flag for array status during recovery.
  • From: Eric Mei <meijia@xxxxxxxxx>
• mdadm RAID6 "active" with spares and failed disks; need help
  • From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
• [PATCH] dm bufio: fix time comparison
  • From: Asaf Vertz <asaf.vertz@xxxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• ignoring %s as it reports %s as failed
  • From: Valentijn <v@xxxxxxxxxxxxxxxx>
• Re: md raid performance with 3-18-rc3
  • From: Manish Awasthi <manish.awasthi@xxxxxxxxxxxxxxxxxx>
• Re: Reassembling RAID1 after good drive was offline [newbie]
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Reassembling RAID1 after good drive was offline [newbie]
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: [dm-devel] Questions about the function, queue_empty in dm-cache-policy-mq.c
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: Reassembling RAID1 after good drive was offline [newbie]
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Reassembling RAID1 after good drive was offline [newbie]
  • From: Aryeh Leib Taurog <vim@xxxxxxxxxxxxx>
• Re: Re : Re: Big trouble during reassemble a Raid5
  • From: sylvain.depuille@xxxxxxxxxxx
• Re: Re : Re: Big trouble during reassemble a Raid5
  • From: sylvain.depuille@xxxxxxxxxxx
• Re: Reassembling RAID1 after good drive was offline [newbie]
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Reassembling RAID1 after good drive was offline [newbie]
  • From: Aryeh Leib Taurog <vim@xxxxxxxxxxxxx>
• Re: Reassembling RAID1 after good drive was offline [newbie]
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: Reassembling RAID1 after good drive was offline [newbie]
  • From: Aryeh Leib Taurog <vim@xxxxxxxxxxxxx>
• Re: Reassembling RAID1 after good drive was offline [newbie]
  • From: Aryeh Leib Taurog <vim@xxxxxxxxxxxxx>
• Re: Reassembling RAID1 after good drive was offline [newbie]
  • From: Anthonys Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Re : Re: Big trouble during reassemble a Raid5
  • From: Can Jeuleers <can.jeuleers@xxxxxxxxx>
• RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
• Re: Re: Re : Re: Big trouble during reassemble a Raid5
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Re: Re : Re: Big trouble during reassemble a Raid5
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Re : Re: Big trouble during reassemble a Raid5
  • From: sylvain.depuille@xxxxxxxxxxx
• Re: Reassembling RAID1 after good drive was offline [newbie]
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: Re : Re: Big trouble during reassemble a Raid5
  • From: sylvain.depuille@xxxxxxxxxxx
• [PATCH] md: dm-thin-metadata: Remove unused function
  • From: Rickard Strandqvist <rickard_strandqvist@xxxxxxxxxxxxxxxxxx>
• Reassembling RAID1 after good drive was offline [newbie]
  • From: Aryeh Leib Taurog <vim@xxxxxxxxxxxxx>
• Re: Re: Re : Re: Big trouble during reassemble a Raid5
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Re : Re: Big trouble during reassemble a Raid5
  • From: sylvain.depuille@xxxxxxxxxxx
• Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Pasi Kärkkäinen <pasik@xxxxxx>
• Re: Re: Re : Re: Big trouble during reassemble a Raid5
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Re : Re: Big trouble during reassemble a Raid5
  • From: sylvain.depuille@xxxxxxxxxxx
• Re: Re: Re : Re: Big trouble during reassemble a Raid5
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Re : Re: Big trouble during reassemble a Raid5
  • From: sylvain.depuille@xxxxxxxxxxx
• RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
• Re: Re : Re: Big trouble during reassemble a Raid5
  • From: sylvain.depuille@xxxxxxxxxxx
• Can't reshape raid0 to raid10
  • From: Xiao Ni <xni@xxxxxxxxxx>
• AW: md_raid5 recovering failed need help
  • From: "Stephan Hafiz" <forum@xxxxxxxx>
• Re: Re : Re: Big trouble during reassemble a Raid5
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• [SOLVED] Re: On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: Big trouble during reassemble a Raid5
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Big trouble during reassemble a Raid5
  • From: sylvain.depuille@xxxxxxxxxxx
• A recommendation from Friend, screw college, I'm dropping out
  • From: fernalynbuendia@xxxxxxxxxxx
• Re: md_raid5 recovering failed need help
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH][MD] raid : fix raid recoverying all data corruption, when j=0(sectors) interrupted by "echo idle > /sys/block/md0/md/sync_action"
  • From: 董杨 <donglife1208@xxxxxxxxx>
• Re: [PATCH 00/24] Clustered MD RAID1
  • From: Marcus <shadowsor@xxxxxxxxx>
• Re: [PATCH 00/24] Clustered MD RAID1
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 00/24] Clustered MD RAID1
  • From: Peter Kieser <peter@xxxxxxxxx>
• md_raid5 recovering failed need help
  • From: "Stephan Hafiz" <forum@xxxxxxxx>
• RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
• Re: [PATCH 00/24] Clustered MD RAID1
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH 00/24] Clustered MD RAID1
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH] Monitor: fix for regression with container devices
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: [RFC PATCH 12/17] md/raid10: make sync_request_write() call bio_copy_data()
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 12/17] md/raid10: make sync_request_write() call bio_copy_data()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 01/24] md-cluster: Design Documentation
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: 4 disks outage in RAID6
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [RFC PATCH 13/17] md/raid5: get rid of bio_fits_rdev()
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• [RFC PATCH 12/17] md/raid10: make sync_request_write() call bio_copy_data()
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• [RFC PATCH 14/17] block: kill merge_bvec_fn() completely
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• Re: Expand RAID5 array or switch to RAID10
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Expand RAID5 array or switch to RAID10
  • From: forumscollective@xxxxxxxxx
• 4 disks outage in RAID6
  • From: Mark Kolama <indigo8472@xxxxxxxxx>
• Re: [PATCH 01/24] md-cluster: Design Documentation
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 01/24] md-cluster: Design Documentation
  • From: John Stoffel <john@xxxxxxxxxxxxxxxxxxxxx>
• Re: indefinite hang when growing/reshaping
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: indefinite hang when growing/reshaping
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Panic doing BLKDISCARD on a raid 5 array on linux 3.17.3
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• [PATCH 23/24] Read from the first device when an area is resyncing
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 24/24] Add new disk to clustered array
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 21/24] Resync start/Finish actions
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 22/24] Suspend writes in RAID1 if within range
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 20/24] Send RESYNCING while performing resync start/stop
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 19/24] Reload superblock if METADATA_UPDATED is received
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 18/24] metadata_update sends message to other nodes
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 17/24] Communication Framework: Sending functions
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 16/24] Communication Framework: Receiving
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 15/24] Perform resync for cluster node failure
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 14/24] Initiate recovery on node failure
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 13/24] Copy set bits from another slot
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 12/24] bitmap_create returns bitmap pointer
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 11/24] Gather on-going resync information of other nodes
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 10/24] Lock bitmap while joining the cluster
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 09/24] Use separate bitmaps for each nodes in the cluster
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 08/24] Add node recovery callbacks
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 07/24] Return MD_SB_CLUSTERED if mddev is clustered
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 06/24] Introduce md_cluster_info
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 05/24] Introduce md_cluster_operations to handle cluster functions
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 04/24] DLM lock and unlock functions
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 03/24] Create a separate module for clustering support
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 02/24] Add number of nodes to bitmap structure for clustering
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 01/24] md-cluster: Design Documentation
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 00/24] Clustered MD RAID1
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: Panic doing BLKDISCARD on a raid 5 array on linux 3.17.3
  • From: Anthony Wright <anthony@xxxxxxxxxxxxxxx>
• Re: Panic doing BLKDISCARD on a raid 5 array on linux 3.17.3
  • From: Anthony Wright <anthony@xxxxxxxxxxxxxxx>
• Re: Question about my patch
  • From: Peter Kieser <peter@xxxxxxxxx>
• Re: raid10: 6 out of 8 disks marked as stale on every restart
  • From: Peter Kieser <peter@xxxxxxxxx>
• RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
• Re: Bug#763917: mdadm: rounding errors in human_size()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10: 6 out of 8 disks marked as stale on every restart
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Panic doing BLKDISCARD on a raid 5 array on linux 3.17.3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] drivers:md: Remove no longer needed fixme comment in raid5.c
  • From: Valdis.Kletnieks@xxxxxx
• Hung RAID5 array with discard
  • From: Terry Hardie <thardie@xxxxxxxxxxxxxxxx>
• Re: [PATCH] drivers:md: Remove no longer needed fixme comment in raid5.c
  • From: NeilBrown <neilb@xxxxxxx>
• indefinite hang when growing/reshaping
  • From: Chris Murphy <chris@xxxxxxxxxxxxxxxxx>
• Panic doing BLKDISCARD on a raid 5 array on linux 3.17.3
  • From: Anthony Wright <anthony@xxxxxxxxxxxxxxx>
• Expand RAID5 array or switch to RAID10
  • From: George Duffield <forumscollective@xxxxxxxxx>
• RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
• RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Question about my patch
  • From: NeilBrown <neilb@xxxxxxx>
• Re: "bitmap file is out of date, doing full recovery"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: [PATCH] Update CONFIG_DM_CRYPT help-text link
  • From: Loic Pefferkorn <loic@xxxxxxxx>
• [PATCH] Update CONFIG_DM_CRYPT help-text link
  • From: Loic Pefferkorn <loic@xxxxxxxx>
• Re: [PATCH] Update CONFIG_DM_CRYPT help-text link
  • From: NeilBrown <neilb@xxxxxxx>
• RE: udisks error creating watch file in md127 container directory
  • From: "Baldysiak, Pawel" <pawel.baldysiak@xxxxxxxxx>
• udisks error creating watch file in md127 container directory
  • From: "John L. Center" <jlcenter@xxxxxxxxxxx>
• Re: RAID1 + power fail + unwanted activation
  • From: Csordás Csaba <cscsordas@xxxxxxxxx>
• Re: Lost raid 5 volume
  • From: "Neil ." <neil.perrie@xxxxxxxxx>
• Re: Lost raid 5 volume
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: "bitmap file is out of date, doing full recovery"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: Lost raid 5 volume
  • From: "Neil ." <neil.perrie@xxxxxxxxx>
• [GIT PULL REQUEST] md updates for 3.19
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Lost raid 5 volume
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Lost raid 5 volume
  • From: "Neil ." <neil.perrie@xxxxxxxxx>
• raid10: 6 out of 8 disks marked as stale on every restart
  • From: Peter Kieser <peter@xxxxxxxxx>
• Re: Growing RAID-10 (near-2) array - which kernel needed?
  • From: cvb@xxxxxxxxxxx
• Re: Growing RAID-10 (near-2) array - which kernel needed?
  • From: cvb@xxxxxxxxxxx
• Re: Growing RAID-10 (near-2) array - which kernel needed?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Growing RAID-10 (near-2) array - which kernel needed?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Growing RAID-10 (near-2) array - which kernel needed?
  • From: cvb@xxxxxxxxxxx
• Re: [PATCH] IMSM: do not use comma expression for simple assignments
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: md raid performance with 3-18-rc3
  • From: Manish Awasthi <manish.awasthi@xxxxxxxxxxxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: md raid performance with 3-18-rc3
  • From: Manish Awasthi <manish.awasthi@xxxxxxxxxxxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: Disks never stop spinning
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: On RAID5 read error during syncing - array .A.A
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• On RAID5 read error during syncing - array .A.A
  • From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
• Re: Disks never stop spinning
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: Multiple arrays out of devices belonging to single array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bug#763917: mdadm: rounding errors in human_size()
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Multiple arrays out of devices belonging to single array
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Re: mdadm creates corrupt superblock
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Disks never stop spinning
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Good drive got kicked out - does mdadm assemble across suspend/resume like it does across reboots?
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: pretty unstable raid 5 now
  • From: "Matthew M. Dean" <fireculex@xxxxxxxxx>
• pretty unstable raid 5 now
  • From: "Matthew M. Dean" <fireculex@xxxxxxxxx>
• Re: [dm-devel] The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: zhangxiao <xiao.zhang@xxxxxxxxxxxxx>
• RAID1 + power fail + unwanted activation
  • From: Csordás Csaba <cscsordas@xxxxxxxxx>
• Re: The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [dm-devel] The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: stray raid10 with 9 hdd with -n3 layout
  • From: Klaus Thorn <klaus@xxxxxxxxxxxxxxxxx>
• Re: md raid performance with 3-18-rc3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md raid performance with 3-18-rc3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: LVM RAID1 syncing component
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: zhangxiao <xiao.zhang@xxxxxxxxxxxxx>
• Re: The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: zhangxiao <xiao.zhang@xxxxxxxxxxxxx>
• Re: The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: NeilBrown <neilb@xxxxxxx>
• The DM_BUFIO_HASH_BITS is defined as 20, any plan to make it flexible?
  • From: zhangxiao <xiao.zhang@xxxxxxxxxxxxx>
• Re: LVM RAID1 syncing component
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 5/8 v2] dm: replace memset by memzero_explicit
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] Grow: Fix wrong 'goto' in set_new_data_offset
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: NeilBrown <neilb@xxxxxxx>
• Re: LVM RAID1 syncing component
  • From: NeilBrown <neilb@xxxxxxx>
• Re: LVM RAID1 syncing component
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: LVM RAID1 syncing component
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: [PATCH 5/8 v2] dm: replace memset by memzero_explicit
  • From: Milan Broz <gmazyland@xxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: [patch] dm space map metadata: fix sm_bootstrap_get_nr_blocks()
  • From: Joe Thornber <thornber@xxxxxxxxxx>
• Re: upgrading a RAID array in-place with larger drives. request for review of my approach?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: upgrading a RAID array in-place with larger drives. request for review of my approach?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: upgrading a RAID array in-place with larger drives. request for review of my approach?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: upgrading a RAID array in-place with larger drives. request for review of my approach?
  • From: terrygalant@xxxxxxxxxxxx
• Re: upgrading a RAID array in-place with larger drives. request for review of my approach?
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• upgrading a RAID array in-place with larger drives. request for review of my approach?
  • From: terrygalant@xxxxxxxxxxxx
• [PATCH 0/8] replace memset by memzero_explicit
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH 5/8 v2] dm: replace memset by memzero_explicit
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH 0/8] replace memset by memzero_explicit
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [PATCH 5/8] dm: replace memset by memzero_explicit
  • From: Julia Lawall <Julia.Lawall@xxxxxxx>
• [no subject]
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: LVM RAID1 syncing component
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Re:
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• [patch] dm space map metadata: fix sm_bootstrap_get_nr_blocks()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: mdadm raid5 single drive fail, single drive out of sync terror
  • From: "Robison, Jon (CMG-Atlanta)" <narfman0@xxxxxxxxx>
• [PATCH] Grow: Fix wrong 'goto' in set_new_data_offset
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: One question about man mdadm
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: One question about man mdadm
  • From: Carsten Aulbert <Carsten.Aulbert@xxxxxxxxxx>
• Re: One question about man mdadm
  • From: XiaoNi <xni@xxxxxxxxxx>
• One question about man mdadm
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Raid 10 far 2 layout clarification.
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• Re:
  • From: NeilBrown <neilb@xxxxxxx>
• Re: LVM RAID1 syncing component
  • From: NeilBrown <neilb@xxxxxxx>
• [no subject]
  • From: Travis Williams <travis@xxxxxxxxx>
• Raid 10 far 2 layout clarification.
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• Re: mdadm raid5 single drive fail, single drive out of sync terror
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: mdadm raid5 single drive fail, single drive out of sync terror
  • From: "Robison, Jon (CMG-Atlanta)" <narfman0@xxxxxxxxx>
• Re: mdadm raid5 single drive fail, single drive out of sync terror
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: mdadm raid5 single drive fail, single drive out of sync terror
  • From: Phil Turmel <philip@xxxxxxxxxx>
• mdadm raid5 single drive fail, single drive out of sync terror
  • From: Jon Robison <narfman0@xxxxxxxxx>
• Re: LVM RAID1 syncing component
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: Is it possible to grow a (far) RAID 10?
  • From: cvb@xxxxxxxxxxx
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: LVM RAID1 syncing component
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Is it possible to grow a (far) RAID 10?
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] Change way of printing name of a process
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: Is it possible to grow a (far) RAID 10?
  • From: cvb@xxxxxxxxxxx
• Is it possible to grow a (far) RAID 10?
  • From: Carsten Aulbert <Carsten.Aulbert@xxxxxxxxxx>
• LVM RAID1 syncing component
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: homehost and 0.90 format
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 - won't rebuild - assigns all added disks as spares
  • From: Jonathan Molyneux <jonathan@xxxxxxxxxxxxxxxxxxxx>
• RE: homehost and 0.90 format
  • From: "Boylan, Ross" <Ross.Boylan@xxxxxxxx>
• Re: homehost and 0.90 format
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD component device renaming with udev and MD on full disk
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD RAID5 hang on make_request
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md raid performance with 3-18-rc3
  • From: NeilBrown <neilb@xxxxxxx>
• Re: raid10 - won't rebuild - assigns all added disks as spares
  • From: NeilBrown <neilb@xxxxxxx>
• raid10 - won't rebuild - assigns all added disks as spares
  • From: Jonathan Molyneux <jonathan@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/5] imsm: support for OROMs shared by multiple HBAs
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm creates corrupt superblock
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: NeilBrown <neilb@xxxxxxx>
• md raid performance with 3-18-rc3
  • From: Manish Awasthi <manish.awasthi@xxxxxxxxxxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• MD RAID5 hang on make_request
  • From: Henry Cai <henryplusplus@xxxxxxxxx>
• MD component device renaming with udev and MD on full disk
  • From: Jason Keltz <jas@xxxxxxxxxxxx>
• Re: degraded raid troubleshooting
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH v2 5/5] imsm: use efivarfs interface for reading UEFI variables
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: [PATCH 1/5] imsm: support for OROMs shared by multiple HBAs
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: mdadm creates corrupt superblock
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• degraded raid troubleshooting
  • From: Stephen Burke <steve.burke.56@xxxxxxxxx>
• Re: [PATCH 5/5] imsm: use efivarfs interface for reading UEFI variables
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/5] imsm: support for OROMs shared by multiple HBAs
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm creates corrupt superblock
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 1/1] dm: Deletion of unnecessary checks before two function calls
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• [PATCH 1/1] bcache: Deletion of an unnecessary check before the function call "kobject_put"
  • From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
• Re: Re-assemble RAID6 from SW to HW RAID
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• [PATCH 5/5] imsm: use efivarfs interface for reading UEFI variables
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH 3/5] imsm: add support for NVMe devices
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH 4/5] imsm: detail-platform improvements
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH 2/5] imsm: support for second and combined AHCI controllers in UEFI mode
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH 1/5] imsm: support for OROMs shared by multiple HBAs
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• [PATCH 0/5] imsm: support for NVMe devices and AHCI spanning
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: mdadm creates corrupt superblock
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: Re-assemble RAID6 from SW to HW RAID
  • From: Drew <drew.kay@xxxxxxxxx>
• Re: Re-assemble RAID6 from SW to HW RAID
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re[2]: Raid 6 Fail Event
  • From: "Justin Stephenson" <justin@xxxxxxxxxxxxxxxxx>
• Re: Re-assemble RAID6 from SW to HW RAID
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re-assemble RAID6 from SW to HW RAID
  • From: Mathias Burén <mathias.buren@xxxxxxxxx>
• Re: Raid 6 Fail Event
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Does order/ sequence of SATA drives matter?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Does order/ sequence of SATA drives matter?
  • From: forumscollective@xxxxxxxxx
• Re[2]: Raid 6 Fail Event
  • From: "Justin Stephenson" <justin@xxxxxxxxxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: NeilBrown <neilb@xxxxxxx>
• [PULL REQUEST] md bug fix for 3.18
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid 6 Fail Event
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Raid 6 Fail Event
  • From: "Justin Stephenson" <justin@xxxxxxxxxxxxxxxxx>
• Re: failed RAID 5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: failed RAID 5 array
  • From: Wolfgang Denk <wd@xxxxxxx>
• Re: failed RAID 5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: failed RAID 5 array
  • From: DeadManMoving <sequel@xxxxxxxxxxxx>
• Re: failed RAID 5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: failed RAID 5 array
  • From: DeadManMoving <sequel@xxxxxxxxxxxx>
• Re: failed RAID 5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: failed RAID 5 array
  • From: DeadManMoving <sequel@xxxxxxxxxxxx>
• Re: Disks never stop spinning
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Disks never stop spinning
  • From: Patrick Gautschi <patrick@xxxxxxxxxxxx>
• Re: md with shared disks
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: Disks never stop spinning
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: failed RAID 5 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: md with shared disks
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: md with shared disks
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: md with shared disks
  • From: Anton Ekermans <antone@xxxxxxxxxx>
• failed RAID 5 array
  • From: DeadManMoving <sequel@xxxxxxxxxxxx>
• Re: RAID 6 (containing LUKS dm-crypt) recovery help.
  • From: pg@xxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• homehost and 0.90 format
  • From: "Boylan, Ross" <Ross.Boylan@xxxxxxxx>
• Re: md with shared disks
  • From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
• Disks never stop spinning
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: md with shared disks
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Jason Keltz <jas@xxxxxxxxxxxx>
• Re: --no-degraded does not work
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• md with shared disks
  • From: Anton Ekermans <antone@xxxxxxxxxx>
• What is the correct way of making image copy of a member disk in md array?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Trying to get POLICY working
  • From: NeilBrown <neilb@xxxxxxx>
• Re: --no-degraded does not work
  • From: NeilBrown <neilb@xxxxxxx>
• --no-degraded does not work
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: RAID 6 (containing LUKS dm-crypt) recovery help.
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Raid5 drive fail during grow and no backup
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 6 (containing LUKS dm-crypt) recovery help.
  • From: xar <xar@xxxxxxxxx>
• Re: RAID 6 (containing LUKS dm-crypt) recovery help.
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• RAID 6 (containing LUKS dm-crypt) recovery help.
  • From: xar <xar@xxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Vince <stuff@xxxxxxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Vince <stuff@xxxxxxxxxxxxxx>
• Re: mdadm named array (metadata 1.2) and udev when assembling an array in initramfs
  • From: Stephen Kent <smkent@xxxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: "bitmap file is out of date, doing full recovery"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: mdadm named array (metadata 1.2) and udev when assembling an array in initramfs
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Maintenance Checklist (sanity check request)
  • From: Barrett Lewis <barrett.lewis.mitsi@xxxxxxxxx>
• Re: [PATCH] mdadm: fix --detail for cases where device count > max_devices/2
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Fake RAID 10 on ASRock Z97 Extreme3 with Slackware 14.1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Fake RAID 10 on ASRock Z97 Extreme3 with Slackware 14.1
  • From: gornea <gornea@xxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Vince <stuff@xxxxxxxxxxxxxx>
• Re: Trying to get POLICY working
  • From: Caspar Smit <c.smit@xxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm named array (metadata 1.2) and udev when assembling an array in initramfs
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm named array (metadata 1.2) and udev when assembling an array in initramfs
  • From: Stephen Kent <smkent@xxxxxxxxxx>
• Re: Trying to get POLICY working
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm named array (metadata 1.2) and udev when assembling an array in initramfs
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: micah <micah@xxxxxxxxxx>
• Re: Raid5 drive fail during grow and no backup
  • From: Phil Turmel <philip@xxxxxxxxxx>
• mdadm named array (metadata 1.2) and udev when assembling an array in initramfs
  • From: Stephen Kent <smkent@xxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Trying to get POLICY working
  • From: NeilBrown <neilb@xxxxxxx>
• Re: question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: Trying to get POLICY working
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Trying to get POLICY working
  • From: Caspar Smit <c.smit@xxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• Raid5 drive fail during grow and no backup
  • From: Vince <stuff@xxxxxxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• [PATCH] mdadm: fix --detail for cases where device count > max_devices/2
  • From: Or Sagi <ors@xxxxxxxxxxx>
• Re: Fwd: I will pay money for the correct RAID recovery instructions
  • From: Ian Young <ian@xxxxxxxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Grub2/raid quickie ...
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Grub2/raid quickie ...
  • From: NeilBrown <neilb@xxxxxxx>
• Grub2/raid quickie ...
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: micah <micah@xxxxxxxxxx>
• Re: mdadm creates corrupt superblock
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
  • From: Jason Keltz <jas@xxxxxxxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: micah <micah@xxxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Split RAID: Proposal for archival RAID using incremental batch checksum
  • From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
• Re: question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
  • From: Jason Keltz <jas@xxxxxxxxxxxx>
• Re: [PATCH] Grow: fix resize of array component size to > 32bits
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Grow: fix resize of array component size to > 32bits
  • From: Justin Maggard <jmaggard10@xxxxxxxxx>
• Re: "bitmap file is out of date, doing full recovery"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Very small bug on assemble --force
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help with raid1 to raid5 reshape after crash
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Grow: fix resize of array component size to > 32bits
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID1 removing failed disk returns EBUSY
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm creates corrupt superblock
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Very small bug on assemble --force
  • From: NeilBrown <neilb@xxxxxxx>
• Re: can i recover an all spare raid10 array ?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• RE: can i recover an all spare raid10 array ?
  • From: Roland RoLaNd <r_o_l_a_n_d@xxxxxxxxxxx>
• Re: can i recover an all spare raid10 array ?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• RE: can i recover an all spare raid10 array ?
  • From: Roland RoLaNd <r_o_l_a_n_d@xxxxxxxxxxx>
• Re: can i recover an all spare raid10 array ?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• FW: can i recover an all spare raid10 array ?
  • From: Roland RoLaNd <r_o_l_a_n_d@xxxxxxxxxxx>
• FW: can i recover an all spare raid10 array ?
  • From: Roland RoLaNd <r_o_l_a_n_d@xxxxxxxxxxx>
• mdadm creates corrupt superblock
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: can i recover an all spare raid10 array ?
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• can i recover an all spare raid10 array ?
  • From: Roland RoLaNd <r_o_l_a_n_d@xxxxxxxxxxx>
• Very small bug on assemble --force
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: micah <micah@xxxxxxxxxx>
• Re: Raid1 element stuck in (S) state
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• RAID1 removing failed disk returns EBUSY
  • From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
• Raid1 element stuck in (S) state
  • From: micah anderson <micah@xxxxxxxxxx>
• Re: storage with "very high Average Read/Write Request Time"
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• storage with "very high Average Read/Write Request Time"
  • From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• [PATCH] Grow: fix resize of array component size to > 32bits
  • From: Justin Maggard <jmaggard10@xxxxxxxxx>
• Help with raid1 to raid5 reshape after crash
  • From: <shane-kernel@xxxxxx>
• Re: "bitmap file is out of date, doing full recovery"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Problem with a dgaded array (not related to my last question)
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: Kernel says there is not a valid superblock, but there is
  • From: Phillip Susi <phillsusi@xxxxxxxxx>
• Re: dm raid: pointer math issue in super_sync()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm raid: pointer math issue in super_sync()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: dm raid: pointer math issue in super_sync()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [patch] dm raid: pointer math issue in super_sync()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: [patch] DM RAID: fix a couple integer overflows
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: How do I set 'write-behind' on existing array?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Kernel says there is not a valid superblock, but there is
  • From: NeilBrown <neilb@xxxxxxx>
• Re: question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
  • From: Jason Keltz <jas@xxxxxxxxxxxx>
• question about MD raid rebuild performance degradation even with speed_limit_min/speed_limit_max set.
  • From: Jason Keltz <jas@xxxxxxxxxxxx>
• Kernel says there is not a valid superblock, but there is
  • From: Phillip Susi <phillsusi@xxxxxxxxx>
• How do I set 'write-behind' on existing array?
  • From: Hans Kraus <hans@xxxxxxxxxxxxxx>
• Re: Multiple drive failure after stupid mistake. Help needed
  • From: Per-Ola Stenborg <per-ola@xxxxxxxxxxx>
• Re: Multiple drive failure after stupid mistake. Help needed
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Multiple drive failure after stupid mistake. Help needed
  • From: Per-Ola Stenborg <per-ola@xxxxxxxxxxx>
• Re: Multiple drive failure after stupid mistake. Help needed
  • From: Per-Ola Stenborg <per-ola@xxxxxxxxxxx>
• Re: Multiple drive failure after stupid mistake. Help needed
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Multiple drive failure after stupid mistake. Help needed
  • From: Per-Ola Stenborg <per-ola@xxxxxxxxxxx>
• Re: migrate to bad block list
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: Fwd: I will pay money for the correct RAID recovery instructions
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Fwd: I will pay money for the correct RAID recovery instructions
  • From: Another Sillyname <anothersname@xxxxxxxxxxxxxx>
• Re: I will pay money for the correct RAID recovery instructions
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: I will pay money for the correct RAID recovery instructions
  • From: Ian Young <ian@xxxxxxxxxxxxxxx>
• Re: I will pay money for the correct RAID recovery instructions
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• I will pay money for the correct RAID recovery instructions
  • From: Ian Young <ian@xxxxxxxxxxxxxxx>
• Re: Preventing automatic start of ARRAY on Kubuntu
  • From: George Rapp <george.rapp@xxxxxxxxx>
• Preventing automatic start of ARRAY on Kubuntu
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: migrate to bad block list
  • From: NeilBrown <neilb@xxxxxxx>
• [GIT PULL REQUEST] md updates for 3.18
  • From: NeilBrown <neilb@xxxxxxx>
• migrate to bad block list
  • From: Michael Ryan <mryan@xxxxxxxxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• [GIT PULL] LLVMLinux patches for v3.18
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH] lib/raid6: Add log level to printks
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] lib/raid6: Add log level to printks
  • From: Anton Blanchard <anton@xxxxxxxxx>
• mdadm: /dev/sdX2 has wrong raid level.
  • From: Weedy <weedy2887@xxxxxxxxx>
• Re: mdadm --grow with --backup-file does not create backupfile?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: mdadm --grow with --backup-file does not create backupfile?
  • From: NeilBrown <neilb@xxxxxxx>
• mdadm --grow with --backup-file does not create backupfile?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: "bitmap file is out of date, doing full recovery"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Is it safe to shutdown while mdadm --grow is in progress.
  • From: NeilBrown <neilb@xxxxxxx>
• "bitmap file is out of date, doing full recovery"
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Good drive got kicked out - does mdadm assemble across suspend/resume like it does across reboots?
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Is it safe to shutdown while mdadm --grow is in progress.
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: Is it safe to shutdown while mdadm --grow is in progress.
  • From: NeilBrown <neilb@xxxxxxx>
• Is it safe to shutdown while mdadm --grow is in progress.
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• [PATCH] monitor: fix nullptr dereference when get_md_name() returns NULL
  • From: Sergey Vidishev <sergeyv@xxxxxxxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Extremely High mismatch_cnt on RAID1 system
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: writing zeros to bad sector results in persistent read error
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: writing zeros to bad sector results in persistent read error
  • From: Phillip Susi <psusi@xxxxxxxxxx>
• Re: Bad sequential performance of RAID5 with a lot of disk seeks
  • From: XiaoNi <xni@xxxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: auto assemble in read-only mode?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: UEFI and mdadm questions.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Extremely High mismatch_cnt on RAID1 system
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: Extremely High mismatch_cnt on RAID1 system
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• Re: Extremely High mismatch_cnt on RAID1 system
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: auto assemble in read-only mode?
  • From: Errol Neal <eneal@xxxxxxxxxxxxxxxxx>
• Re: Bad sequential performance of RAID5 with a lot of disk seeks
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Bad sequential performance of RAID5 with a lot of disk seeks
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: Bad sequential performance of RAID5 with a lot of disk seeks
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Bad sequential performance of RAID5 with a lot of disk seeks
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: Bad sequential performance of RAID5 with a lot of disk seeks
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: auto assemble in read-only mode?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: auto assemble in read-only mode?
  • From: Errol Neal <eneal@xxxxxxxxxxxxxxxxx>
• Bad sequential performance of RAID5 with a lot of disk seeks
  • From: "P. Gautschi" <linuxlist@xxxxxxxxxxxx>
• Re: Cancelling not pausing array check
  • From: Patrik Horník <patrik@xxxxxx>
• Re: Cancelling not pausing array check
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Cancelling not pausing array check
  • From: Patrik Horník <patrik@xxxxxx>
• Re: UEFI and mdadm questions.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Cancelling not pausing array check
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Cancelling not pausing array check
  • From: Patrik Horník <patrik@xxxxxx>
• Re: Cancelling not pausing array check
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Hot replacing device in RAID 6
  • From: Patrik Horník <patrik@xxxxxx>
• Cancelling not pausing array check
  • From: Patrik Horník <patrik@xxxxxx>
• auto assemble in read-only mode?
  • From: Errol Neal <eneal@xxxxxxxxxxxxxxxxx>
• Re: UEFI and mdadm questions.
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: UEFI and mdadm questions.
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: MD Raid1 hangs system on read error (3.10)
  • From: Matthijs Kooijman <matthijs@xxxxxxxx>
• Re: MD Raid1 hangs system on read error (3.10)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: 2 disk raid 5 failure
  • From: NeilBrown <neilb@xxxxxxx>
• Re: not enough operational mirrors
  • From: Ian Young <ian@xxxxxxxxxxxxxxx>
• Re: UEFI and mdadm questions.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Hot replacing device in RAID 6
  • From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: UEFI and mdadm questions.
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Hot replacing device in RAID 6
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Hot replacing device in RAID 6
  • From: Patrik Horník <patrik@xxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• Re: Please advise, strange "not enough to start the array while not clean"
  • From: Patrik Horník <patrik@xxxxxx>
• Re: 2 disk raid 5 failure
  • From: Jean-Paul Sergent <jpsergent@xxxxxxxxx>
• Re: 2 disk raid 5 failure
  • From: NeilBrown <neilb@xxxxxxx>
• MD Raid1 hangs system on read error (3.10)
  • From: Matthijs Kooijman <matthijs@xxxxxxxx>
• Re: 2 disk raid 5 failure
  • From: Jean-Paul Sergent <jpsergent@xxxxxxxxx>
• Re: 2 disk raid 5 failure
  • From: Jean-Paul Sergent <jpsergent@xxxxxxxxx>
• Re: 2 disk raid 5 failure
  • From: NeilBrown <neilb@xxxxxxx>
• 2 disk raid 5 failure
  • From: Jean-Paul Sergent <jpsergent@xxxxxxxxx>
• Re: raid6 appears not-degraded just after creation
  • From: Anssi Hannula <anssi.hannula@xxxxxx>
• Re: build-sys: do not depend on check_rundir for executables
  • From: NeilBrown <neilb@xxxxxxx>
• raid6 appears not-degraded just after creation
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• build-sys: do not depend on check_rundir for executables
  • From: Michael Tokarev <mjt@xxxxxxxxxx>
• Extremely High mismatch_cnt on RAID1 system
  • From: Dennis Grant <reccedg@xxxxxxxxx>
• [GIT PULL REQUEST] one last-minute update for md/raid5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: UEFI and mdadm questions.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: [dm-devel] dm-raid: add RAID discard support
  • From: "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>
• Re: dm-raid: add RAID discard support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-log-userspace: fix memory leak on failure path in dm_ulog_tfr_init()
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: dm-raid: add RAID discard support
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Why MD often doesn't correct read errors?
  • From: Ethan Wilson <ethan.wilson@xxxxxxxxxxxxx>
• Re: [dm-devel] dm-raid: add RAID discard support
  • From: NeilBrown <neilb@xxxxxxx>
• Re: UEFI and mdadm questions.
  • From: Anthonys Lists <antlists@xxxxxxxxxxxxxxx>
• [PATCH] dm-log-userspace: fix memory leak on failure path in dm_ulog_tfr_init()
  • From: Alexey Khoroshilov <khoroshilov@xxxxxxxxx>
• UEFI and mdadm questions.
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: Brassow Jonathan <jbrassow@xxxxxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: Roberto Spadim <rspadim@xxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: Robert L Mathews <lists@xxxxxxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: Andrei Banu <andrei.banu@xxxxxxxxxx>
• Re: raid1 - ssd, doubts
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• raid1 - ssd, doubts
  • From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: NeilBrown <neilb@xxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: dmadm question
  • From: NeilBrown <neilb@xxxxxxx>
• Re: dmadm question
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: NeilBrown <neilb@xxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• Re: /sys/block/md126 still exists even after stopping the array
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: BillStuff <billstuff2001@xxxxxxxxxxxxx>
• Re: Raid5 hang in 3.14.19
  • From: NeilBrown <neilb@xxxxxxx>
• BOUNTY REQUEST: Patch to RAID1/mdadm to DISABLE/ENABLE ALL SYNC ACTIONS, RECOVERY, etc
  • From: Errol Neal <eneal@xxxxxxxxxxxxxxxxx>
• Re: [RESEND PATCH] drivers/md: Use rcu_dereference() for accessing rcu pointer
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• [RESEND PATCH] drivers/md: Use rcu_dereference() for accessing rcu pointer
  • From: Pranith Kumar <bobby.prani@xxxxxxxxx>
• [PATCH] drivers/md: Use rcu_dereference() for accessing rcu pointer
  • From: Pranith Kumar <bobby.prani@xxxxxxxxx>
• Re: [PATCH] dm: sparse: Annotate field with __rcu for checking
  • From: "Paul E. McKenney" <paulmck@xxxxxxxxxxxxxxxxxx>
• [PATCH] md, sysfs, LLVMLinux: Remove nested function from bcache sysfs
  • From: Behan Webster <behanw@xxxxxxxxxxxxxxxxxx>
• Re: [GIT PULL REQUEST] late md/raid1 bug fixes for 3.17
  • From: NeilBrown <neilb@xxxxxxx>