Linux RAID Storage Date Index

• Thread Index

• [PATCH 1/5] MD: add a new disk role to present cache device
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 0/5] a caching layer for raid 5/6
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 2/5] raid5: directly use mddev->queue
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [dm-devel] [PATCH stable] block: discard bdi_unregister() in favour of bdi_destroy()
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH 2/2] md/raid5: remove unnecessary sh->count check
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• [PATCH 1/2] md/raid5: avoid duplicate code
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• Re: [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Removed disk vs. failed disk?
  • From: Hans Malissa <hmalissa@xxxxxx>
• Re: Potential race in dlm based messaging md-cluster.c
  • From: Abhijit Bhopatkar <abhopatk@xxxxxxxxx>
• Re: Potential race in dlm based messaging md-cluster.c
  • From: Abhijit Bhopatkar <abhopatk@xxxxxxxxx>
• Re: Potential race in dlm based messaging md-cluster.c
  • From: "Lidong Zhong" <lzhong@xxxxxxxx>
• raid6: general protection fault in async_copy_data
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: upgrade to jessie/newer kernel and mdadm problems
  • From: Jérôme Tytgat <jerome.tytgat@xxxxxxxxxx>
• Re: upgrade to jessie/newer kernel and mdadm problems
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [PATCH] md/raid5: init batch_xxx for new sh at resize_stripes
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• Re: [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: [PATCH] md/raid5: init batch_xxx for new sh at resize_stripes
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md/raid5: init batch_xxx for new sh at resize_stripes
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• Re: drive failing on same bus every couple weeks
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• drive failing on same bus every couple weeks
  • From: Stephen Burke <steve.burke.56@xxxxxxxxx>
• [SOLVED] Re: md-cluster documentation for testing?
  • From: Abhijit Bhopatkar <abhopatk@xxxxxxxxx>
• md-cluster documentation for testing?
  • From: Abhijit Bhopatkar <abhopatk@xxxxxxxxx>
• upgrade to jessie/newer kernel and mdadm problems
  • From: Jérôme Tytgat <jerome.tytgat@xxxxxxxxxx>
• Re: Help needed recovering from raid failure
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help needed recovering from raid failure
  • From: Peter van Es <vanes.peter@xxxxxxxxx>
• Re: Potential race in dlm based messaging md-cluster.c
  • From: Abhijit Bhopatkar <abhopatk@xxxxxxxxx>
• Re: Potential race in dlm based messaging md-cluster.c
  • From: Abhijit Bhopatkar <abhopatk@xxxxxxxxx>
• Potential race in dlm based messaging md-cluster.c
  • From: Abhijit Bhopatkar <abhopatk@xxxxxxxxx>
• Re: [PATCH 03/10] Create n bitmaps for clustered mode
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 09/10] mdadm: change the num of cluster node
  • From: Guoqing Jiang <gqJiang@xxxxxxxx>
• Re: [PATCH stable] block: discard bdi_unregister() in favour of bdi_destroy()
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid5: trivial coding style fix
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] md/raid5: fix typo
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid5: trivial coding style fix
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] md/raid5: fix typo
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 2/2] md/raid5: trivial coding style fix
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• [PATCH 1/2] md/raid5: fix typo
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• Re: [PATCH 09/10] mdadm: change the num of cluster node
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 04/10] Show all bitmaps while examining bitmap
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 09/10] mdadm: change the num of cluster node
  • From: Guoqing Jiang <jgq516@xxxxxxxxx>
• Re: [PATCH 08/10] mdadm: add the ability to change cluster name
  • From: Guoqing Jiang <jgq516@xxxxxxxxx>
• Re: [PATCH 05/10] Add a new clustered disk
  • From: Guoqing Jiang <jgq516@xxxxxxxxx>
• Re: [PATCH 04/10] Show all bitmaps while examining bitmap
  • From: Guoqing Jiang <gqJiang@xxxxxxxx>
• Re: [PATCH 03/10] Create n bitmaps for clustered mode
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 03/10] Create n bitmaps for clustered mode
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 03/10] Create n bitmaps for clustered mode
  • From: Guoqing Jiang <gqJiang@xxxxxxxx>
• Re: [PATCH 01/10] Add nodes option while creating md
  • From: Guoqing Jiang <gqJiang@xxxxxxxx>
• Re: BUG?: RAID6 reshape hung in reshape_request
  • From: David Wahler <dwahler@xxxxxxxxx>
• [PATCH stable] block: discard bdi_unregister() in favour of bdi_destroy()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH -stable] block: destroy bdi before blockdev is unregistered.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help needed recovering from raid failure
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/3 v2] wait: introduce wait_event_exclusive_cmd
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help needed recovering from raid failure
  • From: Peter van Es <vanes.peter@xxxxxxxxx>
• Re: [PATCH -stable] block: destroy bdi before blockdev is unregistered.
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH -stable] block: destroy bdi before blockdev is unregistered.
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH v2 1/4] dm-raid: Add support for the MD RAID0 personality
  • From: heinzm@xxxxxxxxxx
• [PATCH v2 2/4] md-raid0: conditional mddev->queue access to suit dm-raid
  • From: heinzm@xxxxxxxxxx
• [PATCH v2 3/4] Documentation: add version history entries for raid0 support _and_ forgotten devices_handle_discards_safely module paramater
  • From: heinzm@xxxxxxxxxx
• [PATCH v2 4/4] dm-raid: remove bogus parse_raid_params() comment about devices_handle_discards_safely
  • From: heinzm@xxxxxxxxxx
• [PATCH v2 0/4] dm-raid: Add support for the MD RAID0 personality
  • From: heinzm@xxxxxxxxxx
• Re: [PATCH 1/3 v2] wait: introduce wait_event_exclusive_cmd
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: Ming Lin <mlin@xxxxxxxxxx>
• [PATCH 2/3] md/raid5: split wait_for_stripe and introduce wait_for_quiescent
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• [PATCH 1/3 v2] wait: introduce wait_event_exclusive_cmd
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• [PATCH 3/3] md/raid5: per hash value and exclusive wait_for_stripe
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• Re: [PATCH 03/10] Create n bitmaps for clustered mode
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 09/10] mdadm: change the num of cluster node
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 08/10] mdadm: add the ability to change cluster name
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 05/10] Add a new clustered disk
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/3] wait: introduce wait_event_cmd_exclusive
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• Re: [PATCH 04/10] Show all bitmaps while examining bitmap
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 03/10] Create n bitmaps for clustered mode
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 03/10] Create n bitmaps for clustered mode
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 01/10] Add nodes option while creating md
  • From: NeilBrown <neilb@xxxxxxx>
• Re: PROBLEM: write to jbod with 3TB and 160GB drives hits BUG/oops
  • From: Charles Bertsch <cbertsch@xxxxxxx>
