Linux RAID Storage Date Index

• Thread Index

• 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>
• Re: best way to replace all disks
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: RAID5 mdadm --grow wrote nothing (Reshape Status : 0% complete) and cannot assemble anymore
  • From: Julien ROBIN <julien.robin28@xxxxxxx>
• Re: WARNING: CPU: 13 PID: 3786 at drivers/md/raid5.c:4611 break_stripe_batch_list+0x86/0x1fb
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• WARNING: CPU: 13 PID: 3786 at drivers/md/raid5.c:4611 break_stripe_batch_list+0x86/0x1fb
  • From: Marc Smith <msmith626@xxxxxxxxx>
• Re: [RFC] [PATCH V2 0/1] Introduce emergency raid0 stop for mounted arrays
  • From: "Guilherme G. Piccoli" <kernel@xxxxxxxxxxxx>
• Re: RAID5 mdadm --grow wrote nothing (Reshape Status : 0% complete) and cannot assemble anymore
  • From: Julien ROBIN <julien.robin28@xxxxxxx>
• Re: [RFC] [PATCH V2 0/1] Introduce emergency raid0 stop for mounted arrays
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: RAID5 mdadm --grow wrote nothing (Reshape Status : 0% complete) and cannot assemble anymore
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: RAID5 mdadm --grow wrote nothing (Reshape Status : 0% complete) and cannot assemble anymore
  • From: Julien ROBIN <julien.robin28@xxxxxxx>
• Re: RAID5 mdadm --grow wrote nothing (Reshape Status : 0% complete) and cannot assemble anymore
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [RFC] [PATCH V2 0/1] Introduce emergency raid0 stop for mounted arrays
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH 2/2] md/raid0: Do not bypass blocking queue entered for raid0 bios
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [PATCH 1/2] block: Fix a NULL pointer dereference in generic_make_request()
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: RAID5 mdadm --grow wrote nothing (Reshape Status : 0% complete) and cannot assemble anymore
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: RAID5 mdadm --grow wrote nothing (Reshape Status : 0% complete) and cannot assemble anymore
  • From: Julien ROBIN <julien.robin28@xxxxxxx>
• Re: RAID5 mdadm --grow wrote nothing (Reshape Status : 0% complete) and cannot assemble anymore
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: RAID5 mdadm --grow wrote nothing (Reshape Status : 0% complete) and cannot assemble anymore
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: RAID5 mdadm --grow wrote nothing (Reshape Status : 0% complete) and cannot assemble anymore
  • From: Julien ROBIN <julien.robin28@xxxxxxx>
• RAID5 mdadm --grow wrote nothing (Reshape Status : 0% complete) and cannot assemble anymore
  • From: Julien ROBIN <julien.robin28@xxxxxxx>
• Re: [PATCH] md: properly lock and unlock in rdev_attr_store()
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] md: properly lock and unlock in rdev_attr_store()
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [PATCH] md: properly lock and unlock in rdev_attr_store()
  • From: Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx>
• Re: lost software raid information
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: best way to replace all disks
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: Unexpected difference between a 4-disk RAID5 and a 3-disk RAID5 reshaped into a 4-disk RAID5
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Unexpected difference between a 4-disk RAID5 and a 3-disk RAID5 reshaped into a 4-disk RAID5
  • From: pg@xxxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Unexpected difference between a 4-disk RAID5 and a 3-disk RAID5 reshaped into a 4-disk RAID5
  • From: David Shaw <dshaw@xxxxxxxxxxxxxxx>
• Re: lost software raid information
  • From: Volker Lieder <v.lieder@xxxxxxxxxx>
• Re: lost software raid information
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: lost software raid information
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: lost software raid information
  • From: Volker Lieder <v.lieder@xxxxxxxxxx>
• Re: lost software raid information
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• lost software raid information
  • From: Volker Lieder <v.lieder@xxxxxxxxxx>
• Re: [PATCH] Assemble: print error message if mdadm fails assembling with --uuid option
  • From: Jinpu Wang <jinpu.wang@xxxxxxxxxxxxxxx>
