Linux RAID Storage Date Index

• Thread Index

• [PATCH AUTOSEL 4.19 033/128] md: don't set In_sync if array is frozen
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 5.2 147/185] md/raid1: fail run raid1 array when active disk less than one
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 5.3 052/203] md: don't set In_sync if array is frozen
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.19 114/128] raid5: don't set STRIPE_HANDLE to stripe which is in batch list
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.14 25/89] md: don't call spare_active in md_reap_sync_thread if all member devices can't work
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.14 26/89] md: don't set In_sync if array is frozen
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.14 71/89] md/raid1: fail run raid1 array when active disk less than one
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.14 78/89] raid5: don't set STRIPE_HANDLE to stripe which is in batch list
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.14 81/89] raid5: don't increment read_errors on EILSEQ return
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.9 46/60] md/raid1: fail run raid1 array when active disk less than one
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.4 18/44] md: don't set In_sync if array is frozen
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.4 34/44] md/raid1: fail run raid1 array when active disk less than one
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.4 17/44] md: don't call spare_active in md_reap_sync_thread if all member devices can't work
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.9 21/60] md: don't set In_sync if array is frozen
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.9 20/60] md: don't call spare_active in md_reap_sync_thread if all member devices can't work
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.14 24/89] md/raid1: end bio when the device faulty
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.19 119/128] raid5: don't increment read_errors on EILSEQ return
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.19 104/128] md/raid1: fail run raid1 array when active disk less than one
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 5.2 162/185] raid5: don't set STRIPE_HANDLE to stripe which is in batch list
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 5.2 042/185] md/raid1: end bio when the device faulty
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 5.3 186/203] raid5: don't increment read_errors on EILSEQ return
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 5.3 051/203] md: don't call spare_active in md_reap_sync_thread if all member devices can't work
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• RE: RAID 10 with 2 failed drives
  • From: "Liviu Petcu" <Liviu.Petcu@xxxxxxx>
• Re: RAID 10 with 2 failed drives
  • From: Sarah Newman <srn@xxxxxxxxx>
• RE: RAID 10 with 2 failed drives
  • From: "Liviu Petcu" <Liviu.Petcu@xxxxxxx>
• RE: RAID 10 with 2 failed drives
  • From: "Liviu Petcu" <Liviu.Petcu@xxxxxxx>
• Re: RAID 10 with 2 failed drives
  • From: Sarah Newman <srn@xxxxxxxxx>
• Re: RAID 10 with 2 failed drives
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• RE: RAID 10 with 2 failed drives
  • From: "Liviu Petcu" <Liviu.Petcu@xxxxxxx>
• [PATCH] md/raid0: Fix an error message in raid0_make_request()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• Re: RAID 10 with 2 failed drives
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: RAID 10 with 2 failed drives
  • From: Sarah Newman <srn@xxxxxxxxx>
• RE: RAID 10 with 2 failed drives
  • From: "Liviu Petcu" <Liviu.Petcu@xxxxxxx>
• Re: RAID 10 with 2 failed drives
  • From: Sarah Newman <srn@xxxxxxxxx>
• Re: RAID 10 with 2 failed drives
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: RAID 10 with 2 failed drives
  • From: Sarah Newman <srn@xxxxxxxxx>
• Re: RAID 10 with 2 failed drives
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• [PATCH v3 3/3] drivers/md/raid5-ppl.c: use the new spelling of RWH_WRITE_LIFE_NOT_SET
  • From: Eugene Syromiatnikov <esyr@xxxxxxxxxx>
• [PATCH v3 2/3] drivers/md/raid5.c: use the new spelling of RWH_WRITE_LIFE_NOT_SET
  • From: Eugene Syromiatnikov <esyr@xxxxxxxxxx>
• [PATCH v3 1/3] fcntl: fix typo in RWH_WRITE_LIFE_NOT_SET r/w hint name
  • From: Eugene Syromiatnikov <esyr@xxxxxxxxxx>
• [PATCH v3 0/3] Fix typo in RWH_WRITE_LIFE_NOT_SET constant name
  • From: Eugene Syromiatnikov <esyr@xxxxxxxxxx>
• Re: RAID 10 with 2 failed drives
  • From: Sarah Newman <srn@xxxxxxxxx>
• RE: RAID 10 with 2 failed drives
  • From: "Liviu Petcu" <Liviu.Petcu@xxxxxxx>
• Re: [PATCH] udev: allow for udev attribute reading bug.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Linux RAID 1 Not Working
  • From: "David F." <df7729@xxxxxxxxx>
• Re: [PATCH] udev: allow for udev attribute reading bug.
  • From: "David F." <df7729@xxxxxxxxx>
• Re: RAID 10 with 2 failed drives
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• RAID 10 with 2 failed drives
  • From: "Liviu Petcu" <Liviu.Petcu@xxxxxxx>
• Re: [PATCH 1/1] Call md_handle_request directly in md_flush_request
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH 1/1] Call md_handle_request directly in md_flush_request
  • From: David Jeffery <djeffery@xxxxxxxxxx>
• [PATCH] udev: allow for udev attribute reading bug.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 1/1] Call md_handle_request directly in md_flush_request
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH 1/1] Call md_handle_request directly in md_flush_request
  • From: David Jeffery <djeffery@xxxxxxxxxx>
• [PATCH 1/1] Call md_handle_request directly in md_flush_request
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Linux RAID 1 Not Working
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: Linux RAID 1 Not Working
  • From: "David F." <df7729@xxxxxxxxx>
• Re: [PATCH v4 2/2] mdadm: Introduce new array state 'broken' for raid0/linear
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [GIT PULL] md-next 20190913
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [GIT PULL] md-next 20190913
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 0/2] two trivial cleanup for raid5
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: Linux RAID 1 Not Working
  • From: "Tkaczyk, Mariusz" <mariusz.tkaczyk@xxxxxxxxx>
• Linux RAID 1 Not Working
  • From: "David F." <df7729@xxxxxxxxx>
• [PATCH 2/2] raid5: use bio_end_sector in r5_next_bio
  • From: jgq516@xxxxxxxxx
• [PATCH 1/2] raid5: remove STRIPE_OPS_REQ_PENDING
  • From: jgq516@xxxxxxxxx
• [PATCH 0/2] two trivial cleanup for raid5
  • From: jgq516@xxxxxxxxx
• Re: [PATCH] md: no longer compare spare disk superblock events in super_load
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] md: no longer compare spare disk superblock events in super_load
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH v3 0/2] skip spare disk as freshest disk
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] md/raid0: avoid RAID0 data corruption due to layout confusion.
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] mdadm: force a uuid swap on big endian
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH v3 0/2] skip spare disk as freshest disk
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: [PATCH] raid5: don't set STRIPE_HANDLE to stripe which is in batch list
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] md/raid0: avoid RAID0 data corruption due to layout confusion.
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH v3 0/2] skip spare disk as freshest disk
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [PATCH] raid5: don't set STRIPE_HANDLE to stripe which is in batch list
  • From: jgq516@xxxxxxxxx