• Re: BUG?: RAID6 reshape hung in reshape_request
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help needed recovering from raid failure
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Massive RAID-1 desync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH -stable] block: destroy bdi before blockdev is unregistered.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: [PATCH -stable] block: destroy bdi before blockdev is unregistered.
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/3] wait: introduce wait_event_cmd_exclusive
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• [PATCH 06/10] md/raid5: get rid of bio_fits_rdev()
  • From: Ming Lin <mlin@xxxxxxxxxx>
• [PATCH 09/10] md/raid10: make sync_request_write() call bio_copy_data()
  • From: Ming Lin <mlin@xxxxxxxxxx>
• [PATCH 07/10] block: kill merge_bvec_fn() completely
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: BUG?: RAID6 reshape hung in reshape_request
  • From: David Wahler <dwahler@xxxxxxxxx>
• Re: [PATCH -stable] block: destroy bdi before blockdev is unregistered.
  • From: Jens Axboe <axboe@xxxxxx>
• Re: Paranoid mode for RAID-1 ?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Paranoid mode for RAID-1 ?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: [PATCH -stable] block: destroy bdi before blockdev is unregistered.
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: Paranoid mode for RAID-1 ?
  • From: Jean-Baptiste Thomas <cau2jeaf1honoq@xxxxxxxxxxx>
• Re: Help needed recovering from raid failure
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: <DKIM> Re: Paranoid mode for RAID-1 ?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Paranoid mode for RAID-1 ?
  • From: Jean-Baptiste Thomas <cau2jeaf1honoq@xxxxxxxxxxx>
• Re: <DKIM> Re: Paranoid mode for RAID-1 ?
  • From: Jean-Baptiste Thomas <cau2jeaf1honoq@xxxxxxxxxxx>
• Help needed recovering from raid failure
  • From: Peter van Es <vanes.peter@xxxxxxxxx>
• Re: Paranoid mode for RAID-1 ?
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Paranoid mode for RAID-1 ?
  • From: Pieter De Wit <pieter@xxxxxxxxxxxxx>
• Re: Paranoid mode for RAID-1 ? MD-RAID checksums
  • From: Pasi Kärkkäinen <pasik@xxxxxx>
• Re: Paranoid mode for RAID-1 ?
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Paranoid mode for RAID-1 ?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [PATCH] md/raid10: make sync_request_write() call bio_copy_data()
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Re: Paranoid mode for RAID-1 ?
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: BUG?: RAID6 reshape hung in reshape_request
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Paranoid mode for RAID-1 ?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Paranoid mode for RAID-1 ?
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Paranoid mode for RAID-1 ?
  • From: Jean-Baptiste Thomas <cau2jeaf1honoq@xxxxxxxxxxx>
• [PATCH 3/3 v2] md/raid5: per hash value and exclusive wait_for_stripe
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• [PATCH 2/3 v2] md/raid5: split wait_for_stripe and introduce wait_for_quiescent
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• [PATCH 1/3] wait: introduce wait_event_cmd_exclusive
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• [PATCH -stable] block: destroy bdi before blockdev is unregistered.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] md/raid5: split wait_for_stripe and introduce wait_for_quiesce
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] md/raid5: exclusive wait_for_stripe
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] md/raid5: split wait_for_stripe and introduce wait_for_quiesce
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• Fwd: BUG?: RAID6 reshape hung in reshape_request
  • From: David Wahler <dwahler@xxxxxxxxx>
• Re: BUG?: RAID6 reshape hung in reshape_request
  • From: NeilBrown <neilb@xxxxxxx>
• Re: PROBLEM: write to jbod with 3TB and 160GB drives hits BUG/oops
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] md/raid5: exclusive wait_for_stripe
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/2] md/raid5: split wait_for_stripe and introduce wait_for_quiesce
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md/raid10: make sync_request_write() call bio_copy_data()
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Massive RAID-1 desync
  • From: Jean-Baptiste Thomas <cau2jeaf1honoq@xxxxxxxxxxx>
• Re: [PATCH] md/raid10: make sync_request_write() call bio_copy_data()
  • From: Ming Lin <mlin@xxxxxxxxxx>
• BUG?: RAID6 reshape hung in reshape_request
  • From: David Wahler <dwahler@xxxxxxxxx>
• Re: [PATCH] md/raid10: make sync_request_write() call bio_copy_data()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH] md/raid10: make sync_request_write() call bio_copy_data()
  • From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
• Re: Massive RAID-1 desync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Massive RAID-1 desync
  • From: Jean-Baptiste Thomas <cau2jeaf1honoq@xxxxxxxxxxx>
• Re: Massive RAID-1 desync
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• [PATCH] md/raid10: make sync_request_write() call bio_copy_data()
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Massive RAID-1 desync
  • From: cau2jeaf1honoq@xxxxxxxxxxx
• Re: PROBLEM: write to jbod with 3TB and 160GB drives hits BUG/oops
  • From: Charles Bertsch <cbertsch@xxxxxxx>
• [PATCH 1/2] md/raid5: split wait_for_stripe and introduce wait_for_quiesce
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• [PATCH 2/2] md/raid5: exclusive wait_for_stripe
  • From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
• Re: Bisected, with rfc/patch - was Re: BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 10/10] Reuse the write_bitmap for update uuid
  • From: gqjiang@xxxxxxxx
• [PATCH 09/10] mdadm: change the num of cluster node
  • From: gqjiang@xxxxxxxx
• [PATCH 08/10] mdadm: add the ability to change cluster name
  • From: gqjiang@xxxxxxxx
• [PATCH 05/10] Add a new clustered disk
  • From: gqjiang@xxxxxxxx
• [PATCH 06/10] Convert a bitmap=none device to clustered
  • From: gqjiang@xxxxxxxx
• [PATCH 07/10] Skip clustered devices in incremental
  • From: gqjiang@xxxxxxxx
• [PATCH 03/10] Create n bitmaps for clustered mode
  • From: gqjiang@xxxxxxxx
• [PATCH 04/10] Show all bitmaps while examining bitmap
  • From: gqjiang@xxxxxxxx
• [PATCH 02/10] home-cluster while creating an array
  • From: gqjiang@xxxxxxxx
• [PATCH 01/10] Add nodes option while creating md
  • From: gqjiang@xxxxxxxx
• [PATCH 00/10] mdadm tool: add the support for cluster-md
  • From: gqjiang@xxxxxxxx
• Re: [PATCH v3 2/4] md/raid10: make sync_request_write() call bio_copy_data()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Bisected, with rfc/patch - was Re: BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: PROBLEM: write to jbod with 3TB and 160GB drives hits BUG/oops
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH v3 2/4] md/raid10: make sync_request_write() call bio_copy_data()
  • From: Ming Lin <mlin@xxxxxxxxxx>
• Degraded Array event on /dev/md1:thelma
  • From: Robert Steinmetz AIA <rob@xxxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: Bisected, with rfc/patch - was Re: BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: Bisected, with rfc/patch - was Re: BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bisected, with rfc/patch - was Re: BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
  • From: Christoph Hellwig <hch@xxxxxx>