• Re: best way to replace all disks
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• Re: best way to replace all disks
  • From: pg@xxxxxxxxxxxxxxxxxxxxxx (Peter Grandi)
• Re: best way to replace all disks
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: [GIT PULL] md-next 2019-04-19
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: best way to replace all disks
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• Re: best way to replace all disks
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• Re: best way to replace all disks
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: best way to replace all disks
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: best way to replace all disks
  • From: Feng Zhang <prod.feng@xxxxxxxxx>
• Re: best way to replace all disks
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: best way to replace all disks
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• Re: best way to replace all disks
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• Re: best way to replace all disks
  • From: Carsten Aulbert <carsten.aulbert@xxxxxxxxxx>
• Re: best way to replace all disks
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• best way to replace all disks
  • From: Gandalf Corvotempesta <gandalf.corvotempesta@xxxxxxxxx>
• [GIT PULL] md-next 2019-04-19
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [RFC] [PATCH V2 0/1] Introduce emergency raid0 stop for mounted arrays
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [RFC] [PATCH V2 1/1] md/raid0: Introduce emergency stop for raid0 arrays
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• [RFC] [PATCH V2 0/1] Introduce emergency raid0 stop for mounted arrays
  • From: "Guilherme G. Piccoli" <gpiccoli@xxxxxxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [PATCH] Assemble: print error message if mdadm fails assembling with --uuid option
  • From: Gioh Kim <gi-oh.kim@xxxxxxxxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] udev: Add udev rules to create by-partuuid for md device
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• "echo frozen > /sys/block/md0/md/sync_action" locks up an array entirely
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Replacing a member disk in RAID0
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Replacing a member disk in RAID0
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Replacing a member disk in RAID0
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Replacing a member disk in RAID0
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: Replacing a member disk in RAID0
  • From: Guoqing Jiang <gqjiang@xxxxxxx>
• Replacing a member disk in RAID0
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• Re: [PATCH] udev: Add udev rules to create by-partuuid for md device
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] udev: Add udev rules to create by-partuuid for md device
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: reduce number of devices in raid6
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/1] md: return -ENODEV if rdev has no mddev assigned
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 1/1] md: return -ENODEV if rdev has no mddev assigned
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: reduce number of devices in raid6
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: reduce number of devices in raid6
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/1] md: return -ENODEV if rdev has no mddev assigned
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 1/1] md: return -ENODEV if rdev has no mddev assigned
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: reduce number of devices in raid6
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: reduce number of devices in raid6
  • From: Andreas Klauer <Andreas.Klauer@xxxxxxxxxxxxxx>
• Re: Degraded RAID-6 array reassembling as a RAID-0 array
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Degraded RAID-6 array reassembling as a RAID-0 array
  • From: Mark Wagner <carnildo@xxxxxxxxx>
• Re: [PATCH] md/raid0: don't use line[200] to store zone info
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: Degraded RAID-6 array reassembling as a RAID-0 array
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [HELP] md/raid5: do we really avoid reading from known bad blocks ?
  • From: "jianchao.wang" <jianchao.w.wang@xxxxxxxxxx>
• Re: [GIT PULL] md fixes/changes for 5.2
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [GIT PULL] md fixes/changes for 5.2
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 1/1] md: return -ENODEV if rdev has no mddev assigned
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [HELP] md/raid5: do we really avoid reading from known bad blocks ?
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] md/raid0: don't use line[200] to store zone info
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Degraded RAID-6 array reassembling as a RAID-0 array
  • From: Mark Wagner <carnildo@xxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH] Create: Block rounding size to max
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 1/1] imsm: fix spare activation for old matrix arrays
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 1/1] md: return -ENODEV if rdev has no mddev assigned
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: [PATCH 1/1] imsm: fix spare activation for old matrix arrays
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH] md/raid0: don't use line[200] to store zone info
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• reduce number of devices in raid6
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: Re[20]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: [HELP] md/raid5: do we really avoid reading from known bad blocks ?
  • From: "jianchao.wang" <jianchao.w.wang@xxxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: John Stoffel <john@xxxxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [HELP] md/raid5: do we really avoid reading from known bad blocks ?
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [HELP] md/raid5: do we really avoid reading from known bad blocks ?
  • From: "jianchao.wang" <jianchao.w.wang@xxxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: One more newbee question:
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• One more newbee question:
  • From: "Renaud (Ron) OLGIATI" <renaud@xxxxxxxxxxxxxxxxxxxxxxx>