• [PATCH v3 0/2] skip spare disk as freshest disk
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• [PATCH v3 2/2] md: don't let spare disk become the fresh disk in analyze_sbs()
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• [PATCH v3 1/2] md: add a new entry .disk_is_spare in super_types
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: [PATCH] md/raid0: avoid RAID0 data corruption due to layout confusion.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md/raid0: avoid RAID0 data corruption due to layout confusion.
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid0: avoid RAID0 data corruption due to layout confusion.
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH v2] md: don't let spare disk become the fresh disk in analyze_sbs()
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH v2] md: don't let spare disk become the fresh disk in analyze_sbs()
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: [PATCH] md: no longer compare spare disk superblock events in super_load
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: [PATCH] md/raid0: avoid RAID0 data corruption due to layout confusion.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] md/raid0: avoid RAID0 data corruption due to layout confusion.
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH 2/2] md: add feature flag MD_FEATURE_RAID0_LAYOUT
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] raid5: don't warn with STRIPE_ACTIVE flag in break_stripe_batch_list
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] md: add feature flag MD_FEATURE_RAID0_LAYOUT
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: [PATCH] raid5: don't warn with STRIPE_ACTIVE flag in break_stripe_batch_list
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH] md/raid0: avoid RAID0 data corruption due to layout confusion.
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: [PATCH] raid5: don't increment read_errors on EILSEQ return
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] md/raid0: avoid RAID0 data corruption due to layout confusion.
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 2/2] md: add feature flag MD_FEATURE_RAID0_LAYOUT
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md/raid0: avoid RAID0 data corruption due to layout confusion.
  • From: NeilBrown <neilb@xxxxxxx>
• [SOLVED] Re: --add-journal not working with 5.2.13??!!
  • From: Carlos Carvalho <carlos@xxxxxxxxxxxxxx>
• --add-journal not working with 5.2.13??!!
  • From: Carlos Carvalho <carlos@xxxxxxxxxxxxxx>
• [PATCH] raid5: don't increment read_errors on EILSEQ return
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH] raid5: don't warn with STRIPE_ACTIVE flag in break_stripe_batch_list
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: raid6 with dm-integrity should not cause device to fail
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: raid6 with dm-integrity should not cause device to fail
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: raid6 with dm-integrity should not cause device to fail
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: raid6 with dm-integrity should not cause device to fail
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: raid6 with dm-integrity should not cause device to fail
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: [PATCH] raid5: don't warn with STRIPE_ACTIVE flag in break_stripe_batch_list
  • From: Song Liu <songliubraving@xxxxxx>
• Re: raid6 with dm-integrity should not cause device to fail
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: raid6 with dm-integrity should not cause device to fail
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: [PATCH] raid5: don't warn with STRIPE_ACTIVE flag in break_stripe_batch_list
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: raid6 with dm-integrity should not cause device to fail
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: raid6 with dm-integrity should not cause device to fail
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH v4 2/2] mdadm: Introduce new array state 'broken' for raid0/linear
  • From: Song Liu <songliubraving@xxxxxx>
• Re: md0: bitmap file is out of date, resync
  • From: Mathias G <newsnet-mg-2016@xxxxxxxxxxxxx>
• Re: mdadm RAID5 to RAID6 migration thrown exceptions, access to data lost
  • From: Krzysztof Jakóbczyk <krzysiek.jakobczyk@xxxxxxxxx>
• Re: mdadm RAID5 to RAID6 migration thrown exceptions, access to data lost
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Fwd: mdadm RAID5 to RAID6 migration thrown exceptions, access to data lost
  • From: Krzysztof Jakóbczyk <krzysiek.jakobczyk@xxxxxxxxx>
• Re: [GIT PULL] md-next 20190903
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH v3 1/2] md raid0/linear: Mark array as 'broken' and fail BIOs if a member is gone
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH v4 1/2] md raid0/linear: Mark array as 'broken' and fail BIOs if a member is gone
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH] md/raid5: use bio_end_sector to calculate last_sector
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH v2] md/raid1: fail run raid1 array when active disk less than one
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [GIT PULL] md-next 20190903
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH v4 1/2] md raid0/linear: Mark array as 'broken' and fail BIOs if a member is gone
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH] md: no longer compare spare disk superblock events in super_load
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH v3 1/2] md raid0/linear: Mark array as 'broken' and fail BIOs if a member is gone
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH v4 1/2] md raid0/linear: Mark array as 'broken' and fail BIOs if a member is gone
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH v4 2/2] mdadm: Introduce new array state 'broken' for raid0/linear
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: Fwd: mdadm RAID5 to RAID6 migration thrown exceptions, access to data lost
  • From: Krzysztof Jakóbczyk <krzysiek.jakobczyk@xxxxxxxxx>
• Re: Fwd: mdadm RAID5 to RAID6 migration thrown exceptions, access to data lost
  • From: Phil Turmel <philip@xxxxxxxxxx>
• [PATCH v2] md/raid1: fail run raid1 array when active disk less than one
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: Fwd: mdadm RAID5 to RAID6 migration thrown exceptions, access to data lost
  • From: Krzysztof Jakóbczyk <krzysiek.jakobczyk@xxxxxxxxx>
• [PATCH] md/raid5: use bio_end_sector to calculate last_sector
  • From: Guoqing Jiang <jgq516@xxxxxxxxx>
• Re: md0: bitmap file is out of date, resync
  • From: Hou Tao <houtao1@xxxxxxxxxx>
• Re: [PATCH] md/raid1: fail run raid1 array when active disk less than one
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Fwd: mdadm RAID5 to RAID6 migration thrown exceptions, access to data lost
  • From: NeilBrown <neilb@xxxxxxx>
• Re: Fwd: mdadm RAID5 to RAID6 migration thrown exceptions, access to data lost
  • From: Krzysztof Jakóbczyk <krzysiek.jakobczyk@xxxxxxxxx>
• Re: Fwd: mdadm RAID5 to RAID6 migration thrown exceptions, access to data lost
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Fwd: mdadm RAID5 to RAID6 migration thrown exceptions, access to data lost
  • From: Krzysztof Jakóbczyk <krzysiek.jakobczyk@xxxxxxxxx>
• Re: Fwd: mdadm RAID5 to RAID6 migration thrown exceptions, access to data lost
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Fwd: mdadm RAID5 to RAID6 migration thrown exceptions, access to data lost
  • From: Krzysztof Jakóbczyk <krzysiek.jakobczyk@xxxxxxxxx>
• Re: [PATCH] md/raid1: fail run raid1 array when active disk less than one
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: [PATCH] md/raid1: fail run raid1 array when active disk less than one
  • From: NeilBrown <neilb@xxxxxxx>
• [PATCH] md/raid1: fail run raid1 array when active disk less than one
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• [PATCH] md: no longer compare spare disk superblock events in super_load
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: Kernel error at a LVM snapshot creation
  • From: NeilBrown <neilb@xxxxxxx>
• Re: md0: bitmap file is out of date, resync
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: md0: bitmap file is out of date, resync
  • From: Mathias G <newsnet-mg-2016@xxxxxxxxxxxxx>
• Kernel error at a LVM snapshot creation
  • From: Dmitrij Gusev <dmitrij@xxxxxxxx>
• Kernel error at a LVM snapshot creation
  • From: Dmitrij Gusev <dmitrij@xxxxxxxx>