• [GIT PULL REQUEST] md updates for 4.1
  • From: NeilBrown <neilb@xxxxxxx>
• Bisected, with rfc/patch - was Re: BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
  • From: NeilBrown <neilb@xxxxxxx>
• mdadm.conf issue after updating system
  • From: Stefan Lamby <webmaster@xxxxxxxxxxxxxx>
• Re: [PATCH 1/6] md-cluster: correct the num for comparison
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH RESEND] md-cluster: correct the num for comparison
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [RFC] A caching layer for RAID5/6
  • From: Shaohua Li <shli@xxxxxx>
• Re: Breaks LSI RAID on C600 chipset
  • From: "David F." <df7729@xxxxxxxxx>
• Re: [PATCH] md/raid5: don't do chunk aligned read on degraded array.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 6/6] md-cluster: re-add capabilities
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 5/6] md: re-add a failed disk
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/6] md-cluster: correct the num for comparison
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Raid 5 rebuild and Raid 6 reshape question
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Raid 5 rebuild and Raid 6 reshape question
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Reply:Re: mdadm hang when one subdev error(raid1)
  • From: 席智勇 <xizhiyong18@xxxxxxx>
• dm log: struct log_write_super and padding (was: Re: dm: add log writes target)
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• [PATCH] dm log: Use ULL suffix for 64-bit constants
  • From: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
• Re: Raid 5 rebuild and Raid 6 reshape question
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Raid 5 rebuild and Raid 6 reshape question
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Raid 5 rebuild and Raid 6 reshape question
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• [PATCH 1/3] dm-raid: Add support for the MD RAID0 personality
  • From: heinzm@xxxxxxxxxx
• [PATCH 3/3] raid0: conditional mddev->queue access to suit dm-raid
  • From: heinzm@xxxxxxxxxx
• [PATCH 0/3] dm-raid: Add support for the MD RAID0 personality
  • From: heinzm@xxxxxxxxxx
• [PATCH 2/3] dm core: export dm_disk to allow for dm-raid to pass it on to the MD raid0 personality
  • From: heinzm@xxxxxxxxxx
• Re: mdadm hang when one subdev error(raid1)
  • From: hui jiao <simonjiaoh@xxxxxxxxx>
• Re: [dm-devel] [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Ondrej Kozina <okozina@xxxxxxxxxx>
• WARNING: at kernel/sched/core.c:7331 __might_sleep+0xa6/0xb0() during boot
  • From: Petr Janecek <janecek@xxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• mdadm hang when one subdev error(raid1)
  • From: 席智勇 <xizhiyong18@xxxxxxx>
• [PATCH] Manage: prevent re-adding a raid1 device that was assembled on its own
  • From: nhdailey <nate.dailey@xxxxxxxxxxx>
• Re: RAID 5 "magicaly" become a RAID0
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH] dm crypt: fix error return code in crypt_ctr()
  • From: weiyj_lk@xxxxxxx
• Re: RAID 5 "magicaly" become a RAID0
  • From: Thomas MARCHESSEAU <marchesseau@xxxxxxxxx>
• Re: mdadm raid 5 one disk overwritten file system failed
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: mdadm raid 5 one disk overwritten file system failed
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• SV: mdadm raid 5 one disk overwritten file system failed
  • From: "John Andre Taule" <post@xxxxxxxxxxxxx>
• Re: BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
  • From: Azat Khuzhin <a3at.mail@xxxxxxxxx>
• Re: BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
  • From: Guoqing Jiang <GQJiang@xxxxxxxx>
• Re: [PATCH 2/4] md-cluster: remove capabilities
  • From: gary <gary.mdjiang@xxxxxxxxx>
• Re: Recovery Raid6 Degraded
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: Recovery Raid6 Degraded
  • From: Emanuel Domingos <emanuelsdrock@xxxxxxxxx>
• BUG: unable to handle kernel NULL pointer dereference at sysfs_do_create_link_sd (after mdadm)
  • From: Azat Khuzhin <a3at.mail@xxxxxxxxx>
• [PATCH 6/6] md-cluster: re-add capabilities
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 5/6] md: re-add a failed disk
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 4/6] md-cluster: remove capabilities
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 3/6] md: Export and rename find_rdev_nr_rcu
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 2/6] md: Export and rename kick_rdev_from_array
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 1/6] md-cluster: correct the num for comparison
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: Recovery Raid6 Degraded
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: Recovery Raid6 Degraded
  • From: Emanuel Domingos <emanuelsdrock@xxxxxxxxx>
• Re: Recovery Raid6 Degraded
  • From: Emanuel Domingos <emanuelsdrock@xxxxxxxxx>
• Re: Recovery Raid6 Degraded
  • From: Emanuel Domingos <emanuelsdrock@xxxxxxxxx>
• Re: RAID 5 "magicaly" become a RAID0
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Recovery Raid6 Degraded
  • From: Emanuel Domingos <emanuelsdrock@xxxxxxxxx>
• Re: [PATCH 2/4] md-cluster: remove capabilities
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pavel Machek <pavel@xxxxxx>
• Re: Recovery Raid6 Degraded
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Recovery Raid6 Degraded
  • From: Emanuel Domingos <emanuelsdrock@xxxxxxxxx>
• Re: [GIT PULL REQUEST] md fixes for late 4.0-rc
  • From: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
• Re: RAID 5 "magicaly" become a RAID0
  • From: Thomas MARCHESSEAU <marchesseau@xxxxxxxxx>
• Re: RAID 5 "magicaly" become a RAID0
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 5 "magicaly" become a RAID0
  • From: Thomas MARCHESSEAU <marchesseau@xxxxxxxxx>
• Re: mvsas panics and dies when attached to a port extender on newer kernels
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [PATCH 2/4] md-cluster: remove capabilities
  • From: Guoqing Jiang <GQJiang@xxxxxxxx>
• Re: RAID 5 "magicaly" become a RAID0
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [GIT PULL REQUEST] md fixes for late 4.0-rc
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID 5 "magicaly" become a RAID0
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• RAID 5 "magicaly" become a RAID0
  • From: Thomas MARCHESSEAU <marchesseau@xxxxxxxxx>
• mvsas panics and dies when attached to a port extender on newer kernels
  • From: Adam Talbot <ajtalbot1@xxxxxxxxx>
• Re: Breaks LSI RAID on C600 chipset
  • From: "David F." <df7729@xxxxxxxxx>
• Re: [PATCH 4/4] md-cluster: re-add
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH] md-cluster: correct the num for comparison
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 4/4] md-cluster: re-add
  • From: Guoqing Jiang <GQJiang@xxxxxxxx>
• [PATCH] md-cluster: correct the num for comparison
  • From: gqjiang@xxxxxxxx