• Re: OT: Processor recommendation
  • From: Paul Menzel <pmenzel@xxxxxxxxxxxxx>
• Re: OT: Processor recommendation
  • From: Leslie Rhorer <lrhorer@xxxxxxxxxxxx>
• OT: Processor recommendation
  • From: Paul Menzel <pmenzel@xxxxxxxxxxxxx>
• Re: [PATCH 1/7] md: add a missing endianess conversion in check_sb_changes
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH 5/7] md: mark md_cluster_mod static
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: a bunch of MD raid fixes
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• seagate ST12000NM0007 disk issue
  • From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
• Re: Re[18]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Re[18]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re[18]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: no_spam@xxxxxxxxxxxx
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: Re[16]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• [PATCH 7/7] md: add __acquires/__releases annotations to handle_active_stripes
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 6/7] md: add __acquires/__releases annotations to (un)lock_two_stripes
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 5/7] md: mark md_cluster_mod static
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 4/7] md: use correct type in super_1_sync
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 3/7] md: use correct type in super_1_load
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 2/7] md: use correct types in md_bitmap_print_sb
  • From: Christoph Hellwig <hch@xxxxxx>
• [PATCH 1/7] md: add a missing endianess conversion in check_sb_changes
  • From: Christoph Hellwig <hch@xxxxxx>
• a bunch of MD raid fixes
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re[16]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: no_spam@xxxxxxxxxxxx
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Dan Williams <dan.j.williams@xxxxxxxxx>
• Re: [PATCH v2] md: add mddev->pers to avoid potential NULL pointer dereference
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH v2] md: add mddev->pers to avoid potential NULL pointer dereference
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH v2] md: add mddev->pers to avoid potential NULL pointer dereference
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• Re: [PATCH] md: add mddev->pers to avoid potential NULL pointer dereference
  • From: yuyufen <yuyufen@xxxxxxxxxx>
• Re: [PATCH] md: add mddev->pers to avoid potential NULL pointer dereference
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH] md: add mddev->pers to avoid potential NULL pointer dereference
  • From: Yufen Yu <yuyufen@xxxxxxxxxx>
• [PATCH] Create: Block rounding size to max
  • From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxx>
• Re: Help needed: RAID5 with two apparent simo drive failures
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: Help needed: RAID5 with two apparent simo drive failures
  • From: "Jorge R. Frank" <jrfrank@xxxxxxxxxx>
• Re: Help needed: RAID5 with two apparent simo drive failures
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Help needed: RAID5 with two apparent simo drive failures
  • From: "Jorge R. Frank" <jrfrank@xxxxxxxxxx>
• Re: Question about Intel RST, NVMe SSDs and mdadm
  • From: Raphaël Halimi <raphael.halimi@xxxxxxxxx>
• Re: [PATCH 1/3] Don't jump to compute_result state from check_result state
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH 0/3] md fixes and improvements
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH 1/3] Don't jump to compute_result state from check_result state
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH 2/3] Revert "MD: fix lock contention for flush bios"
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 3/3] md: batch flush requests.
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 1/3] Don't jump to compute_result state from check_result state
  • From: Song Liu <songliubraving@xxxxxx>
• [PATCH 0/3] md fixes and improvements
  • From: Song Liu <songliubraving@xxxxxx>
• Re: Question about Intel RST, NVMe SSDs and mdadm
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: [PATCH 0/2] md: change approach to parallel flush requests.
  • From: NeilBrown <neilb@xxxxxxxx>
• Question about Intel RST, NVMe SSDs and mdadm
  • From: Raphaël Halimi <raphael.halimi@xxxxxxxxx>