• Re: [RFC PATCH] md/raid5: set STRIPE_SIZE as a configurable value
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: [PATCH] raid5: don't warn with STRIPE_SYNCING flag in break_stripe_batch_list
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: WARNING in break_stripe_batch_list with "stripe state: 2001"
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: [PATCH v3 2/2] mdadm: Introduce new array state 'broken' for raid0/linear
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH v3 1/2] md raid0/linear: Mark array as 'broken' and fail BIOs if a member is gone
  • From: Guilherme Piccoli <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH v3 1/2] md raid0/linear: Mark array as 'broken' and fail BIOs if a member is gone
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: WARNING in break_stripe_batch_list with "stripe state: 2001"
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [RFC PATCH] md/raid5: set STRIPE_SIZE as a configurable value
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH v3 2/2] mdadm: Introduce new array state 'broken' for raid0/linear
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH v3 1/2] md raid0/linear: Mark array as 'broken' and fail BIOs if a member is gone
  • From: NeilBrown <neilb@xxxxxxx>
• Re: [PATCH] raid5: don't warn with STRIPE_SYNCING flag in break_stripe_batch_list
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH] raid5: don't warn with STRIPE_SYNCING flag in break_stripe_batch_list
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH] raid5: don't warn with STRIPE_SYNCING flag in break_stripe_batch_list
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: [PATCH v3 2/2] mdadm: Introduce new array state 'broken' for raid0/linear
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH AUTOSEL 4.19 02/29] Revert "dm bufio: fix deadlock with loop device"
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.14 02/14] Revert "dm bufio: fix deadlock with loop device"
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.9 1/8] Revert "dm bufio: fix deadlock with loop device"
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.4 1/6] Revert "dm bufio: fix deadlock with loop device"
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [PATCH] raid5: don't warn with STRIPE_SYNCING flag in break_stripe_batch_list
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• [RFC PATCH] md/raid5: set STRIPE_SIZE as a configurable value
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: [PATCH] raid5: don't warn with STRIPE_SYNCING flag in break_stripe_batch_list
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH] raid5: don't warn with STRIPE_SYNCING flag in break_stripe_batch_list
  • From: Guoqing Jiang <jgq516@xxxxxxxxx>
• Re: [GIT PULL] md-next 20190827
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [GIT PULL] md-next 20190827
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [GIT PULL] md-next 20190827
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [GIT PULL] md-next 20190827
  • From: Song Liu <songliubraving@xxxxxx>
• Re: WARNING in break_stripe_batch_list with "stripe state: 2001"
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] raid5: fix spelling mistake \"bion\" -> \"bios\"
  • From: sunnyZhang <sunny.s.zhang@xxxxxxxxxx>
• Re: [PATCH] raid5: fix spelling mistake \"bion\" -> \"bios\"
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: WARNING in break_stripe_batch_list with "stripe state: 2001"
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• [PATCH] raid5: fix spelling mistake \"bion\" -> \"bios\"
  • From: Shuning Zhang <sunny.s.zhang@xxxxxxxxxx>
• [PATCH] raid5: fix spelling mistake \"bion\" -> \"bios\"
  • From: Shuning Zhang <sunny.s.zhang@xxxxxxxxxx>
• Re: WARNING in break_stripe_batch_list with "stripe state: 2001"
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: WARNING in break_stripe_batch_list with "stripe state: 2001"
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Failed raid after two devices temporarily failed
  • From: Alex Pilon <therealalexpilon@xxxxxxxxx>
• Re: [PATCH] md: update MAINTAINERS info
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH v3 1/2] md raid0/linear: Mark array as 'broken' and fail BIOs if a member is gone
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH v3 1/2] md raid0/linear: Mark array as 'broken' and fail BIOs if a member is gone
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [RFC] How to handle an ugly md raid0 sector map bug ?
  • From: Coly Li <colyli@xxxxxxx>
• Re: [RFC] How to handle an ugly md raid0 sector map bug ?
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [RFC] How to handle an ugly md raid0 sector map bug ?
  • From: Coly Li <colyli@xxxxxxx>
• Re: md0: bitmap file is out of date, resync
  • From: Hou Tao <houtao1@xxxxxxxxxx>
• Re: [RFC] How to handle an ugly md raid0 sector map bug ?
  • From: Song Liu <songliubraving@xxxxxx>
• Re: md0: bitmap file is out of date, resync
  • From: Mathias G <newsnet-mg-2016@xxxxxxxxxxxxx>
• Re: Issues about the merge_bvec_fn callback in 3.10 series
  • From: Jianchao Wang <jianchao.wan9@xxxxxxxxx>
• Re: Issues about the merge_bvec_fn callback in 3.10 series
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [RFC] How to handle an ugly md raid0 sector map bug ?
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v3 2/2] mdadm: Introduce new array state 'broken' for raid0/linear
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH v3 1/2] md raid0/linear: Mark array as 'broken' and fail BIOs if a member is gone
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH] md: update MAINTAINERS info
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH v2 1/2] md raid0/linear: Introduce new array state 'broken'
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH v2] md raid0/linear: Fail BIOs if their underlying block device is gone
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH v3 2/2] mdadm: Introduce new array state 'broken' for raid0/linear
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH v3 1/2] md raid0/linear: Mark array as 'broken' and fail BIOs if a member is gone
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH v2 1/2] md raid0/linear: Introduce new array state 'broken'
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [RFC] How to handle an ugly md raid0 sector map bug ?
  • From: Coly Li <colyli@xxxxxxx>
• Re: [PATCH v2 1/2] md raid0/linear: Introduce new array state 'broken'
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: Issues about the merge_bvec_fn callback in 3.10 series
  • From: Jianchao Wang <jianchao.wan9@xxxxxxxxx>
• Re: [PATCH] md: update MAINTAINERS info
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] md: update MAINTAINERS info
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] md: update MAINTAINERS info
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH] md: update MAINTAINERS info
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH v2 1/2] md raid0/linear: Introduce new array state 'broken'
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH v2 1/2] md raid0/linear: Introduce new array state 'broken'
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH] md: update MAINTAINERS info
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH v2 1/2] md raid0/linear: Introduce new array state 'broken'
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 0/2] Two md fixes suitable for -stable
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] raid5 improve too many read errors msg by adding limits
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH v2 1/2] md raid0/linear: Introduce new array state 'broken'
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH v2 1/2] md raid0/linear: Introduce new array state 'broken'
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH] raid5 improve too many read errors msg by adding limits
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Issues about the merge_bvec_fn callback in 3.10 series
  • From: Jianchao Wang <jianchao.wan9@xxxxxxxxx>
• Re: [PATCH] raid5 improve too many read errors msg by adding limits
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] raid5 improve too many read errors msg by adding limits
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: 5.1.21 Dell 2950 terrible swraid5 I/O performance with swraid on top of Perc 5/i raid0/jbod
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: Bisected: Kernel 4.14 + has 3 times higher write IO latency than Kernel 4.4 with raid1
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH 2/2] md: don't report active array_state until after revalidate_disk() completes.
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH 1/2] md: only call set_in_sync() when it is expected to succeed.
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH 0/2] Two md fixes suitable for -stable
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH v2 1/2] md raid0/linear: Introduce new array state 'broken'
  • From: Song Liu <songliubraving@xxxxxx>
• md-cluster + raid1 and raid0 / clvm
  • From: "Thomas Rosenstein" <thomas.rosenstein@xxxxxxxxxxxxxxxx>
• Re: 5.1.21 Dell 2950 terrible swraid5 I/O performance with swraid on top of Perc 5/i raid0/jbod
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: [PATCH v2 1/2] md raid0/linear: Introduce new array state 'broken'
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH v2 1/2] md raid0/linear: Introduce new array state 'broken'
  • From: Song Liu <songliubraving@xxxxxx>