• Re: interesting MD-xfs bug
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: interesting MD-xfs bug
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: [PATCH 4/4] md-cluster: re-add
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: interesting MD-xfs bug
  • From: NeilBrown <neilb@xxxxxxx>
• Personal insight - Re: Can't mount partitions after "mdadm --zero-superblock"
  • From: Eduard Rozenberg <eduardr@xxxxxxxxx>
• RAID IO stuck under heavy load (writes)
  • From: Tejas Rao <raot@xxxxxxx>
• Re: interesting MD-xfs bug
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: interesting MD-xfs bug
  • From: NeilBrown <neilb@xxxxxxx>
• Re: interesting MD-xfs bug
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: interesting MD-xfs bug
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: interesting MD-xfs bug
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: interesting MD-xfs bug
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• interesting MD-xfs bug
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• md: NULL ptr deref on xfstests generic/040
  • From: Sasha Levin <sasha.levin@xxxxxxxxxx>
• Re: [PATCH 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [PATCH 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Shaohua Li <shli@xxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Shaohua Li <shli@xxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2][v2] blk-plug: don't flush nested plug lists
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
• Re: [PATCH 4/4] md-cluster: re-add
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/4] re-add a failed disk
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/4] md-cluster: remove capabilities
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] IMSM: Count arrays per orom
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 4/4] md-cluster: re-add
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 3/4] re-add a failed disk
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 2/4] md-cluster: remove capabilities
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• [PATCH 1/4] md-cluster: fix bitmap sub-offset in bitmap_read_sb
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: Help recovering an interrupted raid0 reshape
  • From: "Jonathan Harker (Jesusaurus)" <jesusaurus@xxxxxxxxxxxxxxxxx>
• [PATCH] IMSM: Count arrays per orom
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: [PATCH] md: fix md io stats accounting broken
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help recovering an interrupted raid0 reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help recovering an interrupted raid0 reshape
  • From: "Jonathan Harker (Jesusaurus)" <jesusaurus@xxxxxxxxxxxxxxxxx>
• Re: Help recovering an interrupted raid0 reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help recovering an interrupted raid0 reshape
  • From: "Jonathan Harker (Jesusaurus)" <jesusaurus@xxxxxxxxxxxxxxxxx>
• Re: Creating volume in IMSM container
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help recovering an interrupted raid0 reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help recovering an interrupted raid0 reshape
  • From: "Jonathan Harker (Jesusaurus)" <jesusaurus@xxxxxxxxxxxxxxxxx>
• Creating volume in IMSM container
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: [dm-devel] [PATCH 3/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Alasdair G Kergon <agk@xxxxxxxxxx>
• Re: Help recovering an interrupted raid0 reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help recovering an interrupted raid0 reshape
  • From: "Jonathan Harker (Jesusaurus)" <jesusaurus@xxxxxxxxxxxxxxxxx>
• Re: multi-threaded raid5
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• Re: Can't mount partitions after "mdadm --zero-superblock"
  • From: Eduard Rozenberg <eduardr@xxxxxxxxx>
• Re: Can't mount partitions after "mdadm --zero-superblock"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Help recovering an interrupted raid0 reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Can't mount partitions after "mdadm --zero-superblock"
  • From: Eduard Rozenberg <eduardr@xxxxxxxxx>
• Re: write barrier in RAID5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: openSUSE 13.2: md - Need advice which raid1 super format (1.0/1.2) is preferred
  • From: NeilBrown <neilb@xxxxxxx>
• Re: multi-threaded raid5
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Can't mount partitions after "mdadm --zero-superblock"
  • From: NeilBrown <neilb@xxxxxxx>
• Can't mount partitions after "mdadm --zero-superblock"
  • From: Eduard Rozenberg <eduardr@xxxxxxxxx>
• Re: Help recovering an interrupted raid0 reshape
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Recovery of RAID 6 after three rapid disk events (disks are still working)
  • From: NeilBrown <neilb@xxxxxxx>
• Recovery of RAID 6 after three rapid disk events (disks are still working)
  • From: Mike <mboulter@xxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Why wipe crypto keys during suspend (was Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation)
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Two system lockups, Magic SysKeys works, RAID6 resyncs on reboot
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pavel Machek <pavel@xxxxxx>
• Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 2/3] dm: Export function dm_suspend_md()
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• [PATCH 3/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• [PATCH 1/3] PM suspend/hibernate: Call notifier after freezing processes
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
  • From: Pali Rohár <pali.rohar@xxxxxxxxx>
• Help recovering an interrupted raid0 reshape
  • From: "Jonathan Harker (Jesusaurus)" <jesusaurus@xxxxxxxxxxxxxxxxx>
• Re: Breaks LSI RAID on C600 chipset
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Breaks LSI RAID on C600 chipset
  • From: "David F." <df7729@xxxxxxxxx>
• [PATCH] md: fix md io stats accounting broken
  • From: Gu Zheng <guz.fnst@xxxxxxxxxxxxxx>
• Re: [neilb@xxxxxxx: Re: MD request counter broken on 4.0-rc5 RAID1]
  • From: Simon Kirby <sim@xxxxxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Shaohua Li <shli@xxxxxx>
• Re: /dev/md0 can't be created
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Shaohua Li <shli@xxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Jens Axboe <axboe@xxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Two system lockups, Magic SysKeys works, RAID6 resyncs on reboot
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• write barrier in RAID5
  • From: Eric Mei <meijia@xxxxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Shaohua Li <shli@xxxxxx>
• Re: [PATCH] Fix bitmap offset calculations
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH] Fix bitmap offset calculations
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Re: [neilb@xxxxxxx: Re: MD request counter broken on 4.0-rc5 RAID1]
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [neilb@xxxxxxx: Re: MD request counter broken on 4.0-rc5 RAID1]
  • From: Gu Zheng <guz.fnst@xxxxxxxxxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Shaohua Li <shli@xxxxxx>
• Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: /dev/md0 can't be created
  • From: NeilBrown <neilb@xxxxxxx>
• openSUSE 13.2: md - Need advice which raid1 super format (1.0/1.2) is preferred
  • From: Dieter Nützel <Dieter@xxxxxxxxxxxxx>
• Re: no good deed goes unpunished...
  • From: Dave Stevens <geek@xxxxxxxxxxxx>
• Re: Two system lockups, Magic SysKeys works, RAID6 resyncs on reboot
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: no good deed goes unpunished...
  • From: Dave Stevens <geek@xxxxxxxxxxxx>
• Re: no good deed goes unpunished...
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: no good deed goes unpunished...
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: no good deed goes unpunished...
  • From: Dave Stevens <geek@xxxxxxxxxxxx>
• Re: Two system lockups, Magic SysKeys works, RAID6 resyncs on reboot
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• multi-threaded raid5
  • From: stkoupr <p.kouril@xxxxxx>