• Re: [PATCH 0/2] md: change approach to parallel flush requests.
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 0/2] md: change approach to parallel flush requests.
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH 0/2] md: change approach to parallel flush requests.
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: [PATCH 0/2] md: change approach to parallel flush requests.
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH 1/1] md: return -ENODEV if rdev has no mddev assigned
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: [PATCH 0/2] md: change approach to parallel flush requests.
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [PATCH 1/2] Revert "MD: fix lock contention for flush bios"
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH 0/2] md: change approach to parallel flush requests.
  • From: NeilBrown <neilb@xxxxxxxx>
• [PATCH 2/2] md: batch flush requests.
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] Don't jump to compute_result state from check_result state
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: Re[14]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• [PATCH] Don't jump to compute_result state from check_result state
  • From: Nigel Croxon <ncroxon@xxxxxxxxxx>
• Re: [PATCH] udev: Add udev rules to create by-partuuid for md device
  • From: NeilBrown <neilb@xxxxxxxx>
• Re[14]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: no_spam@xxxxxxxxxxxx
• Re: [PATCH] udev: Add udev rules to create by-partuuid for md device
  • From: Liwei Song <liwei.song@xxxxxxxxxxxxx>
• Re: [PATCH] udev: Add udev rules to create by-partuuid for md device
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH RFC] md/raid1: fix deadlock between freeze_array() and wait_barrier().
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: [PATCH] md:MD_CLOSING needs to be cleared after called md_set_readonly or do_md_stop
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• [PATCH] udev: Add udev rules to create by-partuuid for md device
  • From: Liwei Song <liwei.song@xxxxxxxxxxxxx>
• Re: [PATCH] md:MD_CLOSING needs to be cleared after called md_set_readonly or do_md_stop
  • From: NeilBrown <neilb@xxxxxxxx>
• Re: [PATCH] md:MD_CLOSING needs to be cleared after called md_set_readonly or do_md_stop
  • From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
• Re: 4tb NAS drive recommendation
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Re: [GIT PULL] md changes for 5.1
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: troubleshooting RAID-1 array break+resync on boot after upgrades to linux kernel v5.0.x ?
  • From: PGNet Dev <pgnet.dev@xxxxxxxxx>
• Re: troubleshooting RAID-1 array break+resync on boot after upgrades to linux kernel v5.0.x ?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• troubleshooting RAID-1 array break+resync on boot after upgrades to linux kernel v5.0.x ?
  • From: PGNet Dev <pgnet.dev@xxxxxxxxx>
• Re: 4tb NAS drive recommendation
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: 4tb NAS drive recommendation
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• [GIT PULL] md changes for 5.1
  • From: Song Liu <songliubraving@xxxxxx>
• Re: [PATCH] md: Fix failed allocation of md_register_thread
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH 1/1] It's wrong to add len to sector_nr in raid10 reshape twice
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [PATCH v2] raid5: set write hint for PPL
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] raid5: set write hint for PPL
  • From: "Dabrowski, Mariusz" <mariusz.dabrowski@xxxxxxxxx>
• Re: 4tb NAS drive recommendation
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: 4tb NAS drive recommendation
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: 4tb NAS drive recommendation
  • From: "John Stoffel" <john@xxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Kai Stian Olstad <raid+list@xxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Phil Turmel <philip@xxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Nix <nix@xxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
• Re: Re[13]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: "Wol's lists" <antlists@xxxxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Andy Smith <andy@xxxxxxxxxxxxxx>
• Re[13]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: no_spam@xxxxxxxxxxxx
• Re: smart short test crashes software raid array?
  • From: Leslie Rhorer <lrhorer@xxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Reindl Harald <h.reindl@xxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Re[11]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Leslie Rhorer <lrhorer@xxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Kent Dorfman <kent.dorfman766@xxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Leslie Rhorer <lrhorer@xxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Leslie Rhorer <lrhorer@xxxxxxxxxxxx>
• Re: Raid 5 painfully slow with linux 5.0.0
  • From: Michael Leun <linux-raid-20190308@xxxxxxxxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Kent Dorfman <kent.dorfman766@xxxxxxxxx>