• Re: 5.1.21 Dell 2950 terrible swraid5 I/O performance with swraid on top of Perc 5/i raid0/jbod
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: [PATCH v2 1/2] md raid0/linear: Introduce new array state 'broken'
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH v2 1/2] md raid0/linear: Introduce new array state 'broken'
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: 5.1.21 Dell 2950 terrible swraid5 I/O performance with swraid on top of Perc 5/i raid0/jbod
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: 5.1.21 Dell 2950 terrible swraid5 I/O performance with swraid on top of Perc 5/i raid0/jbod
  • From: Paolo Valente <paolo.valente@xxxxxxxxxx>
• Re: 5.1.21 Dell 2950 terrible swraid5 I/O performance with swraid on top of Perc 5/i raid0/jbod
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: 5.1.21 Dell 2950 terrible swraid5 I/O performance with swraid on top of Perc 5/i raid0/jbod
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: 5.1.21 Dell 2950 terrible swraid5 I/O performance with swraid on top of Perc 5/i raid0/jbod
  • From: Paolo Valente <paolo.valente@xxxxxxxxxx>
• Re: 5.1.21 Dell 2950 terrible swraid5 I/O performance with swraid on top of Perc 5/i raid0/jbod
  • From: o1bigtenor <o1bigtenor@xxxxxxxxx>
• Re: 5.1.21 Dell 2950 terrible swraid5 I/O performance with swraid on top of Perc 5/i raid0/jbod
  • From: Paolo Valente <paolo.valente@xxxxxxxxxx>
• 5.1.21 Dell 2950 terrible swraid5 I/O performance with swraid on top of Perc 5/i raid0/jbod
  • From: Marc MERLIN <marc@xxxxxxxxxxx>
• Re: [PATCH] raid5 improve too many read errors msg by adding limits
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] raid5 improve too many read errors msg by adding limits
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] raid5 improve too many read errors msg by adding limits
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH] imsm: data offset support during first volume creation
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH,v2] mdadm: check value returned by snprintf against errors
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 1/2] md/raid0: Introduce new array state 'broken' for raid0
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH v2 2/2] mdadm: Introduce new array state 'broken' for raid0/linear
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH v2 1/2] md raid0/linear: Introduce new array state 'broken'
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH v2] md raid0/linear: Fail BIOs if their underlying block device is gone
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH] imsm: data offset support during first volume creation
  • From: Krzysztof Smolinski <krzysztof.smolinski@xxxxxxxxx>
• Re: [PATCH,v2] mdadm: check value returned by snprintf against errors
  • From: Paul Menzel <pmenzel@xxxxxxxxxxxxx>
• [PATCH,v2] mdadm: check value returned by snprintf against errors
  • From: Krzysztof Smolinski <krzysztof.smolinski@xxxxxxxxx>
• RE: [PATCH] mdadm: fixed mdadm compilation on gcc8
  • From: "Smolinski, Krzysztof" <krzysztof.smolinski@xxxxxxxxx>
• Re: Bisected: Kernel 4.14 + has 3 times higher write IO latency than Kernel 4.4 with raid1
  • From: Jinpu Wang <jinpu.wang@xxxxxxxxxxxxxxx>
• Re: [PATCH] raid5 improve too many read errors msg by adding limits
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] raid5 improve too many read errors msg by adding limits
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• An annoyance resolved
  • From: "Renaud (Ron) OLGIATI" <renaud@xxxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mdadm: fixed mdadm compilation on gcc8
  • From: Paul Menzel <pmenzel@xxxxxxxxxxxxx>
• [PATCH] mdadm: fixed mdadm compilation on gcc8
  • From: Mariusz Dabrowski <mariusz.dabrowski@xxxxxxxxx>
• Re: [PATCH] raid5 improve too many read errors msg by adding limits
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH v2 2/2] udev: add --no-devices option for calling 'mdadm --detail'
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH v2 1/2] mdadm: add --no-devices to avoid component devices detail information
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] mdadm.h: include sysmacros.h unconditionally
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [PATCH] raid5 improve too many read errors msg by adding limits
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: Regression in mdadm breaks assembling of array
  • From: Stephan Diestelhorst <stephan.diestelhorst@xxxxxxxxx>
• Re: [PATCH] mdadm.h: include sysmacros.h unconditionally
  • From: Hauke Mehrtens <hauke@xxxxxxxxxx>
• Re: [GIT PULL] md-next 20190807
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: mdadm reports two different UUIDs on s390
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• [GIT PULL] md-next 20190807
  • From: Song Liu <songliubraving@xxxxxx>
• Re: Raid5 2 drive failure (and my spare failed too)
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• WARNING in break_stripe_batch_list with "stripe state: 2001"
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: Bisected: Kernel 4.14 + has 3 times higher write IO latency than Kernel 4.4 with raid1
  • From: Jinpu Wang <jinpu.wang@xxxxxxxxxxxxxxx>
• Re: Bisected: Kernel 4.14 + has 3 times higher write IO latency than Kernel 4.4 with raid1
  • From: Jinpu Wang <jinpu.wang@xxxxxxxxxxxxxxx>
• Re: Bisected: Kernel 4.14 + has 3 times higher write IO latency than Kernel 4.4 with raid1
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH] mdadm.h: include sysmacros.h unconditionally
  • From: Baruch Siach <baruch@xxxxxxxxxx>
• Re: Bisected: Kernel 4.14 + has 3 times higher write IO latency than Kernel 4.4 with raid1
  • From: Jinpu Wang <jinpu.wang@xxxxxxxxxxxxxxx>
• Re: Bisected: Kernel 4.14 + has 3 times higher write IO latency than Kernel 4.4 with raid1
  • From: Jinpu Wang <jinpu.wang@xxxxxxxxxxxxxxx>
• Unrelated question and threading (was: Bisected: Kernel 4.14 + has 3 times higher write IO latency than Kernel 4.4 with raid1)
  • From: Paul Menzel <pmenzel@xxxxxxxxxxxxx>
• Re: Bisected: Kernel 4.14 + has 3 times higher write IO latency than Kernel 4.4 with raid1
  • From: riccardofarabia@xxxxxxxxx
• Re: Raid5 2 drive failure (and my spare failed too)
  • From: Ryan Heath <gaauuool@xxxxxxxxx>
• Re: Bisected: Kernel 4.14 + has 3 times higher write IO latency than Kernel 4.4 with raid1
  • From: NeilBrown <neilb@xxxxxxxx>
• Bisected: Kernel 4.14 + has 3 times higher write IO latency than Kernel 4.4 with raid1
  • From: Jinpu Wang <jinpu.wang@xxxxxxxxxxxxxxx>
• Re: Kernel 4.14 + has 100 times higher IO latency than Kernel 4.4 with raid1
  • From: Jinpu Wang <jinpu.wang@xxxxxxxxxxxxxxx>
• Re: Raid5 2 drive failure (and my spare failed too)
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Raid5 2 drive failure (and my spare failed too)
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Raid5 2 drive failure (and my spare failed too)
  • From: Ryan Heath <gaauuool@xxxxxxxxx>
• [mdadm PATCH] Add missing include file sys/sysmacros.h
  • From: Hauke Mehrtens <hauke@xxxxxxxxxx>
• Re: Kernel 4.14 + has 100 times higher IO latency than Kernel 4.4 with raid1
  • From: Paul Menzel <pmenzel@xxxxxxxxxxxxx>