• Two system lockups, Magic SysKeys works, RAID6 resyncs on reboot
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• [RFC] raid5: add a log device to fix raid5/6 write hole issue
  • From: Shaohua Li <shli@xxxxxx>
• [PATCH 2/7] dm_table: Use bool function return values of true/false not 1/0
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH 2/7] dm_table: Use bool function return values of true/false not 1/0
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH 0/7] drivers: Use bool function return values true/false not 1/0
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: mdadm RAID6 "active" with spares and failed disks; need help
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Read-only mounts (was mdadm RAID6 "active" with spares and failed disks; need help)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: mdadm RAID6 "active" with spares and failed disks; need help
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: no good deed goes unpunished...
  • From: Dave Stevens <geek@xxxxxxxxxxxx>
• Re: mdadm RAID6 "active" with spares and failed disks; need help
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: no good deed goes unpunished...
  • From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
• Re: no good deed goes unpunished...
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: no good deed goes unpunished...
  • From: Dave Stevens <geek@xxxxxxxxxxxx>
• Re: mdadm RAID6 "active" with spares and failed disks; need help
  • From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
• Re: no good deed goes unpunished...
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• re: no good deed goes unpunished...
  • From: Dave Stevens <geek@xxxxxxxxxxxx>
• Re: missing arrays after OS upgrade
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: /dev/md0 can't be created
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: no good deed goes unpunished...
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• no good deed goes unpunished...
  • From: Dave Stevens <geek@xxxxxxxxxxxx>
• Re: /dev/md0 can't be created
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Badblocks and degraded array.
  • From: NeilBrown <neilb@xxxxxxx>
• Badblocks and degraded array.
  • From: Wakko Warner <wakko@xxxxxxxxxxxx>
• [PATCH] Fix minor typo in mdadm manpage.
  • From: Andrew Burgess <andrew.burgess@xxxxxxxxxxxx>
• Re: RAID6 won't reassemble after disk controller failure
  • From: Scott Sinno <sinno@xxxxxxxxx>
• Re: RAID6 won't reassemble after disk controller failure
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: RAID6 won't reassemble after disk controller failure
  • From: Scott Sinno <sinno@xxxxxxxxx>
• Re: RAID6 won't reassemble after disk controller failure
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: RAID6 won't reassemble after disk controller failure
  • From: Scott Sinno <sinno@xxxxxxxxx>
• Re: RAID6 won't reassemble after disk controller failure
  • From: Scott Sinno <sinno@xxxxxxxxx>
• Re: RAID6 won't reassemble after disk controller failure
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• RAID6 won't reassemble after disk controller failure
  • From: Scott Sinno <sinno@xxxxxxxxx>
• Re: missing arrays after OS upgrade
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: missing arrays after OS upgrade
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: /dev/md0 can't be created
  • From: NeilBrown <neilb@xxxxxxx>
• /dev/md0 can't be created
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH] Fix bitmap offset calculations
  • From: NeilBrown <neilb@xxxxxxx>
• Re: MD request counter broken on 4.0-rc5 RAID1
  • From: NeilBrown <neilb@xxxxxxx>
• MD request counter broken on 4.0-rc5 RAID1
  • From: Simon Kirby <sim@xxxxxxxxxx>
• Re: missing arrays after OS upgrade
  • From: Phil Turmel <philip@xxxxxxxxxx>
• missing arrays after OS upgrade
  • From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Rik van Riel <riel@xxxxxxxxxx>
• Monitor new badblocks
  • From: Serge Bartosh <sb@xxxxxxxxxx>
• [PATCH] Fix bitmap offset calculations
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 1/1] Make bm_blocks to match previous semantic
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• resize a 'far' RAID10 ?
  • From: Wolfgang Denk <wd@xxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
• Re: is mdadm RAID1 disk full sync
  • From: lingli tang <tanglingli001@xxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Rik van Riel <riel@xxxxxxxxxx>
• Re: is mdadm RAID1 disk full sync
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Thanks for the awesome
  • From: Phil Ingram <pingram.au@xxxxxxxxx>
• Re: is mdadm RAID1 disk full sync
  • From: lingli tang <tanglingli001@xxxxxxxxx>
• Re: Hung RAID5 array with discard
  • From: NeilBrown <neilb@xxxxxxx>
• Re: is mdadm RAID1 disk full sync
  • From: NeilBrown <neilb@xxxxxxx>
• [GIT PULL REQUEST] one bugfix for md in 4.0-rc
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
• Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
• Re: is mdadm RAID1 disk full sync
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: is mdadm RAID1 disk full sync
  • From: lingli tang <tanglingli001@xxxxxxxxx>
• Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
• Re: is mdadm RAID1 disk full sync
  • From: lingli tang <tanglingli001@xxxxxxxxx>
• Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
• Re: is mdadm RAID1 disk full sync
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: is mdadm RAID1 disk full sync
  • From: NeilBrown <neilb@xxxxxxx>
• Re: is mdadm RAID1 disk full sync
  • From: lingli tang <tanglingli001@xxxxxxxxx>
• Re: is mdadm RAID1 disk full sync
  • From: NeilBrown <neilb@xxxxxxx>
• is mdadm RAID1 disk full sync
  • From: lingli tang <tanglingli001@xxxxxxxxx>
• Why people recommend to disable NCQ for MD RAID ?
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Re: [PATCH 1/1] Make bm_blocks to match previous semantic
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Rik van Riel <riel@xxxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxxxx>
• Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Rik van Riel <riel@xxxxxxxxxx>
• Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Rik van Riel <riel@xxxxxxxxxx>
• Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid5: don't do chunk aligned read on degraded array.
  • From: Eric Mei <meijia@xxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid5: don't do chunk aligned read on degraded array.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md/raid5: don't do chunk aligned read on degraded array.
  • From: Eric Mei <meijia@xxxxxxxxx>
• Re: [PATCH 1/1] Make bm_blocks to match previous semantic
  • From: Guoqing Jiang <GQJiang@xxxxxxxx>
• Re: Converting a .90 raid superblock to version 1.0 and whether--size parameter is needed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Converting a .90 raid superblock to version 1.0 and whether--size parameter is needed
  • From: Sean Harris <sean@xxxxxxxxxxxxx>
• Re: dm log userspace: use mempool_create_kmalloc_pool()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxxxx>
• Re: [Linux-nvdimm] [RFC PATCH 3/7] dma-mapping: allow archs to optionally specify a ->map_pfn() operation
  • From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
• Re: [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Boaz Harrosh <openosd@xxxxxxxxx>
• Re: Converting a .90 raid superblock to version 1.0 and whether--size parameter is needed
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/1] Make bm_blocks to match previous semantic
  • From: NeilBrown <neilb@xxxxxxx>
• Converting a .90 raid superblock to version 1.0 and whether--size parameter is needed
  • From: Sean Harris <sean@xxxxxxxxxxxxx>