• Re: smart short test crashes software raid array?
  • From: Roman Mamedov <rm@xxxxxxxxxxx>
• smart short test crashes software raid array?
  • From: Kent Dorfman <kent.dorfman766@xxxxxxxxx>
• Re[11]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: no_spam@xxxxxxxxxxxx
• Re: Re[9]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Re[9]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Re[8]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Re[8]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Raid 5 painfully slow with linux 5.0.0
  • From: linux-raid-20190308@xxxxxxxxxxxxxxx
• [PATCH 1/1] It's wrong to add len to sector_nr in raid10 reshape twice
  • From: Xiao Ni <xni@xxxxxxxxxx>
• [PATCH 1/1] imsm: fix spare activation for old matrix arrays
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: [PATCH v2] raid5: set write hint for PPL
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re[9]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: no_spam@xxxxxxxxxxxx
• Re[8]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: no_spam@xxxxxxxxxxxx
• Re: Re[6]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re[6]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: no_spam@xxxxxxxxxxxx
• Re: [PATCH] md: Fix failed allocation of md_register_thread
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: [PATCH v2] raid5: set write hint for PPL
  • From: Guoqing Jiang <gqjiang@xxxxxxxx>
• Re: Re[4]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Re[4]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: [PATCH v2] raid5: set write hint for PPL
  • From: Song Liu <songliubraving@xxxxxx>
• Re[2]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: no_spam@xxxxxxxxxxxx
• Re: [PATCH v2] raid5: set write hint for PPL
  • From: "Dabrowski, Mariusz" <mariusz.dabrowski@xxxxxxxxx>
• Re: Re[2]: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Linux Raid + BTRFS: rookie mistake ... dd bs=1M
  • From: zittware@xxxxxxxxxxxxxxxxxxxxxxx
• Re: [PATCH] md: Fix failed allocation of md_register_thread
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• [PATCH] md: Fix failed allocation of md_register_thread
  • From: Aditya Pakki <pakki001@xxxxxxx>
• Re: [PATCH] add missing units to --examine
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: Raid5 four drives missing
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: [PATCH] add missing units to --examine
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH 1/1] Assemble: Fix starting array with initial reshape checkpoint
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH V2] mdmon: wait for previous mdmon to exit during takeover
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: [PATCH] mdmon: don't attempt to manage new arrays when terminating
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• Re: mdadm RAID10 configuration - performance
  • From: keld@xxxxxxxxxx
• Re: [PATCH V15 14/18] block: enable multipage bvecs
  • From: Jon Hunter <jonathanh@xxxxxxxxxx>
• Re: [PATCH V15 14/18] block: enable multipage bvecs
  • From: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
• Re: [PATCH V15 14/18] block: enable multipage bvecs
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [PATCH V15 14/18] block: enable multipage bvecs
  • From: Jon Hunter <jonathanh@xxxxxxxxxx>
• Re: Raid5 reshape stuck - md0 process hang
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Raid5 reshape stuck - md0 process hang
  • From: Brian <search@xxxxxxxxxxxxxx>
• Re: Raid5 reshape stuck - md0 process hang
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: Raid5 reshape stuck - md0 process hang
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: raid5 reshape is stuck when raid5 journal device miss
  • From: Xiao Ni <xni@xxxxxxxxxx>
• Re: raid5 reshape is stuck when raid5 journal device miss
  • From: Xiao Ni <xni@xxxxxxxxxx>
• mdadm RAID10 configuration - performance
  • From: Guillermo F <guillefraz@xxxxxxxxx>
• Re: Raid5 reshape stuck - md0 process hang
  • From: "search@xxxxxxxxxxxxxx" <search@xxxxxxxxxxxxxx>
• Raid5 reshape stuck - md0 process hang
  • From: "search@xxxxxxxxxxxxxx" <search@xxxxxxxxxxxxxx>
• Raid5 stuck at reshape - md0 process hangs
  • From: "search@xxxxxxxxxxxxxx" <search@xxxxxxxxxxxxxx>
• Re: AW: [PATCH] lib/raid6: possibly use different gen and xor algorithms.,
  • From: Hristo Venev <hristo@xxxxxxxxxx>
