Linux RAID Storage Date Index

• Thread Index

• [PATCH V2 1/8] md-cluster/raid10: resize all the bitmaps before start reshape
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH V2 0/8] md-cluster: add grow support for raid10
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH] imsm: update metadata correctly while raid10 double degradation
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• Re: RAID 1 Performance (Backups)
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: RAID 1 Performance (Backups)
  • From: Shaun Glass <shaunglass@xxxxxxxxx>
• Re: RAID 1 Performance (Backups)
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: RAID 1 Performance (Backups)
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• RAID 1 Performance (Backups)
  • From: Shaun Glass <shaunglass@xxxxxxxxx>
• Re: [PATCH] md/bitmap: use mddev_suspend/resume instead of ->quiesce()
  • From: Jinpu Wang <jinpu.wang@xxxxxxxxxxxxxxxx>
• [PATCH] dm: add secdel target
  • From: Vitaly Chikunov <vt@xxxxxxxxxxxx>
• raid10 - failed drive & botched recovery
  • From: Elvis Dumbledore <elvispdumbledore@xxxxxxxxx>
• Re: raid5 - failed to assemble array
  • From: Geoff Richmond <Geoff.Richmond@xxxxxxxxxxxx>
• Re: raid5 - failed to assemble array
  • From: François Goudal <francois@xxxxxxxxxx>
• raid5 - failed to assemble array
  • From: Geoff Richmond <Geoff.Richmond@xxxxxxxxxxxx>
• Re: [Update PATCH 1/8] md-cluster/raid10: resize all the bitmaps before start reshape
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 0/8] md-cluster: add grow support for raid10
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [Update PATCH 1/8] md-cluster/raid10: resize all the bitmaps before start reshape
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 1/8] md-cluster/raid10: resize all the bitmaps before start reshape
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 1/8] md-cluster/raid10: resize all the bitmaps before start reshape
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 0/8] md-cluster: add grow support for raid10
  • From: keld@xxxxxxxxxx
• Re: [PATCH 0/8] md-cluster: add grow support for raid10
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 0/8] md-cluster: add grow support for raid10
  • From: keld@xxxxxxxxxx
• [PATCH 7/8] md-cluster: send BITMAP_NEEDS_SYNC message if reshaping is interrupted
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 8/8] md-cluster: remove suspend_info
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 6/8] md-cluster/bitmap: don't call md_bitmap_sync_with_cluster during reshaping stage
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 5/8] md-cluster/raid10: don't call remove_and_add_spares during reshaping stage
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 4/8] md-cluster/raid10: call update_size in md_reap_sync_thread
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 3/8] md-cluster: introduce resync_info_get interface for sanity check
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 2/8] md-cluster/raid10: support add disk under grow mode
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 0/8] md-cluster: add grow support for raid10
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 1/8] md-cluster/raid10: resize all the bitmaps before start reshape
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH][md-next] md: remove redundant code that is no longer reachable
  • From: Colin King <colin.king@xxxxxxxxxxxxx>
• [PATCH] md/bitmap: use mddev_suspend/resume instead of ->quiesce()
  • From: Jack Wang <xjtuwjp@xxxxxxxxx>
• Re: [PATCH] md/bitmap: use mddev_suspend/resume instead of ->quiesce()
  • From: Jinpu Wang <jinpu.wang@xxxxxxxxxxxxxxxx>
• [PATCH 1/2] fcntl: fix typo in RWH_WRITE_LIFE_NOT_SET r/w hint
  • From: Eugene Syromiatnikov <esyr@xxxxxxxxxx>
• [PATCH 2/2] drivers/md/raid5.c: use the new spelling of RWH_WRITE_LIFE_NOT_SET
  • From: Eugene Syromiatnikov <esyr@xxxxxxxxxx>
• [PATCH 0/2] Fix typo in RWH_WRITE_LIFE_NOT_SET constant name
  • From: Eugene Syromiatnikov <esyr@xxxxxxxxxx>
• Re: How to disable RAID badblocks?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: How to disable RAID badblocks?
  • From: Andrew Engelbrecht <andrew@xxxxxxx>
• Re: How to disable RAID badblocks?
  • From: Andrew Engelbrecht <andrew@xxxxxxx>
• Re: How to disable RAID badblocks?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: How to toggle state of MD RAID member disk from active to clean?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• How to disable RAID badblocks?
  • From: Andrew Engelbrecht <andrew@xxxxxxx>
• Re: How to toggle state of MD RAID member disk from active to clean?
  • From: Sean Caron <scaron@xxxxxxxxx>
• How to toggle state of MD RAID member disk from active to clean?
  • From: Sean Caron <scaron@xxxxxxxxx>
• Re: RAID 5 kernel BUG
  • From: Steve Kowalik <steven@xxxxxxxxxxxxxxx>
• Re: RAID 5 kernel BUG
  • From: Paul Menzel <pmenzel@xxxxxxxxxxxxx>
• RAID 5 kernel BUG
  • From: Steve Kowalik <steven@xxxxxxxxxxxxxxx>
• Re: RFC - de-clustered raid 60 or 61 algorithm
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: RFC - de-clustered raid 60 or 61 algorithm
  • From: Feng Zhang <prod.feng@xxxxxxxxx>
• [PATCH] md: allow metadata updates while suspending an array - fix
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: RFC - de-clustered raid 60 or 61 algorithm
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid recovery
  • From: Madalin Grosu <madalin.grosu@xxxxxxxxx>
• Re: RFC - de-clustered raid 60 or 61 algorithm
  • From: Feng Zhang <prod.feng@xxxxxxxxx>
• Re: Thanks and possible bug found. Was:Raid10, six drives, two mirrors
  • From: Wilson Jonathan <i400sjon@xxxxxxxxx>
• Re: Announce: mdadm-4.1
  • From: Paul Menzel <pmenzel@xxxxxxxxxxxxx>
• Announce: mdadm-4.1
  • From: Jes Sorensen <jsorensen@xxxxxx>
• Re: [PATCH 0/2] Two patches for RAID-5/6 journal information
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] md/raid1: fix wrong behavior of re-adding a device
  • From: Gi-Oh Kim <gi-oh.kim@xxxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid1: fix wrong behavior of re-adding a device
  • From: Gi-Oh Kim <gi-oh.kim@xxxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] Two patches for RAID-5/6 journal information
  • From: Phillip Potter <phil@xxxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] Two patches for RAID-5/6 journal information
  • From: Phillip Potter <phil@xxxxxxxxxxxxxxxx>
• Re: [PATCH 0/2] Two patches for RAID-5/6 journal information
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [PATCH 2/2] mdadm: Expose journal count via mdadm --detail
  • From: Phillip Potter <phil@xxxxxxxxxxxxxxxx>
• [PATCH 1/2] md: journal: Add journal_disks member to mdu_array_info_t
  • From: Phillip Potter <phil@xxxxxxxxxxxxxxxx>