• chunk size K, KB, KiB
  • From: Chris Murphy <chris@xxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 2/7] block: convert bio_vec.bv_page to bv_pfn
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [RFC PATCH 2/7] block: convert bio_vec.bv_page to bv_pfn
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxxxx>
• [PATCH] dm delay: use msecs_to_jiffies for time conversion
  • From: Nicholas Mc Guire <hofrat@xxxxxxxxx>
• [PATCH 1/1] Make bm_blocks to match previous semantic
  • From: jgq516@xxxxxxxxx
• Re: [RFC PATCH 2/7] block: convert bio_vec.bv_page to bv_pfn
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• [RFC PATCH 0/7] evacuate struct page from the block layer
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [RFC PATCH 3/7] dma-mapping: allow archs to optionally specify a ->map_pfn() operation
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [RFC PATCH 1/7] block: add helpers for accessing a bio_vec page
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [RFC PATCH 4/7] scatterlist: use sg_phys()
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [RFC PATCH 2/7] block: convert bio_vec.bv_page to bv_pfn
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [RFC PATCH 6/7] x86: support dma_map_pfn()
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [RFC PATCH 7/7] block: base support for pfn i/o
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [RFC PATCH 5/7] scatterlist: support "page-less" (__pfn_t only) entries
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] kernfs: handle poll correctly on 'direct_read' files.
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Bad Block Management in RAID1 and "Faulty"
  • From: Ankur Bose <ankur.bose@xxxxxxxxxx>
• [PATCH] kernfs: handle poll correctly on 'direct_read' files.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] dm log userspace: base: fix compile warning
  • From: Nicholas Mc Guire <hofrat@xxxxxxxxx>
• [PATCH] dm log userspace: transfer: match wait_for_completion_timeout return type
  • From: Nicholas Mc Guire <hofrat@xxxxxxxxx>
• /dev/md/xxx sporadically unavailable after mdadm --assemble /dev/md/xxx
  • From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
• Re: Inject I/O latency for RAID5/6 read and writes
  • From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
• Bad block management in raid1
  • From: Ankur Bose <ankur.bose@xxxxxxxxxx>
• Re: Inject I/O latency for RAID5/6 read and writes
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Please kindly read my message
  • From: Sandra toyin rain elizabeth <toyinelizabeth803@xxxxxxxxx>
• Re: Raid 5: all devices marked spare, cannot assemble
  • From: Paul Boven <boven@xxxxxxx>
• Re: Raid 5: all devices marked spare, cannot assemble
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Raid 5: all devices marked spare, cannot assemble
  • From: Paul Boven <boven@xxxxxxx>
• Re: dm log userspace: use mempool_create_kmalloc_pool()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• mdraid with device-mapper multipath devices
  • From: Sushma Gurram <Sushma.Gurram@xxxxxxxxxxx>
• Re: Raid 10 Issue - Swapping Data from Array to Array [SOLVED]
  • From: Stefan Lamby <webmaster@xxxxxxxxxxxxxx>
• Re: Raid 10 Issue
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• Re: two raid issues
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [patch] dm log userspace: use mempool_create_kmalloc_pool()
  • From: David Rientjes <rientjes@xxxxxxxxxx>
• two raid issues
  • From: Dave Stevens <geek@xxxxxxxxxxxx>
• Re: Raid 10 Issue - Booting in case raid failed
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: raid 10 - Recovering raid - what stats are most helpfull?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: raid 10 - Recovering raid - what stats are most helpfull?
  • From: Stefan Lamby <webmaster@xxxxxxxxxxxxxx>
• Re: Raid 10 Issue - Booting in case raid failed
  • From: Stefan Lamby <webmaster@xxxxxxxxxxxxxx>
• Re: Raid 10 Issue - Swapping Data from Array to Array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Raid 10 Issue - Swapping Data from Array to Array
  • From: Stefan Lamby <webmaster@xxxxxxxxxxxxxx>
• Re: Raid 10 Issue [SOLVED]
  • From: Stefan Lamby <webmaster@xxxxxxxxxxxxxx>
• Re: Last working drive in RAID1
  • From: Chris <email.bug@xxxxxxxx>
• Re: Raid 10 Issue
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: Last working drive in RAID1
  • From: Chris <email.bug@xxxxxxxx>
• Re: Last working drive in RAID1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Last working drive in RAID1
  • From: Eric Mei <meijia@xxxxxxxxx>
• Re: Raid 10 Issue
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Last working drive in RAID1
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Last working drive in RAID1
  • From: Eric Mei <meijia@xxxxxxxxx>
• smartctl-timeouts_v1.01 scripts (scterc timeout fixes)
  • From: Chris <email.bug@xxxxxxxx>
• Raid 10 Issue
  • From: Stefan Lamby <webmaster@xxxxxxxxxxxxxx>
• Re: Last working drive in RAID1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Help with raid 10 issue
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Help with raid 10 issue
  • From: Stefan Lamby <sl@xxxxxxxx>
• Re: Last working drive in RAID1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Last working drive in RAID1
  • From: Eric Mei <meijia@xxxxxxxxx>
• Re: Hung RAID5 array with discard
  • From: Terry Hardie <thardie@xxxxxxxxxxxxxxxx>
• Re: Last working drive in RAID1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID0 & diskstats.
  • From: NeilBrown <neilb@xxxxxxx>
• Last working drive in RAID1
  • From: Eric Mei <meijia@xxxxxxxxx>
• Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH] IncRemove: Set "auto-read" only after successful excl open.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] IMSM-orom: make sure, that device list is supported
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Fix stray --cluster-confrim crash
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Communication Framework: fix semicolon.cocci warnings
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH md] recover_bitmaps() can be static
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Riad scrub generated errors, should I worry?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Riad scrub generated errors, should I worry?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Riad scrub generated errors, should I worry?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Riad scrub generated errors, should I worry?
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• Re: Riad scrub generated errors, should I worry?
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Riad scrub generated errors, should I worry?
  • From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
• [PATCH] Fix stray --cluster-confrim crash
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Riad scrub generated errors, should I worry?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Riad scrub generated errors, should I worry?
  • From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
• [GIT PULL REQUEST] md fixes for 4.0
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Bug#779412: block devices loosing state after resume: trigger udev rules to re-apply settings
  • From: Chris <email.bug@xxxxxxxx>
• Re: Bug#779412: block devices loosing state after resume: trigger udev rules to re-apply settings
  • From: Michael Biebl <biebl@xxxxxxxxxx>
• block devices loosing state after resume: trigger udev rules to re-apply settings
  • From: Chris <email.bug@xxxxxxxx>
• [PATCH] Communication Framework: fix semicolon.cocci warnings
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• [md:for-next 14/48] drivers/md/md-cluster.c:190:6: sparse: symbol 'recover_bitmaps' was not declared. Should it be static?
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• [PATCH md] recover_bitmaps() can be static
  • From: kbuild test robot <fengguang.wu@xxxxxxxxx>