• Kernel 4.14 + has 100 times higher IO latency than Kernel 4.4 with raid1
  • From: Jinpu Wang <jinpu.wang@xxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] md/raid0: Introduce new array state 'broken' for raid0
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH] md/raid1: fix a race between removing rdev and access conf->mirrors[i].rdev
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH 0/3] md: export internal stats through debugfs
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] md/raid1: fix a race between removing rdev and access conf->mirrors[i].rdev
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] raid1: factor out a common routine to handle the completion of sync write
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 1/2] md/raid0: Introduce new array state 'broken' for raid0
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 1/2] md/raid0: Introduce new array state 'broken' for raid0
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 1/2] md/raid0: Introduce new array state 'broken' for raid0
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH] md/raid1: fix a race between removing rdev and access conf->mirrors[i].rdev
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] mdadm: add --no-devices to avoid component devices detail information
  • From: Coly Li <colyli@xxxxxxx>
• [PATCH v2 2/2] udev: add --no-devices option for calling 'mdadm --detail'
  • From: Coly Li <colyli@xxxxxxx>
• [PATCH v2 1/2] mdadm: add --no-devices to avoid component devices detail information
  • From: Coly Li <colyli@xxxxxxx>
• Re: [PATCH 1/2] md/raid0: Introduce new array state 'broken' for raid0
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 2/2] udev: add --no-devices option for calling 'mdadm --detail'
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH 1/2] mdadm: add --no-devices to avoid component devices detail information
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: RAID-1 from SAS to SSD
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• [PATCH 2/2] udev: add --no-devices option for calling 'mdadm --detail'
  • From: Coly Li <colyli@xxxxxxx>
• [PATCH 1/2] mdadm: add --no-devices to avoid component devices detail information
  • From: Coly Li <colyli@xxxxxxx>
• Re: [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] md/raid0: Introduce new array state 'broken' for raid0
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: RAID-1 from SAS to SSD
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] md/raid0: Introduce new array state 'broken' for raid0
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• RAID-1 from SAS to SSD
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• Re: [PATCH] md/raid1: fix a race between removing rdev and access conf->mirrors[i].rdev
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: [PATCH 1/2] md/raid0: Introduce new array state 'broken' for raid0
  • From: Bob Liu <bob.liu@xxxxxxxxxx>
• Re: [PATCH 1/2] md/raid0: Introduce new array state 'broken' for raid0
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• [PATCH 2/2] mdadm: Introduce new array state 'broken' for raid0
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH 1/2] md/raid0: Introduce new array state 'broken' for raid0
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH 0/2] Introduce new raid0 state 'broken'
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• [PATCH] md/raid0: Fail BIOs if their underlying block device is gone
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH] md/raid1: fix a race between removing rdev and access conf->mirrors[i].rdev
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid1: fix a race between removing rdev and access conf->mirrors[i].rdev
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: [PATCH] md/raid1: fix a race between removing rdev and access conf->mirrors[i].rdev
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid1: fix a race between removing rdev and access conf->mirrors[i].rdev
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: [PATCH] md/raid1: fix a race between removing rdev and access conf->mirrors[i].rdev
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: memory leak in bio_copy_user_iov
  • From: Bob Liu <bob.liu@xxxxxxxxxx>
• Re: memory leak in bio_copy_user_iov
  • From: syzbot <syzbot+03e5c8ebd22cc6c3a8cb@xxxxxxxxxxxxxxxxxxxxxxxxx>
• [PATCH] raid1: factor out a common routine to handle the completion of sync write
  • From: Hou Tao <houtao1@xxxxxxxxxx>
• Re: [RFC PATCH 0/3] md: export internal stats through debugfs
  • From: Hou Tao <houtao1@xxxxxxxxxx>
• Re: [RFC PATCH 0/3] md: export internal stats through debugfs
  • From: Hou Tao <houtao1@xxxxxxxxxx>
• Re: [PATCH] md/raid1: fix a race between removing rdev and access conf->mirrors[i].rdev
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: [PATCH v1] md: Convert to use int_pow()
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 0/3] enable fail last device in raid1/10 array
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH v1] md: Convert to use int_pow()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH v1] md: Convert to use int_pow()
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH v1] md: Convert to use int_pow()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: [PATCH] md/raid1: fix a race between removing rdev and access conf->mirrors[i].rdev
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/3] md: don't set In_sync if array is frozen
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• [PATCH] md/raid1: fix a race between removing rdev and access conf->mirrors[i].rdev
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: [PATCH 2/3] md: don't set In_sync if array is frozen
  • From: yuyufen <yuyufen@xxxxxxxxxx>
• [PATCH] md: do not set suspend_hi when ->quiesce is null
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• [PATCH 3/3] md: don't call spare_active in md_reap_sync_thread if all member devices can't work
  • From: Guoqing Jiang <jgq516@xxxxxxxxx>
• [PATCH 2/3] md: don't set In_sync if array is frozen
  • From: Guoqing Jiang <jgq516@xxxxxxxxx>
• [PATCH 1/3] md: allow last device to be forcibly removed from RAID1/RAID10.
  • From: Guoqing Jiang <jgq516@xxxxxxxxx>
• [PATCH 0/3] enable fail last device in raid1/10 array
  • From: Guoqing Jiang <jgq516@xxxxxxxxx>
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [PATCH v1] md: Convert to use int_pow()
  • From: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Luca Lazzarin <luca.lazzarin@xxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Luca Lazzarin <luca.lazzarin@xxxxxxxxx>
• Re: [V2 PATCH] Set R5_ReadError when there is read failure on parity disk of raid6
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [RFC PATCH 0/3] md: export internal stats through debugfs
  • From: Bob Liu <bob.liu@xxxxxxxxxx>
• Re: [PATCH 0/2] md: not need error handling when device faulty
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] md/raid1: remove the unnecessary plug in raid1d()
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [V2 PATCH] Set R5_ReadError when there is read failure on parity disk of raid6
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] raid1: use an int as the return value of raise_barrier()
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [RFC PATCH 0/3] md: export internal stats through debugfs
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: Coly Li <colyli@xxxxxxx>
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx>
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx>
• Re: [PATCH 1/1] bad block is after superblock and bitmap
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH 1/1] bad block is after superblock and bitmap
  • From: Hou Tao <houtao1@xxxxxxxxxx>
• [PATCH 1/1] bad block is after superblock and bitmap
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [PATCH 1/1] Don't allow create ddf container on partitioned devices
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [PATCH 2/2] md/raid10: end bio when the device faulty
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• [PATCH 0/2] md: not need error handling when device faulty
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• [PATCH 1/2] md/raid1: end bio when the device faulty
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• mdadm reports two different UUIDs on s390
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: pg@xxxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: pg@xxxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: pg@xxxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: pg@xxxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: pg@xxxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: Guoqing Jiang <guoqing.jiang@xxxxxxxxxxxxxxx>
• Re: slow BLKDISCARD on RAID10 md block devices
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• slow BLKDISCARD on RAID10 md block devices
  • From: Lennert Buytenhek <buytenh@xxxxxxxxxxxxxx>
• [PATCH] imsm: close removed drive fd.
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• [PATCH] Revert "tests: wait for complete rebuild in integrity checks"
  • From: <mingli.yu@xxxxxxxxxxxxx>