• [PATCH 0/2] Two patches for RAID-5/6 journal information
  • From: Phillip Potter <phil@xxxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid1: fix wrong behavior of re-adding a device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH] md/raid1: fix wrong behavior of re-adding a device
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md/bitmap: use mddev_suspend/resume instead of ->quiesce()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH] Fixed code style issues in the drivers/md/md.c
  • From: Andrey Abramov <st5pub@xxxxxxxxx>
• Re: [PATCH] imsm: block using partition
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [PATCH] imsm: block using partition
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• Re: Time line for mdadm-4.1
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 0/2] Two patches for Assemble
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] imsm: Avoid duplicate entries in --detail-platform
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] imsm: Block volume creation with empty name
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] mdadm.c: Fix error handling for --zero-superblock
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [PATCH] md/bitmap: use mddev_suspend/resume instead of ->quiesce()
  • From: Jack Wang <xjtuwjp@xxxxxxxxx>
• Time line for mdadm-4.1
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Raid recovery
  • From: François Goudal <francois@xxxxxxxxxx>
• Re: [RFC] wrong behavior of re-adding a device
  • From: Gi-Oh Kim <gi-oh.kim@xxxxxxxxxxxxxxxx>
• [PATCH] md/raid1: fix wrong behavior of re-adding a device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [RFC] wrong behavior of re-adding a device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [RFC] wrong behavior of re-adding a device
  • From: Gi-Oh Kim <gi-oh.kim@xxxxxxxxxxxxxxxx>
• Re: [RFC] wrong behavior of re-adding a device
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Filesystem-based raid vs. device-based raid
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Filesystem-based raid vs. device-based raid
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: [RFC] wrong behavior of re-adding a device
  • From: Gi-Oh Kim <gi-oh.kim@xxxxxxxxxxxxxxxx>
• Re: [RFC] wrong behavior of re-adding a device
  • From: Gi-Oh Kim <gi-oh.kim@xxxxxxxxxxxxxxxx>
• Re: Filesystem-based raid vs. device-based raid
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• [PATCH v2] md/raid10: Fix raid10 replace hang when new added disk faulty
  • From: alexwu <alexwu@xxxxxxxxxxxx>
• Re: Filesystem-based raid vs. device-based raid
  • From: Mateusz <mateusz-lists@xxxxxxxxxxxxxx>
• Re: Filesystem-based raid vs. device-based raid
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: [RFC] wrong behavior of re-adding a device
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [RFC] wrong behavior of re-adding a device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: Filesystem-based raid vs. device-based raid
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: Raid recovery
  • From: Madalin Grosu <madalin.grosu@xxxxxxxxx>
• Re: Raid recovery
  • From: François Goudal <francois@xxxxxxxxxx>
• Re: Raid recovery
  • From: Madalin Grosu <madalin.grosu@xxxxxxxxx>
• Filesystem-based raid vs. device-based raid
  • From: David F <raid@xxxxxxxxxxxxxxxx>
• Re: Raid recovery
  • From: François Goudal <francois@xxxxxxxxxx>
• Re: Raid recovery
  • From: Madalin Grosu <madalin.grosu@xxxxxxxxx>
• md: dead code in md_alloc()
  • From: Andrey Ryabinin <aryabinin@xxxxxxxxxxxxx>
• Re: [RFC] wrong behavior of re-adding a device
  • From: Gi-Oh Kim <gi-oh.kim@xxxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid10: Fix raid10 replace hang when new added disk faulty
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH] md/raid10: Fix raid10 replace hang when new added disk faulty
  • From: alexwu <alexwu@xxxxxxxxxxxx>
• [RFC] wrong behavior of re-adding a device
  • From: Gi-Oh Kim <gi-oh.kim@xxxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid10: Fix raid10 replace hang when new added disk faulty
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH] md/raid10: Fix raid10 replace hang when new added disk faulty
  • From: alexwu <alexwu@xxxxxxxxxxxx>
• Re: [PATCH] md/raid10: Fix raid10 replace hang when new added disk faulty
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH] md/raid10: Fix raid10 replace hang when new added disk faulty
  • From: alexwu <alexwu@xxxxxxxxxxxx>
• Re: [PATCH] md: bitmap: use mddev_suspend/resume instead of ->quiesce()
  • From: Gi-Oh Kim <gi-oh.kim@xxxxxxxxxxxxxxxx>
• Re: raid5: BUG_ON(atomic_inc_return(&sh->count) != 1)
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH] md/raid10: Fix raid10 replace hang when new added disk faulty
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• recovery raid array
  • From: Madalin Grosu <madalin.grosu@xxxxxxxxx>
• Re: raid array recovery
  • From: Madalin Grosu <madalin.grosu@xxxxxxxxx>
• raid array recovery
  • From: Madalin Grosu <madalin.grosu@xxxxxxxxx>
• raid5: BUG_ON(atomic_inc_return(&sh->count) != 1)
  • From: yuyufen <yuyufen@xxxxxxxxxx>
• Re: autodetection
  • From: Chris Murphy <chris@xxxxxxxxxxxxxxxxx>
• Re: autodetection
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: autodetection
  • From: Chris Murphy <chris@xxxxxxxxxxxxxxxxx>
• Re: autodetection
  • From: Chris Murphy <chris@xxxxxxxxxxxxxxxxx>
• imsm autodetection, kernel 4.18.5 vs 4.16.3
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• autodetection
  • From: Chris Murphy <chris@xxxxxxxxxxxxxxxxx>
• [PATCH] md: bitmap: use mddev_suspend/resume instead of ->quiesce()
  • From: Jack Wang <xjtuwjp@xxxxxxxxx>
• Re: Raid recovery
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Failed RAID5 array - recovery help
  • From: Francois Goudal <francois@xxxxxxxxxx>
• Re: Failed RAID5 array - recovery help
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Failed RAID5 array - recovery help
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Failed RAID5 array - recovery help
  • From: Francois Goudal <francois@xxxxxxxxxx>
• Re: Raid10, six drives, two mirrors
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: linux-next: Tree for Sep 11 (drivers/md/dm-thin-metadata.o:)
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
• Re: Raid10, six drives, two mirrors
  • From: David Brown <david.brown@xxxxxxxxxxxx>
• Re: Raid10, six drives, two mirrors
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: Raid10, six drives, two mirrors
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Raid10, six drives, two mirrors
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Raid10, six drives, two mirrors
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: Raid10, six drives, two mirrors
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH] md/raid10: Fix raid10 replace hang when new added disk faulty
  • From: alexwu <alexwu@xxxxxxxxxxxx>
• Re: Raid10, six drives, two mirrors
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Raid10, six drives, two mirrors
  • From: Wilson Jonathan <i400sjon@xxxxxxxxx>
• [GIT PULL] MD update for 4.19-rc2
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md/raid10: Fix raid10 replace hang when new added disk faulty
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 2/6] md: convert to kvmalloc
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [RFC] raid5: block failing device if raid will be failed
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 2/6] md: convert to kvmalloc
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• [PATCH 2/6] md: convert to kvmalloc
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH] md/raid10: Fix raid10 replace hang when new added disk faulty
  • From: alexwu <alexwu@xxxxxxxxxxxx>