• Re: raid0: "clean" state on drive failure/removal
  • From: NeilBrown <neilb@xxxxxxx>
• raid0: "clean" state on drive failure/removal
  • From: Sushma Gurram <Sushma.Gurram@xxxxxxxxxxx>
• Re: [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• [PATCH] IncRemove: Set "auto-read" only after successful excl open.
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH] IMSM-orom: make sure, that device list is supported
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• smartctl-timeouts_v1.0 (erc timeout fix)
  • From: Chris <email.bug@xxxxxxxx>
• Re: RAID6 write I/O amplification?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID6 write I/O amplification?
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Re: [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: [PATCH 4/5] IncrementalScan(): Make sure 'st' is valid before dereferencing it
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH 4/5] IncrementalScan(): Make sure 'st' is valid before dereferencing it
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 4/5] IncrementalScan(): Make sure 'st' is valid before dereferencing it
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: udev rules and scripts (erc timeout fix)
  • From: Chris <email.bug@xxxxxxxx>
• Re: [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: [dm-devel] [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: [PATCH 2/5] Check return of stat() to avoid covscan complaining
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [dm-devel] [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/5] Check return of stat() to avoid covscan complaining
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/5] Check return of stat() to avoid covscan complaining
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 2/5] Check return of stat() to avoid covscan complaining
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH 1/5] Grow.c: Fix classic readlink() buffer overflow
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 4/5] IncrementalScan(): Make sure 'st' is valid before dereferencing it
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 5/5] write_super_imsm_spares(): C statements are terminated by ;
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/5] Fix issues reported by covscan and newer GCC
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 2/5] Check return of stat() to avoid covscan complaining
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: An old "write-mostly" read balance issue
  • From: Tomáš Hodek <tomas.hodek@xxxxxxxx>
• AW: RAID6 write I/O amplification?
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• RAID6 write I/O amplification?
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Inject I/O latency for RAID5/6 read and writes
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Re: [PATCH 02/24] Add number of nodes to bitmap structure for clustering
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: [dm-devel] [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
• Re: Optimal chunk size for RAID5?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 02/24] Add number of nodes to bitmap structure for clustering
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Optimal chunk size for RAID5?
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: [dm-devel] [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Metadata > 0.90 and auto-assemble
  • From: NeilBrown <neilb@xxxxxxx>
• Re: An old "write-mostly" read balance issue
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Metadata > 0.90 and auto-assemble
  • From: Mark Knecht <markknecht@xxxxxxxxx>
• Re: Optimal chunk size for RAID5?
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Metadata > 0.90 and auto-assemble
  • From: Joshua Kinard <kumba@xxxxxxxxxx>
• Re: Metadata > 0.90 and auto-assemble
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Metadata > 0.90 and auto-assemble
  • From: Joshua Kinard <kumba@xxxxxxxxxx>
• Re: Optimal chunk size for RAID5?
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Re: re-add POLICY
  • From: Chris <email.bug@xxxxxxxx>
• Re: Optimal chunk size for RAID5?
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: Optimal chunk size for RAID5?
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Optimal chunk size for RAID5?
  • From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
• Re: udev rules and scripts (erc timeout fix)
  • From: Chris <email.bug@xxxxxxxx>
• rules and scripts (erc timeout fix)
  • From: email.bug@xxxxxxxx
• Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: [PATCH] [md] raid5: check faulty flag for array status during recovery.
  • From: Eric Mei <meijia@xxxxxxxxx>
• Re: mdadm raid 5 one disk overwritten file system failed
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH] [md] raid5: check faulty flag for array status during recovery.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm raid 5 one disk overwritten file system failed
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• SV: mdadm raid 5 one disk overwritten file system failed
  • From: "John Andre Taule" <post@xxxxxxxxxxxxx>
• Re: mdadm raid 5 one disk overwritten file system failed
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: mdadm raid 5 one disk overwritten file system failed
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• SV: mdadm raid 5 one disk overwritten file system failed
  • From: "John Andre Taule" <post@xxxxxxxxxxxxx>
• Re: mdadm raid 5 one disk overwritten file system failed
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• mdadm raid 5 one disk overwritten file system failed
  • From: "John Andre Taule" <post@xxxxxxxxxxxxx>
• Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• [PATCH/RFC/RFT] md: allow resync to go faster when there is competing IO.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Potential Bug in "echo 0 > /dev/md0"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: help with the little script (erc timout fix)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Potential Bug in "echo 0 > /dev/md0"
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: Potential Bug in "echo 0 > /dev/md0"
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• Re: Potential Bug in "echo 0 > /dev/md0"
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Potential Bug in "echo 0 > /dev/md0"
  • From: Alireza Haghdoost <alireza@xxxxxxxxxx>
• help with the little script (erc timout fix)
  • From: Chris <email.bug@xxxxxxxx>
• Re: RAID1 might_sleep() warning on 3.19-rc7
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• mdadm monitoring for RAID-1 - no events after pulling out all disks.
  • From: Iakiv Shchelkunov <iakiv.shchelkunov@xxxxxxxxxxxxxxx>
• Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
  • From: Chris <email.bug@xxxxxxxx>
• Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: NeilBrown <neilb@xxxxxxx>
• [GIT PULL REQUEST] some more bugfixes for md.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID1 might_sleep() warning on 3.19-rc7
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] Revert "md: When RAID5 is dirty, force reconstruct-write instead of read-modify-write."
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] Revert "md: When RAID5 is dirty, force reconstruct-write instead of read-modify-write."
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
  • From: Chris <email.bug@xxxxxxxx>
• Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: re-add POLICY
  • From: Chris <email.bug@xxxxxxxx>
• Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
  • From: Chris <email.bug@xxxxxxxx>
• Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
  • From: Chris <email.bug@xxxxxxxx>