• Re: Weird behaviour of md, maybe a bug in 4.19.xx kernel? [SOLVED]
  • From: Tito <farmatito@xxxxxxxxxx>
• Re: Weird behaviour of md, maybe a bug in 4.19.xx kernel?
  • From: Tito <farmatito@xxxxxxxxxx>
• Re: Weird behaviour of md, maybe a bug in 4.19.xx kernel?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Weird behaviour of md, maybe a bug in 4.19.xx kernel?
  • From: Tito <farmatito@xxxxxxxxxx>
• Re: Weird behaviour of md, maybe a bug in 4.19.xx kernel?
  • From: Sarah Newman <srn@xxxxxxxxx>
• Re: Weird behaviour of md, maybe a bug in 4.19.xx kernel?
  • From: Tito <farmatito@xxxxxxxxxx>
• Re: Weird behaviour of md, maybe a bug in 4.19.xx kernel?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Weird behaviour of md, maybe a bug in 4.19.xx kernel?
  • From: Tito <farmatito@xxxxxxxxxx>
• Re: [PATCH] imsm: Change in --detail-platform for NVMe devices
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [PATCH] imsm: Change in --detail-platform for NVMe devices
  • From: Blazej Kucman <blazej.kucman@xxxxxxxxx>
• Re: Regression in mdadm breaks assembling of array
  • From: Stephan Diestelhorst <stephan.diestelhorst@xxxxxxxxx>
• Re: [PATCH v2] mdadm: load default sysfs attributes after assemblation
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
• [PATCH v2] mdadm: load default sysfs attributes after assemblation
  • From: Mariusz Dabrowski <mariusz.dabrowski@xxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Luca Lazzarin <luca.lazzarin@xxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Luca Lazzarin <luca.lazzarin@xxxxxxxxx>
• Re: Raid 1 vs Raid 5 suggestion
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Raid 1 vs Raid 5 suggestion
  • From: Luca Lazzarin <luca.lazzarin@xxxxxxxxx>
• Re: Regression in mdadm breaks assembling of array
  • From: Mariusz Dabrowski <mariusz.dabrowski@xxxxxxxxx>
• [PATCH] md/raid1: remove the unnecessary plug in raid1d()
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• [V2 PATCH] Set R5_ReadError when there is read failure on parity disk of raid6
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH] Set R5_ReadError when there is read failure on parity disk of raid6
  • From: kbuild test robot <lkp@xxxxxxxxx>
• Re: md0: bitmap file is out of date, resync
  • From: Mathias G <newsnet-mg-2016@xxxxxxxxxxxxx>
• Re: md0: bitmap file is out of date, resync
  • From: Hou Tao <houtao1@xxxxxxxxxx>
• [PATCH] Set R5_ReadError when there is read failure on parity disk of raid6
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: md-multipath: Replace a seq_printf() call by seq_putc() in multipath_status()
  • From: Markus Elfring <Markus.Elfring@xxxxxx>
• Re: [4.19.y PATCH 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: Guilherme Piccoli <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH] md-multipath: Replace a seq_printf() call by seq_putc() in multipath_status()
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [4.19.y PATCH 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] mdadm: load default sysfs attributes after assemblation
  • From: Mariusz Dabrowski <mariusz.dabrowski@xxxxxxxxx>
• Re: [4.19.y PATCH 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [4.19.y PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [PATCH] raid1: use an int as the return value of raise_barrier()
  • From: Hou Tao <houtao1@xxxxxxxxxx>
• [RFC PATCH 0/3] md: export internal stats through debugfs
  • From: Hou Tao <houtao1@xxxxxxxxxx>
• [RFC PATCH 1/3] md-debugfs: add md_debugfs_create_files()
  • From: Hou Tao <houtao1@xxxxxxxxxx>
• [RFC PATCH 2/3] md: export inflight io counters and internal stats in debugfs
  • From: Hou Tao <houtao1@xxxxxxxxxx>
• [RFC PATCH 3/3] raid1: export inflight io counters and internal stats in debugfs
  • From: Hou Tao <houtao1@xxxxxxxxxx>
• Re: [PATCH] Enable probe_roms to scan more than 6 roms.
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• [PATCH] Enable probe_roms to scan more than 6 roms.
  • From: Roman Sobanski <roman.sobanski@xxxxxxxxx>
• Re: [PATCH] mdadm: load default sysfs attributes after assemblation
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• [PATCH] md/raid: Replace a seq_printf() call by seq_putc() in three functions
  • From: Markus Elfring <Markus.Elfring@xxxxxx>
• [PATCH] md-multipath: Replace a seq_printf() call by seq_putc() in multipath_status()
  • From: Markus Elfring <Markus.Elfring@xxxxxx>
• [4.19.y PATCH 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [4.19.y PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH 14/39] docs: device-mapper: move it to the admin-guide
  • From: Mauro Carvalho Chehab <mchehab+samsung@xxxxxxxxxx>
• Re: md0: bitmap file is out of date, resync
  • From: Mathias G <newsnet-mg-2016@xxxxxxxxxxxxx>
• [PATCH AUTOSEL 5.1 83/95] md: fix for divide error in status_resync
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.19 51/60] md: fix for divide error in status_resync
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.14 28/35] md: fix for divide error in status_resync
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.9 18/21] md: fix for divide error in status_resync
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• [PATCH AUTOSEL 4.4 11/12] md: fix for divide error in status_resync
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [GIT PULL] fix for md-next 20190626
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [GIT PULL] fix for md-next 20190626
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH] md/raid1: Fix a warning message in remove_wb()
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [PATCH] md/raid1: Fix a warning message in remove_wb()
  • From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
• [PATCH] mdadm: load default sysfs attributes after assemblation
  • From: Mariusz Dabrowski <mariusz.dabrowski@xxxxxxxxx>
• Re: md0: bitmap file is out of date, resync
  • From: Mathias G <newsnet-mg-2016@xxxxxxxxxxxxx>
• Re: [GIT PULL] md-next 20190620
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [GIT PULL] md-next 20190620
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 0/5] Fix potential data inconsistency issue with write behind device
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: WARNING: CPU: 13 PID: 3786 at drivers/md/raid5.c:4611 break_stripe_batch_list+0x86/0x1fb
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH 1/5 V2] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• raid6 with dm-integrity should not cause device to fail
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH 1/5 V2] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 1/5 V2] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [PATCH 1/5 V2] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 1/5] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Nikolay Kichukov <hijacker@xxxxxxxxx>
• Re: [PATCH 1/5] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 1/5] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 1/5] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [GIT PULL] md fixes 20190618
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] md: fix for divide error in status_resync
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [GIT PULL] md fixes 20190618
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 1/5] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 1/5] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 1/5] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Nikolay Kichukov <hijacker@xxxxxxxxx>
• Re: [PATCH 1/5] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 1/5] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 1/5] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 1/5] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: RAID-6 aborted reshape
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: md0: bitmap file is out of date, resync
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: md0: bitmap file is out of date, resync
  • From: Mathias G <newsnet-mg-2016@xxxxxxxxxxxxx>
• Re: [PATCH 0/8] md: for-5.3 changes
  • From: Jens Axboe <axboe@xxxxxxxxx>
• RE: RAID-6 aborted reshape
  • From: Colt Boyd <coltboyd@xxxxxxxxx>
• Re: md0: bitmap file is out of date, resync
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• md0: bitmap file is out of date, resync
  • From: Mathias G <newsnet-mg-2016@xxxxxxxxxxxxx>