• Re: Failed RAID5 array - recovery help
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Failed RAID5 array - recovery help
  • From: Francois Goudal <francois@xxxxxxxxxx>
• [RFC] raid5: block failing device if raid will be failed
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• [PATCH] md/raid5: move handle_stripe() comment to correct location
  • From: John Pittman <jpittman@xxxxxxxxxx>
• Re: [RFC] [PATCH 0/1] Introduce emergency raid0 stop for mounted arrays
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH] mdadm.c: Fix error handling for --zero-superblock
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• Re: raid1 becoming raid0 when device is removed before reboot
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: PCIe SATA controllers
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: Panic at BUG_ON(force && !conf->barrier);
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: raid1 becoming raid0 when device is removed before reboot
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH] md-cluster: release RESYNC lock after the last resync message
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: Panic at BUG_ON(force && !conf->barrier);
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH 1/1] RAID10 BUG_ON in raise_barrier when force is true and conf->barrier is 0
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Panic at BUG_ON(force && !conf->barrier);
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Panic at BUG_ON(force && !conf->barrier);
  • From: Xiao Ni <xni@xxxxxxxxxx>
• raid1 becoming raid0 when device is removed before reboot
  • From: Niklas Hambüchen <mail@xxxxxx>
• Re: raid5 reshape is stuck when raid5 journal device miss
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Panic at BUG_ON(force && !conf->barrier);
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: raid5 reshape is stuck when raid5 journal device miss
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Fwd: Setting up readonly fallback mode on device removal
  • From: Günter Manz <gunterznam@xxxxxxxxx>
• Deadlock in md
  • From: Daniel Santos <daniel.santos@xxxxxxxxx>
• Re: raid5-cache: deeply broken (with write-back?)
  • From: Daniel Santos <daniel.santos@xxxxxxxxx>
• Re: raid5-cache: deeply broken (with write-back?)
  • From: Joe Landman <joe.landman@xxxxxxxxx>
• Re: raid5-cache: deeply broken (with write-back?)
  • From: Daniel Santos <daniel.santos@xxxxxxxxx>
• Re: raid5-cache: deeply broken (with write-back?)
  • From: Daniel Santos <daniel.santos@xxxxxxxxx>
• Re: raid5-cache: deeply broken (with write-back?)
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: raid5-cache: deeply broken (with write-back?)
  • From: Lars Schimmer <l.schimmer@xxxxxxxxxxxxx>
• raid5-cache: deeply broken (with write-back?)
  • From: Daniel Santos <daniel.santos@xxxxxxxxx>
• [PATCH 2/2] Assemble: set devices to NULL when load_devices can't load device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 1/2] Assemble: free resources in load_devices
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 0/2] Two patches for Assemble
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Danil Kipnis <danil.kipnis@xxxxxxxxxxxxxxxx>
• raid5 reshape is stuck when raid5 journal device miss
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Jinpu Wang <jinpuwang@xxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Jinpu Wang <jinpuwang@xxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Jinpu Wang <jinpuwang@xxxxxxxxx>
• Re: [PATCH V3 3/3] Assemble: cleanup the failure path
  • From: "Tkaczyk, Mariusz" <mariusz.tkaczyk@xxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH V3 3/3] Assemble: cleanup the failure path
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH V3 3/3] Assemble: cleanup the failure path
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Danil Kipnis <danil.kipnis@xxxxxxxxxxxxxxxx>
• Re: [PATCH V3 3/3] Assemble: cleanup the failure path
  • From: "Tkaczyk, Mariusz" <mariusz.tkaczyk@xxxxxxxxx>
• Panic at BUG_ON(force && !conf->barrier);
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Danil Kipnis <danil.kipnis@xxxxxxxxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Jinpu Wang <jinpuwang@xxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: MegaRAID DDF
  • From: dpr <dpr@xxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Danil Kipnis <danil.kipnis@xxxxxxxxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Jinpu Wang <jinpuwang@xxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: NeilBrown <neilb@xxxxxxxx>
• [GIT PULL] MD update for 4.19-rc1
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Danil Kipnis <danil.kipnis@xxxxxxxxxxxxxxxx>
• [PATCH] imsm: Avoid duplicate entries in --detail-platform
  • From: Roman Sobanski <roman.sobanski@xxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Danil Kipnis <danil.kipnis@xxxxxxxxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Danil Kipnis <danil.kipnis@xxxxxxxxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Sarah Newman <srn@xxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Swapnil Ingle <swapnil.ingle@xxxxxxxxxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• Re: PCIe SATA controllers
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH] imsm: Block volume creation with empty name
  • From: Roman Sobanski <roman.sobanski@xxxxxxxxx>
• Re: RAID1 sometimes have different data on the slave devices
  • From: Jack Wang <jack.wang.usish@xxxxxxxxx>
• Re: PCIe SATA controllers
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: PCIe SATA controllers
  • From: Weedy <weedy2887@xxxxxxxxx>
• Re: PCIe SATA controllers
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: [RFC] [PATCH 0/1] Introduce emergency raid0 stop for mounted arrays
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: PCIe SATA controllers
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: PCIe SATA controllers
  • From: Alex <mysqlstudent@xxxxxxxxx>
• Re: PCIe SATA controllers
  • From: Ram Ramesh <rramesh2400@xxxxxxxxx>
• Re: PCIe SATA controllers
  • From: Matt Garman <matthew.garman@xxxxxxxxx>
• PCIe SATA controllers
  • From: Alex <mysqlstudent@xxxxxxxxx>
• RAID1 sometimes have different data on the slave devices
  • From: Swapnil Ingle <swapnil.ingle@xxxxxxxxxxxxxxxx>
• Re: Unable to re-assemble failed RAID6 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Unable to re-assemble failed RAID6 array
  • From: Nick Gruszauskas <ngrusz1@xxxxxxxxx>
• Read error and messy up array forcing assemble
  • From: Giulio Carabetta <giulio.carabetta@xxxxxxxxx>
• Re: Unable to re-assemble failed RAID6 array
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Unable to re-assemble failed RAID6 array
  • From: Nick Gruszauskas <ngrusz1@xxxxxxxxx>
• Re: Broken raid6 continually resyncing
  • From: Zach Adams <androlgenhald@xxxxxxxxx>
• Broken raid6 continually resyncing
  • From: Zach Adams <androlgenhald@xxxxxxxxx>
• Re: Boot Message Question
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Boot Message Question
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Boot Message Question
  • From: Robert Steinmetz AIA <rob@xxxxxxxxxxxxxxxx>
• Re: chunks/sectors/blocks/stripes ??
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: chunks/sectors/blocks/stripes ??
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: chunks/sectors/blocks/stripes ??
  • From: donotcare@xxxxxxxxxxx
• Re: LSI Patrol Read equivalent
  • From: Phil Turmel <philip@xxxxxxxxxx>
• LSI Patrol Read equivalent
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• Re: chunks/sectors/blocks/stripes ??
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: chunks/sectors/blocks/stripes ??
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• chunks/sectors/blocks/stripes ??
  • From: donotcare@xxxxxxxxxxx