• AW: [PATCH] lib/raid6: possibly use different gen and xor algorithms.,
  • From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
• [PATCH] lib/raid6: possibly use different gen and xor algorithms.,
  • From: Hristo Venev <hristo@xxxxxxxxxx>
• Re: Raid5 four drives missing
  • From: Romulo Albuquerque <romulo.albuquerque@xxxxxxxxx>
• [PATCH V2] mdmon: wait for previous mdmon to exit during takeover
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH 1/1] Assemble: Fix starting array with initial reshape checkpoint
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• [PATCH] mdmon: don't attempt to manage new arrays when terminating
  • From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
• Re: [PATCH V15 14/18] block: enable multipage bvecs
  • From: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
• Re: [PATCH V15 14/18] block: enable multipage bvecs
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [PATCH V15 14/18] block: enable multipage bvecs
  • From: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
• Re: [PATCH V15 14/18] block: enable multipage bvecs
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [PATCH V15 14/18] block: enable multipage bvecs
  • From: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
• Re: [PATCH V15 14/18] block: enable multipage bvecs
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [PATCH V15 14/18] block: enable multipage bvecs
  • From: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
• RE: RAID6 : Sequential Write Performance
  • From: Jean De Gyns <Jean.DeGyns@xxxxxxxxxx>
• Re: [dm-devel] [PATCH V15 00/18] block: support multi-page bvec
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [dm-devel] [PATCH V15 00/18] block: support multi-page bvec
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: RAID6 : Sequential Write Performance
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: RAID6 : Sequential Write Performance
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: RAID6 : Sequential Write Performance
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: RAID6 : Sequential Write Performance
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: raid1 out of sync, but which files are affected?
  • From: "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>
• Re: Raid5 four drives missing
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: RAID6 : Sequential Write Performance
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• RE: RAID6 : Sequential Write Performance
  • From: Jean De Gyns <Jean.DeGyns@xxxxxxxxxx>
• Re: [PATCH 1/1] mdmon: wait for previous mdmon to exit during takeover
  • From: Jes Sorensen <jes.sorensen@xxxxxxxxx>
• RE: RAID6 : Sequential Write Performance
  • From: Jean De Gyns <Jean.DeGyns@xxxxxxxxxx>
• Re: [dm-devel] [PATCH V15 00/18] block: support multi-page bvec
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: Raid5 four drives missing
  • From: Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx>
• Re: [PATCH 1/1] mdmon: wait for previous mdmon to exit during takeover
  • From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
• Re: Raid5 four drives missing
  • From: Mikael Abrahamsson <swmike@xxxxxxxxx>
• Raid5 four drives missing
  • From: Romulo Albuquerque <romulo.albuquerque@xxxxxxxxx>
• [PATCH v2] raid5: set write hint for PPL
  • From: Mariusz Dabrowski <mariusz.dabrowski@xxxxxxxxx>
• Re: [dm-devel] [PATCH V15 00/18] block: support multi-page bvec
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [dm-devel] [PATCH V15 00/18] block: support multi-page bvec
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [dm-devel] [PATCH V15 00/18] block: support multi-page bvec
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: [PATCH V15 00/18] block: support multi-page bvec
  • From: Ming Lei <ming.lei@xxxxxxxxxx>
• Re: RAID6 : Sequential Write Performance
  • From: Roger Heflin <rogerheflin@xxxxxxxxx>
• Re: [PATCH] add missing units to --examine
  • From: Corey Hickey <bugfood-ml@xxxxxxxxxx>
• Re: RAID6 : Sequential Write Performance
  • From: Song Liu <liu.song.a23@xxxxxxxxx>
• Re: [dm-devel] [PATCH V15 00/18] block: support multi-page bvec
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [dm-devel] [PATCH V15 00/18] block: support multi-page bvec
  • From: Bart Van Assche <bvanassche@xxxxxxx>
• Re: [PATCH V15 00/18] block: support multi-page bvec
  • From: Jens Axboe <axboe@xxxxxxxxx>