• [PATCH 8/8] md/raid10: read balance chooses idlest disk for SSD
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 7/8] md: raid1-10: Unify r{1,10}bio_pool_free
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 6/8] md: raid10: Use struct_size() in kmalloc()
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 5/8] md/raid1: get rid of extra blank line and space
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 4/8] md: fix spelling typo and add necessary space
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 3/8] md: md.c: Return -ENODEV when mddev is NULL in rdev_attr_show
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 2/8] raid5-cache: Need to do start() part job after adding journal device
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 1/8] drivers: md: Unify common definitions of raid1 and raid10
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 0/8] md: for-5.3 changes
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 1/5] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] md: fix for divide error in status_resync
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH V2] md/raid10: read balance chooses idlest disk for SSD
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [PATCH 3/5] md-bitmap: create and destroy wb_info_pool with the change of backlog
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 4/5] md-bitmap: create and destroy wb_info_pool with the change of bitmap
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 5/5] md: add bitmap_abort label in md_run
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 2/5] md: introduce mddev_create/destroy_wb_pool for the change of member device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 0/5] Fix potential data inconsistency issue with write behind device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH 1/5] md/raid1: fix potential data inconsistency issue with write behind device
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: WARNING: CPU: 13 PID: 3786 at drivers/md/raid5.c:4611 break_stripe_batch_list+0x86/0x1fb
  • From: Marc Smith <msmith626@xxxxxxxxx>
• [PATCH V2] md/raid10: read balance chooses idlest disk for SSD
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• [PATCH] md: fix for divide error in status_resync
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Guilherme Piccoli <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Guilherme Piccoli <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Guilherme Piccoli <gpiccoli@xxxxxxxxxxxxx>
• Re: RAID-6 aborted reshape
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• mdadm: /dev/dm-4 not large enough to join array
  • From: listmailer273 <listmailer273@xxxxxxxxxxxxxx>
• Re: RAID-6 aborted reshape
  • From: Colt Boyd <coltboyd@xxxxxxxxx>
• Re: RAID-6 aborted reshape
  • From: Colt Boyd <coltboyd@xxxxxxxxx>
• Re: RAID-6 aborted reshape
  • From: Colt Boyd <coltboyd@xxxxxxxxx>
• Re: [PATCH] md/raid10: read balance chooses idlest disk for SSD
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] md/raid10: read balance chooses idlest disk for SSD
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 1/1] raid5-cache: Need to do start() part job after adding journal device
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] md/raid10: read balance chooses idlest disk for SSD
  • From: keld@xxxxxxxxxx
• Re: RAID-6 aborted reshape
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: RAID-6 aborted reshape
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH] md/raid10: read balance chooses idlest disk for SSD
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH] md/raid10: read balance chooses idlest disk for SSD
  • From: keld@xxxxxxxxxx
• [PATCH] md/raid10: read balance chooses idlest disk for SSD
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• RAID5 R5_Wantread BUG_ON in fetch_block
  • From: Fisher <fisherthepooh@xxxxxxxxxxxxxx>
• RE: RAID-6 aborted reshape
  • From: Colt Boyd <coltboyd@xxxxxxxxx>
• Re: [PATCH 1/1] raid5-cache: Need to do start() part job after adding journal device
  • From: Xiao Ni <xni@xxxxxxxxxx>
• RAID-6 aborted reshape
  • From: Colt Boyd <coltboyd@xxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Sarah Newman <srn@xxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: [PATCH] md: raid10: Use struct_size() in kmalloc()
  • From: "Gustavo A. R. Silva" <gustavo@xxxxxxxxxxxxxx>
• Re: [PATCH] md: raid10: Use struct_size() in kmalloc()
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 0/2] md: fix spelling typo and remove extra blank line
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] md: md.c: Return -ENODEV when mddev is NULL in rdev_attr_show
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 1/1] raid5-cache: Need to do start() part job after adding journal device
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [PATCH 2/2] md/raid1: get rid of extra blank line and space
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• [PATCH 1/2] md: fix spelling typo and add necessary space
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• [PATCH 0/2] md: fix spelling typo and remove extra blank line
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• [PATCH] md: raid10: Use struct_size() in kmalloc()
  • From: "Gustavo A. R. Silva" <gustavo@xxxxxxxxxxxxxx>
• Re: lost software raid information
  • From: Volker Lieder <v.lieder@xxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Kai Stian Olstad <raid+list@xxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: keld@xxxxxxxxxx
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: keld@xxxxxxxxxx
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: keld@xxxxxxxxxx
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• [PATCH AUTOSEL 4.4 38/56] md: add mddev->pers to avoid potential NULL pointer dereference
  • From: Sasha Levin <sashal@xxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: keld@xxxxxxxxxx
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• [RFC PATCH V3] mdadm/md.4: add the descriptions for bitmap sysfs nodes
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: keld@xxxxxxxxxx
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: keld@xxxxxxxxxx
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: keld@xxxxxxxxxx
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: keld@xxxxxxxxxx
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: keld@xxxxxxxxxx
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Robin Hill <robin@xxxxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: keld@xxxxxxxxxx
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: keld@xxxxxxxxxx
• Re: [RFC PATCH V2] mdadm/md.4: add the descriptions for bitmap sysfs nodes
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• RAID-1 can (sometimes) be 3x faster than RAID-10
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Optimising raid on 4k devices
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: Few questions about (attempting to use) write journal + call traces
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: Few questions about (attempting to use) write journal + call traces
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: [RFC PATCH V2] mdadm/md.4: add the descriptions for bitmap sysfs nodes
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Optimising raid on 4k devices
  • From: michael@xxxxxxxxxxxxx
• Re: Optimising raid on 4k devices
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Optimising raid on 4k devices
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/1] raid5-cache: Need to do start() part job after adding journal device
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: Few questions about (attempting to use) write journal + call traces
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: Optimising raid on 4k devices
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [PATCH 1/1] raid5-cache: Need to do start() part job after adding journal device
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Few questions about (attempting to use) write journal + call traces
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: Few questions about (attempting to use) write journal + call traces
  • From: Michal Soltys <soltys@xxxxxxxx>
• [RFC PATCH V2] mdadm/md.4: add the descriptions for bitmap sysfs nodes
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [RFC PATCH] mdadm/md.4: add the descriptions for bitmap sysfs nodes
  • From: NeilBrown <neilb@xxxxxxxx>
• Optimising raid on 4k devices
  • From: Matthew Moore <matthew@moore.sydney>
• Re: help recovering raid5 after degraded to 2 disks and then i/o errors on 1 of the 2
  • From: Emmanouil Kapernaros <manolis@xxxxxxxxx>
• Re: BUG: RAID6 recovery broken by commit 4f4fd7c5798bbdd5a03a60f6269cf1177fbd11ef (Linux 5.1.3)
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: Few questions about (attempting to use) write journal + call traces
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [PATCH] mdadm: use pkgconfig to find systemd unit dir
  • From: luca.boccassi@xxxxxxxxx
• Re: Few questions about (attempting to use) write journal + call traces
  • From: Michal Soltys <soltys@xxxxxxxx>
• Re: BUG: RAID6 recovery broken by commit 4f4fd7c5798bbdd5a03a60f6269cf1177fbd11ef (Linux 5.1.3)
  • From: Thorsten Knabe <linux@xxxxxxxxxxxxxxxxx>