• mdadm 4.1-rc2 released!
  • From: Jes Sorensen <jsorensen@xxxxxx>
• Re: [PATCH] Incremental: remove external arrays and devices correctly
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Why raid456 doesn't block removing member drives?
  • From: "Tkaczyk, Mariusz" <mariusz.tkaczyk@xxxxxxxxx>
• Re: Help / advice RAID5 Inactive
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• [PATCH] Incremental: remove external arrays and devices correctly
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• Re: Help / advice RAID5 Inactive
  • From: jonathan.p.milton@xxxxxxxxx
• Re: Help / advice RAID5 Inactive
  • From: Jonathan Milton <jonathan.p.milton@xxxxxxxxx>
• Re: Help / advice RAID5 Inactive
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [RFC] [PATCH 0/1] Introduce emergency raid0 stop for mounted arrays
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: Help / advice RAID5 Inactive
  • From: jonathan.p.milton@xxxxxxxxx
• Re: Help / advice RAID5 Inactive
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [RFC] [PATCH 0/1] Introduce emergency raid0 stop for mounted arrays
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH v4 0/5] bitmap: Introduce alloc/free helpers
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Help / advice RAID5 Inactive
  • From: Jonathan Milton <jonathan.p.milton@xxxxxxxxx>
• Re: [RFC] [PATCH 0/1] Introduce emergency raid0 stop for mounted arrays
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v4 0/5] bitmap: Introduce alloc/free helpers
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: [PATCH] Grow: Frozen array can't be idle
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [RFC] [PATCH 1/1] md/raid0: Introduce emergency stop for raid0 arrays
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [RFC] [PATCH 0/1] Introduce emergency raid0 stop for mounted arrays
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH] Grow: Frozen array can't be idle
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• Re: destroyed raid 5 by removing wrong disk
  • From: Martin Probst <martin.probst@xxxxxxxxxxx>
• [PATCH] md/raid5: fix data corruption of replacements after originals dropped
  • From: bingjingc <bingjingc@xxxxxxxxxxxx>
• Re: destroyed raid 5 by removing wrong disk
  • From: Martin Probst <martin.probst@xxxxxxxxxxx>
• Re: destroyed raid 5 by removing wrong disk
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• destroyed raid 5 by removing wrong disk
  • From: Martin Probst <martin.probst@xxxxxxxxxxx>
• Re: [PATCH] udev.rules: make safe timeouts compatible with split-usr systems.
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] udev.rules: make safe timeouts compatible with split-usr systems.
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] udev.rules: make safe timeouts compatible with split-usr systems.
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH v4 0/5] bitmap: Introduce alloc/free helpers
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH] udev.rules: make safe timeouts compatible with split-usr systems.
  • From: Dimitri John Ledkov <xnox@xxxxxxxxxx>
• Re: [PATCH] Assemble: remove the protection when clustered raid do assemble
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 2/6] drivers/md/raid5: Do not disable irq on release_inactive_stripe_list() call
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH] Assemble: remove the protection when clustered raid do assemble
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH] mapfile: set *mapp to NULL after map_free
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH] mapfile: set *mapp to NULL after map_free
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 1/6] drivers/md/raid5: Use irqsave variant of atomic_dec_and_lock()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Re: [PATCH 1/6] drivers/md/raid5: Use irqsave variant of atomic_dec_and_lock()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH] mapfile: set *mapp to NULL after map_free
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH V2] Free map to avoid resource leak issues
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 1/6] drivers/md/raid5: Use irqsave variant of atomic_dec_and_lock()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Re: [PATCH V2] Free map to avoid resource leak issues
  • From: "Tkaczyk, Mariusz" <mariusz.tkaczyk@xxxxxxxxx>
• Re: Failed to grow RAID - "failed to restore critical section for reshape" after reboot
  • From: Christian <christian+lr@xxxxxxxxx>
• Re: [PATCH 2/2] Coverity: 289702: Fix resource leak - free avail
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 1/2] Coverity: 289704: Fix resource leak (bitmap_fd not closed)
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: Adding a USB device to a SATA-only array
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Failed to grow RAID - "failed to restore critical section for reshape" after reboot
  • From: Christian <christian+lr@xxxxxxxxx>
• Re: Adding a USB device to a SATA-only array
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: Adding a USB device to a SATA-only array
  • From: Kevin Lyda <kevin@xxxxxxxxxxxxxx>
• Re: [PATCH V2] Free map to avoid resource leak issues
  • From: "Tkaczyk, Mariusz" <mariusz.tkaczyk@xxxxxxxxx>
• Re: [PATCH V2] Free map to avoid resource leak issues
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 1/6] drivers/md/raid5: Use irqsave variant of atomic_dec_and_lock()
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Adding a USB device to a SATA-only array
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/6] drivers/md/raid5: Use irqsave variant of atomic_dec_and_lock()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Re: Adding a USB device to a SATA-only array
  • From: Kevin Lyda <kevin@xxxxxxxxxxxxxx>
• Re: Adding a USB device to a SATA-only array
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Adding a USB device to a SATA-only array
  • From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Adding a USB device to a SATA-only array
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Adding a USB device to a SATA-only array
  • From: Kevin Lyda <kevin@xxxxxxxxxxxxxx>
• [PATCH 2/2] Coverity: 289702: Fix resource leak - free avail
  • From: Wol <anthony@xxxxxxxxxxxxxxx>
• [PATCH 1/2] Coverity: 289704: Fix resource leak (bitmap_fd not closed)
  • From: Wol <anthony@xxxxxxxxxxxxxxx>
• RE: [PATCH V2] Free map to avoid resource leak issues
  • From: "Tkaczyk, Mariusz" <mariusz.tkaczyk@xxxxxxxxx>
• Re: [PATCH V2] Free map to avoid resource leak issues
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• RE: [PATCH V2] Free map to avoid resource leak issues
  • From: "Tkaczyk, Mariusz" <mariusz.tkaczyk@xxxxxxxxx>
• Re: [PATCH] Coverity: Resource leak: close fd before return
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: MegaRAID DDF
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 1/6] tests, imsm: Set correct expected offset between volumes
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] Coverity: Resource leak: close fd before return
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] Coverity: Resource leak: close fds and free array before return
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] Coverity: Resource leak: fix return without free
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Michael Niewöhner <linux@xxxxxxxxxxxxxx>
• Re: Σχετ: Reduce resync time by keeping track of referenced blocks
  • From: Michael Niewöhner <linux@xxxxxxxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Michael Niewöhner <linux@xxxxxxxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Michael Niewöhner <linux@xxxxxxxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Michael Niewöhner <linux@xxxxxxxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Michael Niewöhner <linux@xxxxxxxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Michael Niewöhner <linux@xxxxxxxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Michael Niewöhner <linux@xxxxxxxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Michael Niewöhner <linux@xxxxxxxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Weedy <weedy2887@xxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Reduce resync time by keeping track of referenced blocks
  • From: Weedy <weedy2887@xxxxxxxxx>