• Re: What are mdadm maintainers to do? (was: desktop disk's error recovery timeouts)
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: All drive in Raid 5 are in 'spare' mode
  • From: Dush <tomdush@xxxxxxxxx>
• Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
  • From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
• Re: All drive in Raid 5 are in 'spare' mode
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: What are mdadm maintainers to do?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: All drive in Raid 5 are in 'spare' mode
  • From: Dush <tomdush@xxxxxxxxx>
• What are mdadm maintainers to do? (was: desktop disk's error recovery timeouts)
  • From: Chris <email.bug@xxxxxxxx>
• Re: desktop disk's error recovery timouts
  • From: Phil Turmel <philip@xxxxxxxxxx>
• desktop disk's error recovery timouts (was: re-add POLICY)
  • From: Chris <email.bug@xxxxxxxx>
• Re: re-add POLICY
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID 1 metadata - keep separate from mirror disks ?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: re-add POLICY
  • From: Chris <email.bug@xxxxxxxx>
• RE: RAID 1 metadata - keep separate from mirror disks ?
  • From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
• Re: mdadm failed to remove internal bitmap
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm failed to remove internal bitmap
  • From: gary <gary.mdjiang@xxxxxxxxx>
• Re: [md PATCH] md/raid1: round up to bdev_logical_block_size in narrow_write_error
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdadm failed to remove internal bitmap
  • From: NeilBrown <neilb@xxxxxxx>
• Re: re-add POLICY
  • From: NeilBrown <neilb@xxxxxxx>
• Re: re-add POLICY: conflict detection?
  • From: Chris <email.bug@xxxxxxxx>
• Re: update mdadm version to 3.3.2 in Centos 6.4
  • From: alpha lin <lin.alpha@xxxxxxxxx>
• [PATCH 2/3] md raid0: access mddev->queue (request queue member) conditionally because it is not set when accessed from dm-raid
  • From: heinzm@xxxxxxxxxx
• [PATCH 1/3] md core: add 2 API functions for takeover and resize to support dm-raid
  • From: heinzm@xxxxxxxxxx
• [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
  • From: heinzm@xxxxxxxxxx
• [PATCH 3/3] md bitmap: export bitmap_destroy() to support dm-raid down takover to raid0
  • From: heinzm@xxxxxxxxxx
• re-add POLICY
  • From: Chris <email.bug@xxxxxxxx>
• [PATCH 0/1] Bug fix for mdadm 3.3 with large md device numbers
  • From: Mike Lovell <mlovell@xxxxxxxxxxxx>
• [PATCH 1/1] Use dev_t for devnm2devid and devid2devnm
  • From: Mike Lovell <mlovell@xxxxxxxxxxxx>
• Re: [PATCH RESEND] Monitor: fix for regression with container devices
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: RAID1 might_sleep() warning on 3.19-rc7
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: RAID1 might_sleep() warning on 3.19-rc7
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• mdadm failed to remove internal bitmap
  • From: gary <gary.mdjiang@xxxxxxxxx>
• Re: RAID1 might_sleep() warning on 3.19-rc7
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID1 might_sleep() warning on 3.19-rc7
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: raid1 narrow_write_error with 4K disks, sd "bad block number requested" messages
  • From: NeilBrown <neilb@xxxxxxx>
• Re: RAID1 might_sleep() warning on 3.19-rc7
  • From: NeilBrown <neilb@xxxxxxx>
• [md PATCH] md/raid1: round up to bdev_logical_block_size in narrow_write_error
  • From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
• Re: raid1 narrow_write_error with 4K disks, sd "bad block number requested" messages
  • From: Nate Dailey <nate.dailey@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: RAID 1 metadata - keep separate from mirror disks ?
  • From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
• Re: please help - raid 1 degraded
  • From: Roaming <antmbox@xxxxxxxxxxxxxxx>
• [GIT PULL REQUEST] md updates for 3.20
  • From: NeilBrown <neilb@xxxxxxx>
• Re: please help - raid 1 degraded
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: [PATCH RESEND] Change way of printing name of a process
  • From: NeilBrown <neilb@xxxxxxx>
• Re: All drive in Raid 5 are in 'spare' mode
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: please help - raid 1 degraded
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: please help - raid 1 degraded
  • From: sunruh@xxxxxxxxxxxx
• Re: please help - raid 1 degraded
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Wierd: Degrading while recovering raid5
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: please help - raid 1 degraded
  • From: sunruh@xxxxxxxxxxxx
• Re: please help - raid 1 degraded
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Wierd: Degrading while recovering raid5
  • From: Kyle Logue <teque5@xxxxxxxxx>
• [PATCH RESEND] Change way of printing name of a process
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• All drive in Raid 5 are in 'spare' mode
  • From: Dush <tomdush@xxxxxxxxx>
• [PATCH 1/1] mddev_create(): choose /dev/md/ name over /dev/mdX
  • From: Jes.Sorensen@xxxxxxxxxx
• [PATCH 0/1] RFC: Use /dev/md/X as default name
  • From: Jes.Sorensen@xxxxxxxxxx
• Re: dead RAID6 array on CentOS6.6 / kernel 3.19
  • From: Adam Thompson <athompso@xxxxxxxxxxxx>
• please help - raid 1 degraded
  • From: sunruh@xxxxxxxxxxxx
• Re: [PATCH 00/24] Clustered MD RAID1
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Re: RAID 1 metadata - keep separate from mirror disks ?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Wierd: Degrading while recovering raid5
  • From: Phil Turmel <philip@xxxxxxxxxx>
• RAID 1 metadata - keep separate from mirror disks ?
  • From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
• Re: Wierd: Degrading while recovering raid5
  • From: Kyle Logue <teque5@xxxxxxxxx>
• Re: [PATCH RESEND] Monitor: fix for regression with container devices
  • From: NeilBrown <neilb@xxxxxxx>
• Re: dead RAID6 array on CentOS6.6 / kernel 3.19
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 00/24] Clustered MD RAID1
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [Board] dead RAID6 array on CentOS6.6 / kernel 3.19
  • From: Adam Thompson <athompso@xxxxxxxxxxxx>
• Re: dead RAID6 array on CentOS6.6 / kernel 3.19
  • From: Adam Thompson <athompso@xxxxxxxxxxxx>
• Re: dead RAID6 array on CentOS6.6 / kernel 3.19
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: dead RAID6 array on CentOS6.6 / kernel 3.19
  • From: Adam Thompson <athompso@xxxxxxxxxxxx>
• Re: dead RAID6 array on CentOS6.6 / kernel 3.19
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: ignoring %s as it reports %s as failed
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Wierd: Degrading while recovering raid5
  • From: Phil Turmel <philip@xxxxxxxxxx>
• dead RAID6 array on CentOS6.6 / kernel 3.19
  • From: Adam Thompson <athompso@xxxxxxxxxxxx>
• [no subject]
  • From: Kyle Logue <teque5@xxxxxxxxx>
• Re: Wierd: Degrading while recovering raid5
  • From: Kyle Logue <teque5@xxxxxxxxx>
• Re: [PATCH 00/24] Clustered MD RAID1
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• ignoring %s as it reports %s as failed
  • From: Valentijn <v@xxxxxxxxxxxxxxxx>
• Re: Wierd: Degrading while recovering raid5
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: RAID1 might_sleep() warning on 3.19-rc7
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: RAID1 might_sleep() warning on 3.19-rc7
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: Wierd: Degrading while recovering raid5
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Upgrading storage server
  • From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
• Wierd: Degrading while recovering raid5
  • From: Kyle Logue <teque5@xxxxxxxxx>
• Re: Upgrading storage server
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: RAID1 might_sleep() warning on 3.19-rc7
  • From: NeilBrown <neilb@xxxxxxx>
• Re: mdsadm -A won't assemble my array
  • From: "G. Michael Carter" <mikey@xxxxxxxxxxxxxxx>
• 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>