• [PATCH] md: md.c: Return -ENODEV when mddev is NULL in rdev_attr_show
  • From: Marcos Paulo de Souza <marcos.souza.org@xxxxxxxxx>
• Re: [PATCH V2 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: Guilherme Piccoli <gpiccoli@xxxxxxxxxxxxx>
• Re: Fix bad backport to stable v3.16+
  • From: Song Liu <songliubraving@xxxxxx>
• Re: Few questions about (attempting to use) write journal + call traces
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: Fix bad backport to stable v3.16+
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH V2 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH V2 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: Few questions about (attempting to use) write journal + call traces
  • From: Michal Soltys <soltys@xxxxxxxx>
• [RFC PATCH] mdadm/md.4: add the descriptions for bitmap sysfs nodes
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: Few questions about (attempting to use) write journal + call traces
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: BUG: RAID6 recovery broken by commit 4f4fd7c5798bbdd5a03a60f6269cf1177fbd11ef (Linux 5.1.3)
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Fix bad backport to stable v3.16+
  • From: Song Liu <songliubraving@xxxxxx>
• Re: BUG: RAID6 recovery broken by commit 4f4fd7c5798bbdd5a03a60f6269cf1177fbd11ef (Linux 5.1.3)
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Few questions about (attempting to use) write journal + call traces
  • From: Michal Soltys <soltys@xxxxxxxx>
• BUG: RAID6 recovery broken by commit 4f4fd7c5798bbdd5a03a60f6269cf1177fbd11ef (Linux 5.1.3)
  • From: Thorsten Knabe <linux@xxxxxxxxxxxxxxxxx>
• Re: [PATCH V2 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Guilherme Piccoli <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH V2 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH V2 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Guilherme Piccoli <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH V2 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH V2 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [PATCH V2 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: Guilherme Piccoli <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH] drivers: md: Unify common definitions of raid1 and raid10
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH V2 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 2/4] md: raid0: Remove return statement from void function
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [PATCH V2 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH V2 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH 3/4] md: raid0: Return md_integrity_register result directly
  • From: Marcos Paulo de Souza <marcos.souza.org@xxxxxxxxx>
• [PATCH 4/4] md: raid0: Make ret local in raid0_run
  • From: Marcos Paulo de Souza <marcos.souza.org@xxxxxxxxx>
• [PATCH 2/4] md: raid0: Remove return statement from void function
  • From: Marcos Paulo de Souza <marcos.souza.org@xxxxxxxxx>
• [PATCH 1/4] md: raid1-10: Unify r{1,10}bio_pool_free
  • From: Marcos Paulo de Souza <marcos.souza.org@xxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Guilherme Piccoli <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH] mdmon: fix wrong array state when disk fails during mdmon startup
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: Eric Ren <renzhengeek@xxxxxxxxx>
• Re: Is --write-mostly supposed to do anything for SSD- and NVMe-class devices?
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: Is --write-mostly supposed to do anything for SSD- and NVMe-class devices?
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: [PATCH 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: Ming Lei <tom.leiming@xxxxxxxxx>
• Is --write-mostly supposed to do anything for SSD- and NVMe-class devices?
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: "Guilherme G. Piccoli" <kernel@xxxxxxxxxxxx>
• Re: [PATCH 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: "Guilherme G. Piccoli" <kernel@xxxxxxxxxxxx>
• Re: [PATCH 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: Eric Ren <renzhengeek@xxxxxxxxx>
• Re: [PATCH] drivers: md: Unify common definitions of raid1 and raid10
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] drivers: md: Unify common definitions of raid1 and raid10
  • From: Marcos Paulo de Souza <marcos.souza.org@xxxxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Eric Valette <eric.valette@xxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Julien ROBIN <julien.robin28@xxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Eric Valette <eric.valette@xxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Eric Valette <eric.valette@xxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Eric Valette <eric.valette@xxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Julien ROBIN <julien.robin28@xxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Eric Valette <eric.valette@xxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Julien ROBIN <julien.robin28@xxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Eric Valette <eric.valette@xxxxxxx>
• Re: Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Feng Zhang <prod.feng@xxxxxxxxx>
• Help restoring a raid10 Array (4 disk + one spare) after a hard disk failure at power on
  • From: Eric Valette <eric.valette@xxxxxxx>
• Re: ID 5 Reallocated Sectors Count
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: [PATCH 1/1] raid5-cache: rename r5l_flush_stripe_to_raid to r5l_flush_stripe_to_journal
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: best way to replace all disks
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• Re: ID 5 Reallocated Sectors Count
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: [PATCH 1/1] raid5-cache: rename r5l_flush_stripe_to_raid to r5l_flush_stripe_to_journal
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 1/1] raid5-cache: rename r5l_flush_stripe_to_raid to r5l_flush_stripe_to_journal
  • From: Xiao Ni <xni@xxxxxxxxxx>
• recovering a single device RAID
  • From: "Boylan, Ross" <Ross.Boylan@xxxxxxxx>
• Re: [PATCH 1/1] raid5-cache: rename r5l_flush_stripe_to_raid to r5l_flush_stripe_to_journal
  • From: Song Liu <songliubraving@xxxxxx>
• Re: ID 5 Reallocated Sectors Count
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• [PATCH 1/1] raid5-cache: rename r5l_flush_stripe_to_raid to r5l_flush_stripe_to_journal
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: ID 5 Reallocated Sectors Count
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• [PATCH] drivers: md: Unify common definitions of raid1 and raid10
  • From: Marcos Paulo de Souza <marcos.souza.org@xxxxxxxxx>
• Re: ID 5 Reallocated Sectors Count
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Spare pool documentation
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Spare pool documentation
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: ID 5 Reallocated Sectors Count
  • From: Mark Wagner <carnildo@xxxxxxxxx>
• Re: ID 5 Reallocated Sectors Count
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: ID 5 Reallocated Sectors Count
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: ID 5 Reallocated Sectors Count
  • From: Julien ROBIN <julien.robin28@xxxxxxx>
• Re: ID 5 Reallocated Sectors Count
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: ID 5 Reallocated Sectors Count
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: ID 5 Reallocated Sectors Count
  • From: Julien ROBIN <julien.robin28@xxxxxxx>
• Re: ID 5 Reallocated Sectors Count
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• ID 5 Reallocated Sectors Count
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: "Guilherme G. Piccoli" <guilherme@xxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Spare pool documentation
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• [PATCH] mdmon: fix wrong array state when disk fails during mdmon startup
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: Locating slow drives
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Locating slow drives
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Locating slow drives
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: New complete guide for irreversible mdadm failures recovery
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: Raid1 syncing every Sunday morning.
  • From: "Renaud (Ron) OLGIATI" <renaud@xxxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH] md: properly lock and unlock in rdev_attr_store()
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Re: Raid1 syncing every Sunday morning.
  • From: Rudy Zijlstra <rudy@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: Raid1 syncing every Sunday morning.
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Raid1 syncing every Sunday morning.
  • From: "Renaud (Ron) OLGIATI" <renaud@xxxxxxxxxxxxxxxxxxxxxxx>
• New complete guide for irreversible mdadm failures recovery
  • From: Julien ROBIN <julien.robin28@xxxxxxx>
• Working 2 disks RAID0 : failed mdadm --add command : problem at reboot
  • From: Julien ROBIN <julien.robin28@xxxxxxx>