• Reduce resync time by keeping track of referenced blocks
  • From: Michael Niewöhner <linux@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/5] bitmap: Introduce alloc/free helpers
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• Re: MegaRAID DDF
  • From: dpr <dpr@xxxxxxx>
• [PATCH 2/6] drivers/md/raid5: Do not disable irq on release_inactive_stripe_list() call
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH 1/6] drivers/md/raid5: Use irqsave variant of atomic_dec_and_lock()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH 0/6] use irqsafe variant of refcount_dec_and_lock() / atomic_dec_and_lock()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH] md/r5cache: remove redundant pointer bio
  • From: Colin King <colin.king@xxxxxxxxxxxxx>
• MegaRAID DDF
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• Re: [PATCH v4 1/5] dm: Avoid namespace collision with bitmap API
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v4 2/5] md: Avoid namespace collision with bitmap API
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [GIT PULL] MD update for 4.18-rc3
  • From: Shaohua Li <shli@xxxxxxxxxx>
• [PATCH 3/3] md-cluster: don't send msg if array is closing
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 2/3] md-cluster: show array's status more accurate
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 1/3] md-cluster: clear another node's suspend_area after the copy is finished
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH v4 5/5] Input: evdev - Switch to bitmap API
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v4 2/5] md: Avoid namespace collision with bitmap API
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v4 4/5] Input: gpio-keys - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v4 1/5] dm: Avoid namespace collision with bitmap API
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v4 0/5] bitmap: Introduce alloc/free helpers
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v4 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: Healthy RAID10 always mounts under Ubuntu 16.04, but not under Ubuntu 18.04.
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Healthy RAID10 always mounts under Ubuntu 16.04, but not under Ubuntu 18.04.
  • From: Hans Deragon <hans@xxxxxxxxxxx>
• Re: A Nasty md/raid bug in 2018?
  • From: Dmytro Shcherbakov <dmytro.shcherbakov@xxxxxxxxx>
• [PATCH] md/raid10: fix that replacement cannot complete recovery after reassemble
  • From: bingjingc <bingjingc@xxxxxxxxxxxx>
• Re: [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• [PATCH 6/6] tests, imsm: Calculate expected array_size in proper way
  • From: Michal Zylowski <michal.zylowski@xxxxxxxxx>
• [PATCH 5/6] tests, imsm: Migration from RAID5 to RAID0 is not supported for IMSM metadata
  • From: Michal Zylowski <michal.zylowski@xxxxxxxxx>
• [PATCH 4/6] tests, imsm: Test shouldn't call grow with chunk and level in one command
  • From: Michal Zylowski <michal.zylowski@xxxxxxxxx>
• [PATCH 3/6] tests, imsm: Set new_num_disks value corectly to perform expected size calculations
  • From: Michal Zylowski <michal.zylowski@xxxxxxxxx>
• [PATCH 2/6] tests, imsm: Fix unit inconsistency in tests error messages
  • From: Michal Zylowski <michal.zylowski@xxxxxxxxx>
• [PATCH 1/6] tests, imsm: Set correct expected offset between volumes
  • From: Michal Zylowski <michal.zylowski@xxxxxxxxx>
• Re: RAID5 degraded, removed the wrong hard disk frm the tray
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: RAID5 degraded, removed the wrong hard disk frm the tray
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: RAID5 degraded, removed the wrong hard disk frm the tray
  • From: Piero <info@xxxxxxxxxxxxx>
• Re: [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: RAID5 degraded, removed the wrong hard disk frm the tray
  • From: Piero <info@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/5] bitmap: Introduce alloc/free helpers
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/5] bitmap: Introduce alloc/free helpers
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• Re: [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• Re: [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx>
• Re: [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH v3] async_pq: Remove VLA usage
  • From: Vinod <vkoul@xxxxxxxxxx>
• Re: [PATCH v3 1/5] md: Avoid namespace collision with bitmap API
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v3 1/5] md: Avoid namespace collision with bitmap API
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH v2 1/5] md: Avoid namespace collision with bitmap API
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH v3 0/5] bitmap: Introduce alloc/free helpers
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v3 4/5] Input: gpio-keys - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v3 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v3 1/5] md: Avoid namespace collision with bitmap API
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v3 2/5] bitmap: Drop unnecessary 0 check for u32 array operations
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v3 5/5] Input: evdev - Switch to bitmap API
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: RAID5 degraded, removed the wrong hard disk frm the tray
  • From: Piero <info@xxxxxxxxxxxxx>
• Re: RAID5 degraded, removed the wrong hard disk frm the tray
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• RAID5 degraded, removed the wrong hard disk frm the tray
  • From: Piero <info@xxxxxxxxxxxxx>
• [PATCH] Coverity: Resource leak: close fds and free array before return
  • From: Anthony Youngman <anthony@xxxxxxxxxxxxxxx>
• Coverity resource leak
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Coverity potential buffer overflow
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 4/5] Input: gpio-keys - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• [PATCH] Coverity: Resource leak: free array before return
  • From: Anthony Youngman <anthony@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• Re: [PATCH v2 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andy Shevchenko <andy.shevchenko@xxxxxxxxx>
• Re: [PATCH v2 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 4/5] Input: gpio-keys - Switch to bitmap_zalloc()
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Yury Norov <ynorov@xxxxxxxxxxxxxxxxxx>
• [PATCH] Coverity: Resource leak: close fd before return
  • From: Anthony Youngman <anthony@xxxxxxxxxxxxxxx>
• [PATCH] Coverity: Resource leak: fix return without free
  • From: Anthony Youngman <anthony@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 1/5] md: Avoid namespace collision with bitmap API
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: [PATCH v2 1/5] md: Avoid namespace collision with bitmap API
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v2 1/5] md: Avoid namespace collision with bitmap API
  • From: kbuild test robot <lkp@xxxxxxxxx>
• [PATCH v2 4/5] Input: gpio-keys - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v2 1/5] md: Avoid namespace collision with bitmap API
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v2 2/5] bitmap: Drop unnecessary 0 check for u32 array operations
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v2 0/5] bitmap: Introduce alloc/free helpers
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v2 5/5] Input: evdev - Switch to bitmap_zalloc()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• [PATCH v2 3/5] bitmap: Add bitmap_alloc(), bitmap_zalloc() and bitmap_free()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Journaled RAID rebuilding fully after power failure
  • From: Ben Estrabaud <ben.estrabaud@xxxxxxxxxx>
• bitmap namespace conflict
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: RAID6: "Bad block number requested"
  • From: Sebastian Hegler <sebastian.hegler@xxxxxxxxxxxxx>
• Re: RAID6: "Bad block number requested"
  • From: Bryan Gurney <bgurney@xxxxxxxxxx>
• mdadm raid soft lock-ups kernel 4.13.0-36
  • From: Premysl Kouril <premysl.kouril@xxxxxxxxx>
• Re: My first Coverity mdadm fix
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: RAID6: "Bad block number requested"
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: RAID6: "Bad block number requested"
  • From: Bryan Gurney <bgurney@xxxxxxxxxx>
• Re: RAID6: "Bad block number requested"
  • From: Anthony Youngman <anthony@xxxxxxxxxxxxxxx>
• My first Coverity mdadm fix
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: RAID6: "Bad block number requested"
  • From: Douglas Gilbert <dgilbert@xxxxxxxxxxxx>
• Re: RAID6: "Bad block number requested"
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• Re: RAID6: "Bad block number requested"
  • From: James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>
• RAID6: "Bad block number requested"
  • From: Sebastian Hegler <sebastian.hegler@xxxxxxxxxxxxx>
• Re: Preparing for mdadm-4.1 and gcc-8.1
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [mdadm PATCH 3/3] Replace snprintf with strncpy to avoid building error
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [mdadm PATCH 2/3] Fix one building error related with memcpy
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [mdadm PATCH 1/3] Fix building error because of -Werror=format-overflow
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH V2] Free map to avoid resource leak issues
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [PATCH V2] Free map to avoid resource leak issues
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH] Free map to avoid resource leak issues
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [GIT PULL] MD update for 4.18-rc
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] imsm: correct num_data_stripes in metadata map for migration
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] Free map to avoid resource leak issues
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH RESEND] Assemble.c Don't ignore faulty disk when array is auto assembled.
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH blktests 1/9] blktests: add hepler functions for new md tests
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• [PATCH] imsm: correct num_data_stripes in metadata map for migration
  • From: Roman Sobanski <roman.sobanski@xxxxxxxxx>
• [PATCH] Free map to avoid resource leak issues
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH] md: Unify mddev destruction paths
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH] md: Unify mddev destruction paths
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH blktests 1/9] blktests: add hepler functions for new md tests
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH RESEND] Assemble.c Don't ignore faulty disk when array is auto assembled.
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• Re: [PATCH blktests 1/9] blktests: add hepler functions for new md tests
  • From: Johannes Thumshirn <jthumshirn@xxxxxxx>
• Re: [PATCH blktests 1/9] blktests: add hepler functions for new md tests
  • From: bingjingc <bingjingc@xxxxxxxxxxxx>
• problem statement regarding --re-add
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [PATCH blktests 1/9] blktests: add hepler functions for new md tests
  • From: Johannes Thumshirn <jthumshirn@xxxxxxx>
• Re: [PATCH blktests 1/9] blktests: add hepler functions for new md tests
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH blktests 1/9] blktests: add hepler functions for new md tests
  • From: Johannes Thumshirn <jthumshirn@xxxxxxx>
• [mdadm PATCH 3/3] Replace snprintf with strncpy to avoid building error
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [mdadm PATCH 2/3] Fix one building error related with memcpy
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [mdadm PATCH 1/3] Fix building error because of -Werror=format-overflow
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [mdadm PATCH 0/3] Fix some building errors
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Healthy RAID10 always mounts under Ubuntu 16.04, but not under Ubuntu 18.04.
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Healthy RAID10 always mounts under Ubuntu 16.04, but not under Ubuntu 18.04.
  • From: Hans Deragon <hans@xxxxxxxxxxx>
• Re: [PATCH v3] async_pq: Remove VLA usage
  • From: Vinod <vkoul@xxxxxxxxxx>
• Re: mdadm coverity scan
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Mdadm raid and UEFI boot
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• mdadm coverity scan
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: Mdadm raid and UEFI boot
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Mdadm raid and UEFI boot
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Mdadm raid and UEFI boot
  • From: G <garboge@xxxxxxx>
• Re: Mdadm raid and EUFI booting
  • From: G <garboge@xxxxxxx>
• [PATCH 1/5 v2] spinlock: atomic_dec_and_lock: Add an irqsave variant
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Mdadm raid and EUFI booting
  • From: G <garboge@xxxxxxx>
• Mdadm raid and EUFI booting
  • From: G <garboge@xxxxxxx>
• Re: [PATCH v3] async_pq: Remove VLA usage
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH v3] async_pq: Remove VLA usage
  • From: Kyle Spiers <ksspiers@xxxxxxxxxx>
• Preparing for mdadm-4.1 and gcc-8.1
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] mdadm/test: correct tests/testdev as testdev in 02r5grow
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] mdadm/test: mdadm needn't make install on the system
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [mdadm PATCH 1/1] Check major number of block device when querying md device
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: Ubuntu 16.04 mdadm bug or feature?
  • From: Bill Broadley <bill@xxxxxxxxxxxx>
• Re: Ubuntu 16.04 mdadm bug or feature?
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [PATCH 06/12] md: convert to bioset_init()/mempool_init()
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Ubuntu 16.04 mdadm bug or feature?
  • From: Bill Broadley <bill@xxxxxxxxxxxx>
• Re: [PATCH] imsm: Do not require MDADM_EXPERIMENTAL flag anymore
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] imsm: Do not block volume creation when container has disks with mixed sector size
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH v2] async_pq: Remove VLA usage
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2] async_pq: Remove VLA usage
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH 10/12] btrfs: convert to bioset_init()/mempool_init()
  • From: Chris Mason <clm@xxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH 07/12] dm: convert to bioset_init()/mempool_init()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: IMSM volume name truncation
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: dm-writecache: fix compilation issue with !DAX
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH] dm-writecache: fix compilation issue with !DAX
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: [PATCH] dm: writecache: add DAX dependency
  • From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
• Re: Introduce atomic_dec_and_lock_irqsave()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH] mdadm/test: correct tests/testdev as testdev in 02r5grow
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• [PATCH] mdadm/test: mdadm needn't make install on the system
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• [mdadm PATCH 1/1] Check major number of block device when querying md device
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH v2] async_pq: Remove VLA usage
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2] async_pq: Remove VLA usage
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: dm-writecache: fix compilation issue with !DAX
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• IMSM volume name truncation
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: dm-writecache: fix compilation issue with !DAX
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] Fix misspelling of 'alignment' and 'geometry'
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: dm-writecache: fix compilation issue with !DAX
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• [PATCH] dm-writecache: fix compilation issue with !DAX
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• Re: [PATCH] dm: writecache: add DAX dependency
  • From: Ross Zwisler <ross.zwisler@xxxxxxxxxxxxxxx>
• [PATCH] imsm: Do not require MDADM_EXPERIMENTAL flag anymore
  • From: Michal Zylowski <michal.zylowski@xxxxxxxxx>
• [PATCH] imsm: Do not block volume creation when container has disks with mixed sector size
  • From: Michal Zylowski <michal.zylowski@xxxxxxxxx>
• [PATCH] Fix misspelling of 'alignment' and 'geometry'
  • From: Michal Zylowski <michal.zylowski@xxxxxxxxx>
• Re: dm: writecache: add DAX dependency
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 1/6] Generic radix trees
  • From: Liu Bo <obuil.liubo@xxxxxxxxx>
• Re: [PATCH] dm: writecache: add DAX dependency
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• [PATCH] dm: writecache: add DAX dependency
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH 1/6] Generic radix trees
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH 1/6] Generic radix trees
  • From: Liu Bo <obuil.liubo@xxxxxxxxx>
• Re: A Nasty md/raid bug in 2018?
  • From: Dmytro Shcherbakov <dmytro.shcherbakov@xxxxxxxxx>
• Re: A Nasty md/raid bug in 2018?
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: A Nasty md/raid bug in 2018?
  • From: Dmytro Shcherbakov <dmytro.shcherbakov@xxxxxxxxx>
• Re: [PATCH 3/8] md: raid5: use refcount_t for reference counting instead atomic_t
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 4/6] openvswitch: convert to genradix
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH 2/6] proc: commit to genradix
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH 6/6] Drop flex_arrays
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH 3/8] md: raid5: use refcount_t for reference counting instead atomic_t
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 3/8] md: raid5: use refcount_t for reference counting instead atomic_t
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 6/6] Drop flex_arrays
  • From: Dave Hansen <dave.hansen@xxxxxxxxx>
• Re: [PATCH 6/6] Drop flex_arrays
  • From: Jonathan Corbet <corbet@xxxxxxx>
• Re: [PATCH 3/8] md: raid5: use refcount_t for reference counting instead atomic_t
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH v2 0/8] Introduce refcount_dec_and_lock_irqsave()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Re: Introduce atomic_dec_and_lock_irqsave()
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v2 0/8] Introduce refcount_dec_and_lock_irqsave()
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 3/8] md: raid5: use refcount_t for reference counting instead atomic_t
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 3/8] md: raid5: use refcount_t for reference counting instead atomic_t
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Re: [PATCH 3/8] md: raid5: use refcount_t for reference counting instead atomic_t
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 4/6] openvswitch: convert to genradix
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• Re: [PATCH 2/6] proc: commit to genradix
  • From: Matthew Wilcox <willy@xxxxxxxxxxxxx>
• [PATCH 2/6] proc: commit to genradix
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 4/6] openvswitch: convert to genradix
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 6/6] Drop flex_arrays
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 3/6] md: convert to genradix
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 5/6] selinux: convert to genradix
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 1/6] Generic radix trees
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: Defective RAID
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: [PATCH 01/12] block: convert bounce, q->bio_split to bioset_init()/mempool_init()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 08/12] target: convert to bioset_init()/mempool_init()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 09/12] fs: convert block_dev.c to bioset_init()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 11/12] xfs: convert to bioset_init()/mempool_init()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 12/12] block: Drop bioset_create()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH 04/12] lightnvm: convert to bioset_init()/mempool_init()
  • From: Javier Gonzalez <javier@xxxxxxxxxxxx>
• Re: Defective RAID
  • From: Johannes Truschnigg <johannes@xxxxxxxxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: Defective RAID
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Defective RAID
  • From: Axel Spallek IT-Dienstleistungen <axel@xxxxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH 11/12] xfs: convert to bioset_init()/mempool_init()
  • From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH V5 1/1] MD: fix lock contention for flush bios
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: David Sterba <dsterba@xxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Mike Snitzer <snitzer@xxxxxxxxxx>
• Re: [PATCH 05/12] bcache: convert to bioset_init()/mempool_init()
  • From: Coly Li <colyli@xxxxxxx>
• [PATCH V5 1/1] MD: fix lock contention for flush bios
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [PATCH 06/12] md: convert to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH 01/12] block: convert bounce, q->bio_split to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 00/13] convert block layer to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 04/12] lightnvm: convert to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 05/12] bcache: convert to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 03/12] pktcdvd: convert to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 06/12] md: convert to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 08/12] target: convert to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 07/12] dm: convert to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 02/12] drbd: convert to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 12/12] block: Drop bioset_create()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 11/12] xfs: convert to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 10/12] btrfs: convert to bioset_init()/mempool_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• [PATCH 09/12] fs: convert block_dev.c to bioset_init()
  • From: Kent Overstreet <kent.overstreet@xxxxxxxxx>
• Re: [PATCH] md: simplify flush request handling
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH] md: simplify flush request handling
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md/raid5: Assigning NULL to sh->batch_head before testing bit R5_Overlap of a stripe
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md: zero the original position of sb for 0.90 and 1.0
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md: simplify flush request handling
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md: simplify flush request handling
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [PATCH] md/raid5: Assigning NULL to sh->batch_head before testing bit R5_Overlap of a stripe
  • From: Amy Chiang <amychiang@xxxxxxxx>
• [PATCH] md: zero the original position of sb for 0.90 and 1.0
  • From: Jianchao Wang <jianchao.w.wang@xxxxxxxxxx>
• Re: [PATCH] md: simplify flush request handling
  • From: Ming Lei <tom.leiming@xxxxxxxxx>
• NVME RAID0 bottlenecked on single kworker thread?
  • From: Ryan <ryanrs@xxxxxxxxx>
• Re: [PATCH] md/raid1: add error handling of read error from FailFast device
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md: simplify flush request handling
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md: simplify flush request handling
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH] md/raid1: add error handling of read error from FailFast device
  • From: Jinpu Wang <jinpu.wang@xxxxxxxxxxxxxxxx>
• Re: A Nasty md/raid bug in 2018?
  • From: Dmytro Shcherbakov <dmytro.shcherbakov@xxxxxxxxx>
• Re: [PATCH] md: simplify flush request handling
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH] md: simplify flush request handling
  • From: Ming Lei <tom.leiming@xxxxxxxxx>
• [PATCH] md: simplify flush request handling
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Deadlock during memory reclaim path involving sysfs and MD-Raid layers
  • From: Bruno Faccini <bfaccini62@xxxxxxxxx>
• [PATCH 1/8] bdi: use refcount_t for reference counting instead atomic_t
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH 2/8] userns: use refcount_t for reference counting instead atomic_t
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH 5/8] bdi: Use irqsave variant of refcount_dec_and_lock()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH 3/8] md: raid5: use refcount_t for reference counting instead atomic_t
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH 6/8] userns: Use irqsave variant of refcount_dec_and_lock()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH 4/8] locking/refcount: implement refcount_dec_and_lock_irqsave()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH 7/8] md: raid5: Use irqsave variant of refcount_dec_and_lock()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH 8/8] md: raid5: Do not disable irq on release_inactive_stripe_list() call
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH v2 0/8] Introduce refcount_dec_and_lock_irqsave()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH] Assemble.c Don't ignore faulty disk when array is auto assembled.
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• Re: [PATCH v4] Since changing number of devices in RAID10 is possible fix man and add a test
  • From: Azat Khuzhin <a3at.mail@xxxxxxxxx>
• Re: Introduce atomic_dec_and_lock_irqsave()
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: Introduce atomic_dec_and_lock_irqsave()
  • From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
• Re: Introduce atomic_dec_and_lock_irqsave()
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: Introduce atomic_dec_and_lock_irqsave()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• Re: Introduce atomic_dec_and_lock_irqsave()
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Introduce atomic_dec_and_lock_irqsave()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH 3/5] kernel/user: Use irqsave variant of atomic_dec_and_lock()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH 2/5] mm/backing-dev: Use irqsave variant of atomic_dec_and_lock()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH 1/5] spinlock: atomic_dec_and_lock: Add an irqsave variant
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH 5/5] drivers/md/raid5: Do not disable irq on release_inactive_stripe_list() call
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH 4/5] drivers/md/raid5: Use irqsave variant of atomic_dec_and_lock()
  • From: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx>
• [PATCH] md: fix NULL dereference of mddev->pers in remove_and_add_spares()
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: [PATCH] md/raid1: add error handling of read error from FailFast device
  • From: Gi-Oh Kim <gi-oh.kim@xxxxxxxxxxxxxxxx>
• [RFC PATCH] raid6_pq: Add module options to prefer algorithm
  • From: Timofey Titovets <nefelim4ag@xxxxxxxxx>
• Re: question for documentation writers
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• question for documentation writers
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• [mdadm] Reshape stuck after interrupted by reboot
  • From: Fisher <fisherthepooh@xxxxxxxxxxxxxx>
• Re: Question re: re-establishment of a raid-10 array
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: [PATCH] md/raid1: add error handling of read error from FailFast device
  • From: Gi-Oh Kim <gi-oh.kim@xxxxxxxxxxxxxxxx>
• [PATCH] md/raid1: add error handling of read error from FailFast device
  • From: Gioh Kim <gi-oh.kim@xxxxxxxxxxxxxxxx>
• creating parities
  • From: Marek <mlf.conv@xxxxxxxxx>
• Re: Verify RAID1
  • From: Nick Leli <nicholasleli@xxxxxxxxx>
• Re: Further question(s)
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Further question(s)
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Further question(s)
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Question re: re-establishment of a raid-10 array
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Question re: re-establishment of a raid-10 array
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Verify RAID1
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Question re: re-establishment of a raid-10 array
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Further question(s)
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Question re: re-establishment of a raid-10 array
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• WARNING in md_ioctl
  • From: syzbot <syzbot+1e46a0864c1a6e9bd3d8@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Question re: re-establishment of a raid-10 array
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Question re: re-establishment of a raid-10 array
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH] md: fix two problems with setting the "re-add" device state.
  • From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
• Question re: re-establishment of a raid-10 array
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: Verify RAID1
  • From: Nick Leli <nicholasleli@xxxxxxxxx>
• Re: Verify RAID1
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH v4] Since changing number of devices in RAID10 is possible fix man and add a test
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• Re: Verify RAID1
  • From: Nikhil Kshirsagar <nkshirsa@xxxxxxxxxx>
• Verify RAID1
  • From: Nick Leli <nicholasleli@xxxxxxxxx>
• Re: Should a raid-0 array immediately stop if a component disk is removed?
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: Should a raid-0 array immediately stop if a component disk is removed?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Should a raid-0 array immediately stop if a component disk is removed?
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH] mdadm/grow: correct size and chunk_size casting
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH v4] Since changing number of devices in RAID10 is possible fix man and add a test
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: Fixing priority of RAID check?
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• [PATCH] mdadm/grow: correct size and chunk_size casting
  • From: Roman Sobanski <roman.sobanski@xxxxxxxxx>
• Re: Fixing priority of RAID check?
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Fixing priority of RAID check?
  • From: Linus Lüssing <linus.luessing@xxxxxxxxx>
• Re: [lkp-robot] [MD] 0ffbb1adf8: aim7.jobs-per-min -10.6% regression
  • From: Ye Xiaolong <xiaolong.ye@xxxxxxxxx>
• Re: [lkp-robot] [MD] 0ffbb1adf8: aim7.jobs-per-min -10.6% regression
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH v4] Since changing number of devices in RAID10 is possible fix man and add a test
  • From: Zhilong Liu <zlliu@xxxxxxxx>
• Re: [PATCH v4] Since changing number of devices in RAID10 is possible fix man and add a test
  • From: Azat Khuzhin <a3at.mail@xxxxxxxxx>
• [PATCH] md: fix two problems with setting the "re-add" device state.
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH] raid10: check bio in r10buf_pool_free to void NULL pointer dereference
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: Fwd: Kernel crash trying to add an already removed disk from RAID 10
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [lkp-robot] [MD] 0ffbb1adf8: aim7.jobs-per-min -10.6% regression
  • From: Ye Xiaolong <xiaolong.ye@xxxxxxxxx>
• Re: mdadm: unrecognized option '--replace'
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• Re: mdadm: unrecognized option '--replace'
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• Re: mdadm: unrecognized option '--replace'
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Fwd: Kernel crash trying to add an already removed disk from RAID 10
  • From: Alexis Castilla <pencerval@xxxxxxxxx>
• Re: [PATCH] Prevent create IMSM volume with size smaller than 1M or chunk
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [PATCH] Prevent create IMSM volume with size smaller than 1M or chunk
  • From: Roman Sobanski <roman.sobanski@xxxxxxxxx>
• Re: Fwd: Kernel crash trying to add an already removed disk from RAID 10
  • From: Alexis Castilla <pencerval@xxxxxxxxx>
• Re: Fwd: Kernel crash trying to add an already removed disk from RAID 10
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: Fwd: Kernel crash trying to add an already removed disk from RAID 10
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [lkp-robot] [MD] 0ffbb1adf8: aim7.jobs-per-min -10.6% regression
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Fwd: Kernel crash trying to add an already removed disk from RAID 10
  • From: Alexis Castilla <pencerval@xxxxxxxxx>
• [RFC PATCH] md: add io statistics
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• [PATCH] md: fix an error code format and remove unsed bio_sector
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• mdadm: unrecognized option '--replace'
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• [PATCH] md/raid10: exit sync request if MD_RECOVERY_INTR is set
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: Question
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• [PATCH v3] raid5: copy write hint from origin bio to stripe
  • From: Mariusz Dabrowski <mariusz.dabrowski@xxxxxxxxx>
• Re: [PATCH v2] raid5: copy write hint from origin bio to stripe
  • From: Mariusz Dabrowski <mariusz.dabrowski@xxxxxxxxx>
• [GIT PULL] MD update for 4.17-rc1
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: [PATCH v2] raid5: copy write hint from origin bio to stripe
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Kernel bug when creating MD arrays
  • From: Shaohua Li <shli@xxxxxxxxxx>
• Re: Question
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Question
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Kernel bug when creating MD arrays
  • From: Mariusz Dabrowski <mariusz.dabrowski@xxxxxxxxx>
• Re: Add udev-md-raid-safe-timeouts.rules
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: Add udev-md-raid-safe-timeouts.rules
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Re: Add udev-md-raid-safe-timeouts.rules
  • From: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
• Re: Add udev-md-raid-safe-timeouts.rules
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Add udev-md-raid-safe-timeouts.rules
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: Add udev-md-raid-safe-timeouts.rules
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: Add udev-md-raid-safe-timeouts.rules
  • From: "Austin S. Hemmelgarn" <ahferroin7@xxxxxxxxx>
• Add udev-md-raid-safe-timeouts.rules
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: 4tb NAS drive recommendation
  • From: "John Stoffel" <john@xxxxxxxxxxx>