Linux RAID Storage Date Index

Thread Index

Re: [PATCH 1/3] PM suspend/hibernate: Call notifier after freezing processes
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Shaohua Li <shli@xxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Pali Rohár <pali.rohar@xxxxxxxxx>
Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Pali Rohár <pali.rohar@xxxxxxxxx>
Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Pali Rohár <pali.rohar@xxxxxxxxx>
Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 1/3] PM suspend/hibernate: Call notifier after freezing processes
- From: Pali Rohár <pali.rohar@xxxxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Shaohua Li <shli@xxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/2][v2] blk-plug: don't flush nested plug lists
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Shaohua Li <shli@xxxxxx>
Re: [PATCH 1/3] PM suspend/hibernate: Call notifier after freezing processes
- From: "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>
Re: [PATCH 4/4] md-cluster: re-add
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 3/4] re-add a failed disk
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/4] md-cluster: remove capabilities
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] IMSM: Count arrays per orom
- From: NeilBrown <neilb@xxxxxxx>
[PATCH 4/4] md-cluster: re-add
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
[PATCH 3/4] re-add a failed disk
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
[PATCH 2/4] md-cluster: remove capabilities
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
[PATCH 1/4] md-cluster: fix bitmap sub-offset in bitmap_read_sb
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
Re: Help recovering an interrupted raid0 reshape
- From: "Jonathan Harker (Jesusaurus)" <jesusaurus@xxxxxxxxxxxxxxxxx>
[PATCH] IMSM: Count arrays per orom
- From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
Re: [PATCH] md: fix md io stats accounting broken
- From: NeilBrown <neilb@xxxxxxx>
Re: Help recovering an interrupted raid0 reshape
- From: NeilBrown <neilb@xxxxxxx>
Re: Help recovering an interrupted raid0 reshape
- From: "Jonathan Harker (Jesusaurus)" <jesusaurus@xxxxxxxxxxxxxxxxx>
Re: Help recovering an interrupted raid0 reshape
- From: NeilBrown <neilb@xxxxxxx>
Re: Help recovering an interrupted raid0 reshape
- From: "Jonathan Harker (Jesusaurus)" <jesusaurus@xxxxxxxxxxxxxxxxx>
Re: Creating volume in IMSM container
- From: NeilBrown <neilb@xxxxxxx>
Re: Help recovering an interrupted raid0 reshape
- From: NeilBrown <neilb@xxxxxxx>
Re: Help recovering an interrupted raid0 reshape
- From: "Jonathan Harker (Jesusaurus)" <jesusaurus@xxxxxxxxxxxxxxxxx>
Creating volume in IMSM container
- From: Ian Pilcher <arequipeno@xxxxxxxxx>
Re: [dm-devel] [PATCH 3/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: Help recovering an interrupted raid0 reshape
- From: NeilBrown <neilb@xxxxxxx>
Re: Help recovering an interrupted raid0 reshape
- From: "Jonathan Harker (Jesusaurus)" <jesusaurus@xxxxxxxxxxxxxxxxx>
Re: multi-threaded raid5
- From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
Re: Can't mount partitions after "mdadm --zero-superblock"
- From: Eduard Rozenberg <eduardr@xxxxxxxxx>
Re: Can't mount partitions after "mdadm --zero-superblock"
- From: NeilBrown <neilb@xxxxxxx>
Re: Help recovering an interrupted raid0 reshape
- From: NeilBrown <neilb@xxxxxxx>
Re: Can't mount partitions after "mdadm --zero-superblock"
- From: Eduard Rozenberg <eduardr@xxxxxxxxx>
Re: write barrier in RAID5
- From: NeilBrown <neilb@xxxxxxx>
Re: openSUSE 13.2: md - Need advice which raid1 super format (1.0/1.2) is preferred
- From: NeilBrown <neilb@xxxxxxx>
Re: multi-threaded raid5
- From: NeilBrown <neilb@xxxxxxx>
Re: Can't mount partitions after "mdadm --zero-superblock"
- From: NeilBrown <neilb@xxxxxxx>
Can't mount partitions after "mdadm --zero-superblock"
- From: Eduard Rozenberg <eduardr@xxxxxxxxx>
Re: Help recovering an interrupted raid0 reshape
- From: NeilBrown <neilb@xxxxxxx>
Re: Recovery of RAID 6 after three rapid disk events (disks are still working)
- From: NeilBrown <neilb@xxxxxxx>
Recovery of RAID 6 after three rapid disk events (disks are still working)
- From: Mike <mboulter@xxxxxxxxx>
Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Pali Rohár <pali.rohar@xxxxxxxxx>
Why wipe crypto keys during suspend (was Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation)
- From: Pavel Machek <pavel@xxxxxx>
Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: Two system lockups, Magic SysKeys works, RAID6 resyncs on reboot
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Pavel Machek <pavel@xxxxxx>
Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Pali Rohár <pali.rohar@xxxxxxxxx>
Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Pavel Machek <pavel@xxxxxx>
Re: [PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH 2/3] dm: Export function dm_suspend_md()
- From: Pali Rohár <pali.rohar@xxxxxxxxx>
[PATCH 3/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Pali Rohár <pali.rohar@xxxxxxxxx>
[PATCH 1/3] PM suspend/hibernate: Call notifier after freezing processes
- From: Pali Rohár <pali.rohar@xxxxxxxxx>
[PATCH 0/3] dm-crypt: Adds support for wiping key when doing suspend/hibernation
- From: Pali Rohár <pali.rohar@xxxxxxxxx>
Help recovering an interrupted raid0 reshape
- From: "Jonathan Harker (Jesusaurus)" <jesusaurus@xxxxxxxxxxxxxxxxx>
Re: Breaks LSI RAID on C600 chipset
- From: "John Stoffel" <john@xxxxxxxxxxx>
Breaks LSI RAID on C600 chipset
- From: "David F." <df7729@xxxxxxxxx>
[PATCH] md: fix md io stats accounting broken
- From: Gu Zheng <guz.fnst@xxxxxxxxxxxxxx>
Re: [neilb@xxxxxxx: Re: MD request counter broken on 4.0-rc5 RAID1]
- From: Simon Kirby <sim@xxxxxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Shaohua Li <shli@xxxxxx>
Re: /dev/md0 can't be created
- From: Xiao Ni <xni@xxxxxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Shaohua Li <shli@xxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Jens Axboe <axboe@xxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: "Jiang, Dave" <dave.jiang@xxxxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Alireza Haghdoost <alireza@xxxxxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
Re: Two system lockups, Magic SysKeys works, RAID6 resyncs on reboot
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Alireza Haghdoost <alireza@xxxxxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
write barrier in RAID5
- From: Eric Mei <meijia@xxxxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Shaohua Li <shli@xxxxxx>
Re: [PATCH] Fix bitmap offset calculations
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
Re: [PATCH] Fix bitmap offset calculations
- From: Alireza Haghdoost <alireza@xxxxxxxxxx>
Re: [neilb@xxxxxxx: Re: MD request counter broken on 4.0-rc5 RAID1]
- From: NeilBrown <neilb@xxxxxxx>
Re: [neilb@xxxxxxx: Re: MD request counter broken on 4.0-rc5 RAID1]
- From: Gu Zheng <guz.fnst@xxxxxxxxxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Shaohua Li <shli@xxxxxx>
Re: [RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: /dev/md0 can't be created
- From: NeilBrown <neilb@xxxxxxx>
openSUSE 13.2: md - Need advice which raid1 super format (1.0/1.2) is preferred
- From: Dieter Nützel <Dieter@xxxxxxxxxxxxx>
Re: no good deed goes unpunished...
- From: Dave Stevens <geek@xxxxxxxxxxxx>
Re: Two system lockups, Magic SysKeys works, RAID6 resyncs on reboot
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: no good deed goes unpunished...
- From: Dave Stevens <geek@xxxxxxxxxxxx>
Re: no good deed goes unpunished...
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: no good deed goes unpunished...
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: no good deed goes unpunished...
- From: Dave Stevens <geek@xxxxxxxxxxxx>
Re: Two system lockups, Magic SysKeys works, RAID6 resyncs on reboot
- From: Roman Mamedov <rm@xxxxxxxxxxx>
multi-threaded raid5
- From: stkoupr <p.kouril@xxxxxx>
Two system lockups, Magic SysKeys works, RAID6 resyncs on reboot
- From: Mark Knecht <markknecht@xxxxxxxxx>
[RFC] raid5: add a log device to fix raid5/6 write hole issue
- From: Shaohua Li <shli@xxxxxx>
[PATCH 2/7] dm_table: Use bool function return values of true/false not 1/0
- From: Joe Perches <joe@xxxxxxxxxxx>
Re: [PATCH 2/7] dm_table: Use bool function return values of true/false not 1/0
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
[PATCH 0/7] drivers: Use bool function return values true/false not 1/0
- From: Joe Perches <joe@xxxxxxxxxxx>
Re: mdadm RAID6 "active" with spares and failed disks; need help
- From: Phil Turmel <philip@xxxxxxxxxx>
Read-only mounts (was mdadm RAID6 "active" with spares and failed disks; need help)
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: mdadm RAID6 "active" with spares and failed disks; need help
- From: Roman Mamedov <rm@xxxxxxxxxxx>
Re: no good deed goes unpunished...
- From: Dave Stevens <geek@xxxxxxxxxxxx>
Re: mdadm RAID6 "active" with spares and failed disks; need help
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: no good deed goes unpunished...
- From: Brad Campbell <brad@xxxxxxxxxxxxxxx>
Re: no good deed goes unpunished...
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: no good deed goes unpunished...
- From: Dave Stevens <geek@xxxxxxxxxxxx>
Re: mdadm RAID6 "active" with spares and failed disks; need help
- From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
Re: no good deed goes unpunished...
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
re: no good deed goes unpunished...
- From: Dave Stevens <geek@xxxxxxxxxxxx>
Re: missing arrays after OS upgrade
- From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
Re: /dev/md0 can't be created
- From: Xiao Ni <xni@xxxxxxxxxx>
Re: no good deed goes unpunished...
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
no good deed goes unpunished...
- From: Dave Stevens <geek@xxxxxxxxxxxx>
Re: /dev/md0 can't be created
- From: Xiao Ni <xni@xxxxxxxxxx>
Re: Badblocks and degraded array.
- From: NeilBrown <neilb@xxxxxxx>
Badblocks and degraded array.
- From: Wakko Warner <wakko@xxxxxxxxxxxx>
[PATCH] Fix minor typo in mdadm manpage.
- From: Andrew Burgess <andrew.burgess@xxxxxxxxxxxx>
Re: RAID6 won't reassemble after disk controller failure
- From: Scott Sinno <sinno@xxxxxxxxx>
Re: RAID6 won't reassemble after disk controller failure
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: RAID6 won't reassemble after disk controller failure
- From: Scott Sinno <sinno@xxxxxxxxx>
Re: RAID6 won't reassemble after disk controller failure
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: RAID6 won't reassemble after disk controller failure
- From: Scott Sinno <sinno@xxxxxxxxx>
Re: RAID6 won't reassemble after disk controller failure
- From: Scott Sinno <sinno@xxxxxxxxx>
Re: RAID6 won't reassemble after disk controller failure
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
RAID6 won't reassemble after disk controller failure
- From: Scott Sinno <sinno@xxxxxxxxx>
Re: missing arrays after OS upgrade
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: missing arrays after OS upgrade
- From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
Re: /dev/md0 can't be created
- From: NeilBrown <neilb@xxxxxxx>
/dev/md0 can't be created
- From: Xiao Ni <xni@xxxxxxxxxx>
Re: [PATCH] Fix bitmap offset calculations
- From: NeilBrown <neilb@xxxxxxx>
Re: MD request counter broken on 4.0-rc5 RAID1
- From: NeilBrown <neilb@xxxxxxx>
MD request counter broken on 4.0-rc5 RAID1
- From: Simon Kirby <sim@xxxxxxxxxx>
Re: missing arrays after OS upgrade
- From: Phil Turmel <philip@xxxxxxxxxx>
missing arrays after OS upgrade
- From: Daniel Sanabria <sanabria.d@xxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Rik van Riel <riel@xxxxxxxxxx>
Monitor new badblocks
- From: Serge Bartosh <sb@xxxxxxxxxx>
[PATCH] Fix bitmap offset calculations
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
Re: [PATCH 1/1] Make bm_blocks to match previous semantic
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
resize a 'far' RAID10 ?
- From: Wolfgang Denk <wd@xxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
Re: is mdadm RAID1 disk full sync
- From: lingli tang <tanglingli001@xxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Rik van Riel <riel@xxxxxxxxxx>
Re: is mdadm RAID1 disk full sync
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
Thanks for the awesome
- From: Phil Ingram <pingram.au@xxxxxxxxx>
Re: is mdadm RAID1 disk full sync
- From: lingli tang <tanglingli001@xxxxxxxxx>
Re: Hung RAID5 array with discard
- From: NeilBrown <neilb@xxxxxxx>
Re: is mdadm RAID1 disk full sync
- From: NeilBrown <neilb@xxxxxxx>
[GIT PULL REQUEST] one bugfix for md in 4.0-rc
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
Re: is mdadm RAID1 disk full sync
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
Re: is mdadm RAID1 disk full sync
- From: lingli tang <tanglingli001@xxxxxxxxx>
Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
Re: is mdadm RAID1 disk full sync
- From: lingli tang <tanglingli001@xxxxxxxxx>
Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
Re: is mdadm RAID1 disk full sync
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
Re: is mdadm RAID1 disk full sync
- From: NeilBrown <neilb@xxxxxxx>
Re: is mdadm RAID1 disk full sync
- From: lingli tang <tanglingli001@xxxxxxxxx>
Re: is mdadm RAID1 disk full sync
- From: NeilBrown <neilb@xxxxxxx>
is mdadm RAID1 disk full sync
- From: lingli tang <tanglingli001@xxxxxxxxx>
Why people recommend to disable NCQ for MD RAID ?
- From: Alireza Haghdoost <alireza@xxxxxxxxxx>
Re: [PATCH 1/1] Make bm_blocks to match previous semantic
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Rik van Riel <riel@xxxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Matthew Wilcox <willy@xxxxxxxxxxxxxxx>
Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Rik van Riel <riel@xxxxxxxxxx>
Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Rik van Riel <riel@xxxxxxxxxx>
Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Re: [PATCH] md/raid5: don't do chunk aligned read on degraded array.
- From: Eric Mei <meijia@xxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Matthew Wilcox <willy@xxxxxxxxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Matthew Wilcox <willy@xxxxxxxxxxxxxxx>
Re: [PATCH] md/raid5: don't do chunk aligned read on degraded array.
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] md/raid5: don't do chunk aligned read on degraded array.
- From: Eric Mei <meijia@xxxxxxxxx>
Re: [PATCH 1/1] Make bm_blocks to match previous semantic
- From: Guoqing Jiang <GQJiang@xxxxxxxx>
Re: Converting a .90 raid superblock to version 1.0 and whether--size parameter is needed
- From: NeilBrown <neilb@xxxxxxx>
Re: Converting a .90 raid superblock to version 1.0 and whether--size parameter is needed
- From: Sean Harris <sean@xxxxxxxxxxxxx>
Re: dm log userspace: use mempool_create_kmalloc_pool()
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [Linux-nvdimm] [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Matthew Wilcox <willy@xxxxxxxxxxxxxxx>
Re: [Linux-nvdimm] [RFC PATCH 3/7] dma-mapping: allow archs to optionally specify a ->map_pfn() operation
- From: Boaz Harrosh <boaz@xxxxxxxxxxxxx>
Re: [RFC PATCH 0/7] evacuate struct page from the block layer
- From: Boaz Harrosh <openosd@xxxxxxxxx>
Re: Converting a .90 raid superblock to version 1.0 and whether--size parameter is needed
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/1] Make bm_blocks to match previous semantic
- From: NeilBrown <neilb@xxxxxxx>
Converting a .90 raid superblock to version 1.0 and whether--size parameter is needed
- From: Sean Harris <sean@xxxxxxxxxxxxx>
chunk size K, KB, KiB
- From: Chris Murphy <chris@xxxxxxxxxxxxxxxxx>
Re: [RFC PATCH 2/7] block: convert bio_vec.bv_page to bv_pfn
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [RFC PATCH 2/7] block: convert bio_vec.bv_page to bv_pfn
- From: Matthew Wilcox <willy@xxxxxxxxxxxxxxx>
[PATCH] dm delay: use msecs_to_jiffies for time conversion
- From: Nicholas Mc Guire <hofrat@xxxxxxxxx>
[PATCH 1/1] Make bm_blocks to match previous semantic
- From: jgq516@xxxxxxxxx
Re: [RFC PATCH 2/7] block: convert bio_vec.bv_page to bv_pfn
- From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
[RFC PATCH 0/7] evacuate struct page from the block layer
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 3/7] dma-mapping: allow archs to optionally specify a ->map_pfn() operation
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 1/7] block: add helpers for accessing a bio_vec page
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 4/7] scatterlist: use sg_phys()
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 2/7] block: convert bio_vec.bv_page to bv_pfn
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 6/7] x86: support dma_map_pfn()
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 7/7] block: base support for pfn i/o
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 5/7] scatterlist: support "page-less" (__pfn_t only) entries
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [PATCH] kernfs: handle poll correctly on 'direct_read' files.
- From: Tejun Heo <tj@xxxxxxxxxx>
Bad Block Management in RAID1 and "Faulty"
- From: Ankur Bose <ankur.bose@xxxxxxxxxx>
[PATCH] kernfs: handle poll correctly on 'direct_read' files.
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] dm log userspace: base: fix compile warning
- From: Nicholas Mc Guire <hofrat@xxxxxxxxx>
[PATCH] dm log userspace: transfer: match wait_for_completion_timeout return type
- From: Nicholas Mc Guire <hofrat@xxxxxxxxx>
/dev/md/xxx sporadically unavailable after mdadm --assemble /dev/md/xxx
- From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
Re: Inject I/O latency for RAID5/6 read and writes
- From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Bad block management in raid1
- From: Ankur Bose <ankur.bose@xxxxxxxxxx>
Re: Inject I/O latency for RAID5/6 read and writes
- From: Alireza Haghdoost <alireza@xxxxxxxxxx>
Please kindly read my message
- From: Sandra toyin rain elizabeth <toyinelizabeth803@xxxxxxxxx>
Re: Raid 5: all devices marked spare, cannot assemble
- From: Paul Boven <boven@xxxxxxx>
Re: Raid 5: all devices marked spare, cannot assemble
- From: Phil Turmel <philip@xxxxxxxxxx>
Raid 5: all devices marked spare, cannot assemble
- From: Paul Boven <boven@xxxxxxx>
Re: dm log userspace: use mempool_create_kmalloc_pool()
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
mdraid with device-mapper multipath devices
- From: Sushma Gurram <Sushma.Gurram@xxxxxxxxxxx>
Re: Raid 10 Issue - Swapping Data from Array to Array [SOLVED]
- From: Stefan Lamby <webmaster@xxxxxxxxxxxxxx>
Re: Raid 10 Issue
- From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
Re: two raid issues
- From: Phil Turmel <philip@xxxxxxxxxx>
[patch] dm log userspace: use mempool_create_kmalloc_pool()
- From: David Rientjes <rientjes@xxxxxxxxxx>
two raid issues
- From: Dave Stevens <geek@xxxxxxxxxxxx>
Re: Raid 10 Issue - Booting in case raid failed
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: raid 10 - Recovering raid - what stats are most helpfull?
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: raid 10 - Recovering raid - what stats are most helpfull?
- From: Stefan Lamby <webmaster@xxxxxxxxxxxxxx>
Re: Raid 10 Issue - Booting in case raid failed
- From: Stefan Lamby <webmaster@xxxxxxxxxxxxxx>
Re: Raid 10 Issue - Swapping Data from Array to Array
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Raid 10 Issue - Swapping Data from Array to Array
- From: Stefan Lamby <webmaster@xxxxxxxxxxxxxx>
Re: Raid 10 Issue [SOLVED]
- From: Stefan Lamby <webmaster@xxxxxxxxxxxxxx>
Re: Last working drive in RAID1
- From: Chris <email.bug@xxxxxxxx>
Re: Raid 10 Issue
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: Last working drive in RAID1
- From: Chris <email.bug@xxxxxxxx>
Re: Last working drive in RAID1
- From: NeilBrown <neilb@xxxxxxx>
Re: Last working drive in RAID1
- From: Eric Mei <meijia@xxxxxxxxx>
Re: Raid 10 Issue
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Last working drive in RAID1
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Last working drive in RAID1
- From: Eric Mei <meijia@xxxxxxxxx>
smartctl-timeouts_v1.01 scripts (scterc timeout fixes)
- From: Chris <email.bug@xxxxxxxx>
Raid 10 Issue
- From: Stefan Lamby <webmaster@xxxxxxxxxxxxxx>
Re: Last working drive in RAID1
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: Help with raid 10 issue
- From: Phil Turmel <philip@xxxxxxxxxx>
Help with raid 10 issue
- From: Stefan Lamby <sl@xxxxxxxx>
Re: Last working drive in RAID1
- From: NeilBrown <neilb@xxxxxxx>
Re: Last working drive in RAID1
- From: Eric Mei <meijia@xxxxxxxxx>
Re: Hung RAID5 array with discard
- From: Terry Hardie <thardie@xxxxxxxxxxxxxxxx>
Re: Last working drive in RAID1
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID0 & diskstats.
- From: NeilBrown <neilb@xxxxxxx>
Last working drive in RAID1
- From: Eric Mei <meijia@xxxxxxxxx>
Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH] IncRemove: Set "auto-read" only after successful excl open.
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] IMSM-orom: make sure, that device list is supported
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] Fix stray --cluster-confrim crash
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] Communication Framework: fix semicolon.cocci warnings
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH md] recover_bitmaps() can be static
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
- From: NeilBrown <neilb@xxxxxxx>
Re: Riad scrub generated errors, should I worry?
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: Riad scrub generated errors, should I worry?
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: Riad scrub generated errors, should I worry?
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Riad scrub generated errors, should I worry?
- From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
Re: Riad scrub generated errors, should I worry?
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: Riad scrub generated errors, should I worry?
- From: Thomas Fjellstrom <thomas@xxxxxxxxxxxxx>
[PATCH] Fix stray --cluster-confrim crash
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: Riad scrub generated errors, should I worry?
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Riad scrub generated errors, should I worry?
- From: "Wilson, Jonathan" <piercing_male@xxxxxxxxxxx>
[GIT PULL REQUEST] md fixes for 4.0
- From: NeilBrown <neilb@xxxxxxx>
Re: Bug#779412: block devices loosing state after resume: trigger udev rules to re-apply settings
- From: Chris <email.bug@xxxxxxxx>
Re: Bug#779412: block devices loosing state after resume: trigger udev rules to re-apply settings
- From: Michael Biebl <biebl@xxxxxxxxxx>
block devices loosing state after resume: trigger udev rules to re-apply settings
- From: Chris <email.bug@xxxxxxxx>
[PATCH] Communication Framework: fix semicolon.cocci warnings
- From: kbuild test robot <fengguang.wu@xxxxxxxxx>
[md:for-next 14/48] drivers/md/md-cluster.c:190:6: sparse: symbol 'recover_bitmaps' was not declared. Should it be static?
- From: kbuild test robot <fengguang.wu@xxxxxxxxx>
[PATCH md] recover_bitmaps() can be static
- From: kbuild test robot <fengguang.wu@xxxxxxxxx>
Re: raid0: "clean" state on drive failure/removal
- From: NeilBrown <neilb@xxxxxxx>
raid0: "clean" state on drive failure/removal
- From: Sushma Gurram <Sushma.Gurram@xxxxxxxxxxx>
Re: [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
[PATCH] IncRemove: Set "auto-read" only after successful excl open.
- From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
[PATCH] IMSM-orom: make sure, that device list is supported
- From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
Re: [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
smartctl-timeouts_v1.0 (erc timeout fix)
- From: Chris <email.bug@xxxxxxxx>
Re: RAID6 write I/O amplification?
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID6 write I/O amplification?
- From: Alireza Haghdoost <alireza@xxxxxxxxxx>
Re: [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
Re: [PATCH 4/5] IncrementalScan(): Make sure 'st' is valid before dereferencing it
- From: "John Stoffel" <john@xxxxxxxxxxx>
Re: [PATCH 4/5] IncrementalScan(): Make sure 'st' is valid before dereferencing it
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 4/5] IncrementalScan(): Make sure 'st' is valid before dereferencing it
- From: "John Stoffel" <john@xxxxxxxxxxx>
Re: udev rules and scripts (erc timeout fix)
- From: Chris <email.bug@xxxxxxxx>
Re: [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
Re: [dm-devel] [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
Re: [PATCH 2/5] Check return of stat() to avoid covscan complaining
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [dm-devel] [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/5] Check return of stat() to avoid covscan complaining
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 2/5] Check return of stat() to avoid covscan complaining
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 2/5] Check return of stat() to avoid covscan complaining
- From: NeilBrown <neilb@xxxxxxx>
[PATCH 1/5] Grow.c: Fix classic readlink() buffer overflow
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 4/5] IncrementalScan(): Make sure 'st' is valid before dereferencing it
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 5/5] write_super_imsm_spares(): C statements are terminated by ;
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 0/5] Fix issues reported by covscan and newer GCC
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 3/5] add_orom(): Compare content of struct imsm_orom rather than pointers to it
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 2/5] Check return of stat() to avoid covscan complaining
- From: Jes.Sorensen@xxxxxxxxxx
Re: An old "write-mostly" read balance issue
- From: Tomáš Hodek <tomas.hodek@xxxxxxxx>
AW: RAID6 write I/O amplification?
- From: Markus Stockhausen <stockhausen@xxxxxxxxxxx>
RAID6 write I/O amplification?
- From: Roman Mamedov <rm@xxxxxxxxxxx>
Inject I/O latency for RAID5/6 read and writes
- From: Alireza Haghdoost <alireza@xxxxxxxxxx>
Re: [PATCH 02/24] Add number of nodes to bitmap structure for clustering
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
Re: [dm-devel] [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
Re: Optimal chunk size for RAID5?
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 02/24] Add number of nodes to bitmap structure for clustering
- From: NeilBrown <neilb@xxxxxxx>
Re: Optimal chunk size for RAID5?
- From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
Re: [dm-devel] [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
- From: NeilBrown <neilb@xxxxxxx>
Re: Metadata > 0.90 and auto-assemble
- From: NeilBrown <neilb@xxxxxxx>
Re: An old "write-mostly" read balance issue
- From: NeilBrown <neilb@xxxxxxx>
Re: Metadata > 0.90 and auto-assemble
- From: Mark Knecht <markknecht@xxxxxxxxx>
Re: Optimal chunk size for RAID5?
- From: NeilBrown <neilb@xxxxxxx>
Re: Metadata > 0.90 and auto-assemble
- From: Joshua Kinard <kumba@xxxxxxxxxx>
Re: Metadata > 0.90 and auto-assemble
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Metadata > 0.90 and auto-assemble
- From: Joshua Kinard <kumba@xxxxxxxxxx>
Re: Optimal chunk size for RAID5?
- From: Alireza Haghdoost <alireza@xxxxxxxxxx>
Re: re-add POLICY
- From: Chris <email.bug@xxxxxxxx>
Re: Optimal chunk size for RAID5?
- From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
Re: Optimal chunk size for RAID5?
- From: Roman Mamedov <rm@xxxxxxxxxxx>
Optimal chunk size for RAID5?
- From: Christer Solskogen <christer.solskogen@xxxxxxxxx>
Re: udev rules and scripts (erc timeout fix)
- From: Chris <email.bug@xxxxxxxx>
rules and scripts (erc timeout fix)
- From: email.bug@xxxxxxxx
Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
Re: [PATCH] [md] raid5: check faulty flag for array status during recovery.
- From: Eric Mei <meijia@xxxxxxxxx>
Re: mdadm raid 5 one disk overwritten file system failed
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
Re: [PATCH] [md] raid5: check faulty flag for array status during recovery.
- From: NeilBrown <neilb@xxxxxxx>
Re: mdadm raid 5 one disk overwritten file system failed
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
SV: mdadm raid 5 one disk overwritten file system failed
- From: "John Andre Taule" <post@xxxxxxxxxxxxx>
Re: mdadm raid 5 one disk overwritten file system failed
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
Re: mdadm raid 5 one disk overwritten file system failed
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
SV: mdadm raid 5 one disk overwritten file system failed
- From: "John Andre Taule" <post@xxxxxxxxxxxxx>
Re: mdadm raid 5 one disk overwritten file system failed
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
mdadm raid 5 one disk overwritten file system failed
- From: "John Andre Taule" <post@xxxxxxxxxxxxx>
Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
[PATCH/RFC/RFT] md: allow resync to go faster when there is competing IO.
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
- From: NeilBrown <neilb@xxxxxxx>
Re: Potential Bug in "echo 0 > /dev/md0"
- From: NeilBrown <neilb@xxxxxxx>
Re: help with the little script (erc timout fix)
- From: NeilBrown <neilb@xxxxxxx>
Re: Potential Bug in "echo 0 > /dev/md0"
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 0/1] RFC: Use /dev/md/X as default name
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: Potential Bug in "echo 0 > /dev/md0"
- From: Alireza Haghdoost <alireza@xxxxxxxxxx>
Re: Potential Bug in "echo 0 > /dev/md0"
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Potential Bug in "echo 0 > /dev/md0"
- From: Alireza Haghdoost <alireza@xxxxxxxxxx>
help with the little script (erc timout fix)
- From: Chris <email.bug@xxxxxxxx>
Re: RAID1 might_sleep() warning on 3.19-rc7
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
mdadm monitoring for RAID-1 - no events after pulling out all disks.
- From: Iakiv Shchelkunov <iakiv.shchelkunov@xxxxxxxxxxxxxxx>
Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
- From: Chris <email.bug@xxxxxxxx>
Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
- From: NeilBrown <neilb@xxxxxxx>
[GIT PULL REQUEST] some more bugfixes for md.
- From: NeilBrown <neilb@xxxxxxx>
Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID1 might_sleep() warning on 3.19-rc7
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] Revert "md: When RAID5 is dirty, force reconstruct-write instead of read-modify-write."
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] Revert "md: When RAID5 is dirty, force reconstruct-write instead of read-modify-write."
- From: Jes.Sorensen@xxxxxxxxxx
Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
- From: Chris <email.bug@xxxxxxxx>
Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Re: re-add POLICY
- From: Chris <email.bug@xxxxxxxx>
Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
- From: Chris <email.bug@xxxxxxxx>
Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
- From: Mikael Abrahamsson <swmike@xxxxxxxxx>
Re: What are mdadm maintainers to do? (error recovery redundancy/data loss)
- From: Chris <email.bug@xxxxxxxx>
Re: What are mdadm maintainers to do? (was: desktop disk's error recovery timeouts)
- From: NeilBrown <neilb@xxxxxxx>
Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: All drive in Raid 5 are in 'spare' mode
- From: Dush <tomdush@xxxxxxxxx>
Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: All drive in Raid 5 are in 'spare' mode
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: What are mdadm maintainers to do?
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: All drive in Raid 5 are in 'spare' mode
- From: Dush <tomdush@xxxxxxxxx>
What are mdadm maintainers to do? (was: desktop disk's error recovery timeouts)
- From: Chris <email.bug@xxxxxxxx>
Re: desktop disk's error recovery timouts
- From: Phil Turmel <philip@xxxxxxxxxx>
desktop disk's error recovery timouts (was: re-add POLICY)
- From: Chris <email.bug@xxxxxxxx>
Re: re-add POLICY
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: RAID 1 metadata - keep separate from mirror disks ?
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: re-add POLICY
- From: Chris <email.bug@xxxxxxxx>
RE: RAID 1 metadata - keep separate from mirror disks ?
- From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
Re: mdadm failed to remove internal bitmap
- From: NeilBrown <neilb@xxxxxxx>
Re: mdadm failed to remove internal bitmap
- From: gary <gary.mdjiang@xxxxxxxxx>
Re: [md PATCH] md/raid1: round up to bdev_logical_block_size in narrow_write_error
- From: NeilBrown <neilb@xxxxxxx>
Re: mdadm failed to remove internal bitmap
- From: NeilBrown <neilb@xxxxxxx>
Re: re-add POLICY
- From: NeilBrown <neilb@xxxxxxx>
Re: re-add POLICY: conflict detection?
- From: Chris <email.bug@xxxxxxxx>
Re: update mdadm version to 3.3.2 in Centos 6.4
- From: alpha lin <lin.alpha@xxxxxxxxx>
[PATCH 2/3] md raid0: access mddev->queue (request queue member) conditionally because it is not set when accessed from dm-raid
- From: heinzm@xxxxxxxxxx
[PATCH 1/3] md core: add 2 API functions for takeover and resize to support dm-raid
- From: heinzm@xxxxxxxxxx
[PATCH 0/3] md raid: enhancements to support the device mapper dm-raid target
- From: heinzm@xxxxxxxxxx
[PATCH 3/3] md bitmap: export bitmap_destroy() to support dm-raid down takover to raid0
- From: heinzm@xxxxxxxxxx
re-add POLICY
- From: Chris <email.bug@xxxxxxxx>
[PATCH 0/1] Bug fix for mdadm 3.3 with large md device numbers
- From: Mike Lovell <mlovell@xxxxxxxxxxxx>
[PATCH 1/1] Use dev_t for devnm2devid and devid2devnm
- From: Mike Lovell <mlovell@xxxxxxxxxxxx>
Re: [PATCH RESEND] Monitor: fix for regression with container devices
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
Re: RAID1 might_sleep() warning on 3.19-rc7
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Re: RAID1 might_sleep() warning on 3.19-rc7
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
mdadm failed to remove internal bitmap
- From: gary <gary.mdjiang@xxxxxxxxx>
Re: RAID1 might_sleep() warning on 3.19-rc7
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID1 might_sleep() warning on 3.19-rc7
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Re: raid1 narrow_write_error with 4K disks, sd "bad block number requested" messages
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID1 might_sleep() warning on 3.19-rc7
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH] md/raid1: round up to bdev_logical_block_size in narrow_write_error
- From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
Re: raid1 narrow_write_error with 4K disks, sd "bad block number requested" messages
- From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
RE: RAID 1 metadata - keep separate from mirror disks ?
- From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
Re: please help - raid 1 degraded
- From: Roaming <antmbox@xxxxxxxxxxxxxxx>
[GIT PULL REQUEST] md updates for 3.20
- From: NeilBrown <neilb@xxxxxxx>
Re: please help - raid 1 degraded
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: [PATCH RESEND] Change way of printing name of a process
- From: NeilBrown <neilb@xxxxxxx>
Re: All drive in Raid 5 are in 'spare' mode
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: please help - raid 1 degraded
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
Re: please help - raid 1 degraded
- From: sunruh@xxxxxxxxxxxx
Re: please help - raid 1 degraded
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
Re: Wierd: Degrading while recovering raid5
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: please help - raid 1 degraded
- From: sunruh@xxxxxxxxxxxx
Re: please help - raid 1 degraded
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
Re: Wierd: Degrading while recovering raid5
- From: Kyle Logue <teque5@xxxxxxxxx>
[PATCH RESEND] Change way of printing name of a process
- From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
All drive in Raid 5 are in 'spare' mode
- From: Dush <tomdush@xxxxxxxxx>
[PATCH 1/1] mddev_create(): choose /dev/md/ name over /dev/mdX
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 0/1] RFC: Use /dev/md/X as default name
- From: Jes.Sorensen@xxxxxxxxxx
Re: dead RAID6 array on CentOS6.6 / kernel 3.19
- From: Adam Thompson <athompso@xxxxxxxxxxxx>
please help - raid 1 degraded
- From: sunruh@xxxxxxxxxxxx
Re: [PATCH 00/24] Clustered MD RAID1
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
Re: RAID 1 metadata - keep separate from mirror disks ?
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Wierd: Degrading while recovering raid5
- From: Phil Turmel <philip@xxxxxxxxxx>
RAID 1 metadata - keep separate from mirror disks ?
- From: Suresh Babu Kandukuru <suresh.babu.kandukuru@xxxxxxxxxx>
Re: Wierd: Degrading while recovering raid5
- From: Kyle Logue <teque5@xxxxxxxxx>
Re: [PATCH RESEND] Monitor: fix for regression with container devices
- From: NeilBrown <neilb@xxxxxxx>
Re: dead RAID6 array on CentOS6.6 / kernel 3.19
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 00/24] Clustered MD RAID1
- From: NeilBrown <neilb@xxxxxxx>
Re: [Board] dead RAID6 array on CentOS6.6 / kernel 3.19
- From: Adam Thompson <athompso@xxxxxxxxxxxx>
Re: dead RAID6 array on CentOS6.6 / kernel 3.19
- From: Adam Thompson <athompso@xxxxxxxxxxxx>
Re: dead RAID6 array on CentOS6.6 / kernel 3.19
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: dead RAID6 array on CentOS6.6 / kernel 3.19
- From: Adam Thompson <athompso@xxxxxxxxxxxx>
Re: dead RAID6 array on CentOS6.6 / kernel 3.19
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: ignoring %s as it reports %s as failed
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Wierd: Degrading while recovering raid5
- From: Phil Turmel <philip@xxxxxxxxxx>
dead RAID6 array on CentOS6.6 / kernel 3.19
- From: Adam Thompson <athompso@xxxxxxxxxxxx>
[no subject]
- From: Kyle Logue <teque5@xxxxxxxxx>
Re: Wierd: Degrading while recovering raid5
- From: Kyle Logue <teque5@xxxxxxxxx>
Re: [PATCH 00/24] Clustered MD RAID1
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
ignoring %s as it reports %s as failed
- From: Valentijn <v@xxxxxxxxxxxxxxxx>
Re: Wierd: Degrading while recovering raid5
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: RAID1 might_sleep() warning on 3.19-rc7
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Re: RAID1 might_sleep() warning on 3.19-rc7
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Re: Wierd: Degrading while recovering raid5
- From: Adam Goryachev <mailinglists@xxxxxxxxxxxxxxxxxxxxxx>
Re: Upgrading storage server
- From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
Wierd: Degrading while recovering raid5
- From: Kyle Logue <teque5@xxxxxxxxx>
Re: Upgrading storage server
- From: "John Stoffel" <john@xxxxxxxxxxx>
Re: RAID1 might_sleep() warning on 3.19-rc7
- From: NeilBrown <neilb@xxxxxxx>
Re: mdsadm -A won't assemble my array
- From: "G. Michael Carter" <mikey@xxxxxxxxxxxxxxx>
Re: mdsadm -A won't assemble my array
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: mdsadm -A won't assemble my array
- From: "G. Michael Carter" <mikey@xxxxxxxxxxxxxxx>
Re: mdsadm -A won't assemble my array
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: mdsadm -A won't assemble my array
- From: "G. Michael Carter" <mikey@xxxxxxxxxxxxxxx>
mdsadm -A won't assemble my array
- From: "G. Michael Carter" <mikey@xxxxxxxxxxxxxxx>
Re: Upgrading storage server
- From: Joe Landman <joe.landman@xxxxxxxxx>
Upgrading storage server
- From: Adam Goryachev <adam@xxxxxxxxxxxxxxxxxxxxxx>
Re: raid md126, md127 problem after reboot, howto fix?
- From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Re: raid md126, md127 problem after reboot, howto fix?
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
[PATCH RESEND] Monitor: fix for regression with container devices
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
Re: raid md126, md127 problem after reboot, howto fix?
- From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Re: raid md126, md127 problem after reboot, howto fix?
- From: Sebastian Parschauer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Re: RAID1 might_sleep() warning on 3.19-rc7
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Re: RAID1 might_sleep() warning on 3.19-rc7
- From: NeilBrown <neilb@xxxxxxx>
Re: raid md126, md127 problem after reboot, howto fix?
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
raid md126, md127 problem after reboot, howto fix?
- From: Marc Widmer <metafor@xxxxxxxxx>
Re: md resync ignoring unreadable sectors
- From: "John Stoffel" <john@xxxxxxxxxxx>
Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
- From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
An old "write-mostly" read balance issue
- From: Dark Penguin <darkpenguin@xxxxxxxxx>
Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
- From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
Re: md resync ignoring unreadable sectors
- From: Roman Mamedov <rm@xxxxxxxxxxx>
Re: md resync ignoring unreadable sectors
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: md resync ignoring unreadable sectors
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
Re: md resync ignoring unreadable sectors
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: md resync ignoring unreadable sectors
- From: Roman Mamedov <rm@xxxxxxxxxxx>
Re: md resync ignoring unreadable sectors
- From: Eyal Lebedinsky <eyal@xxxxxxxxxxxxxx>
md resync ignoring unreadable sectors
- From: Roman Mamedov <rm@xxxxxxxxxxx>
Re: [PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
- From: Mike Snitzer <snitzer@xxxxxxxxxx>
Re: RAID1 might_sleep() warning on 3.19-rc7
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Re: [PATCH 00/24] Clustered MD RAID1
- From: NeilBrown <neilb@xxxxxxx>
Re: md: 'array_size' sysfs attribute
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] drivers: md: md-thin: remove duplication with time_after
- From: Pierre Chevalier <pierrechevalier83@xxxxxxxxx>
Re: RAID1 might_sleep() warning on 3.19-rc7
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] drivers: md: remove duplication with time_after
- From: Pierre Chevalier <pierrechevalier83@xxxxxxxxx>
RAID1 might_sleep() warning on 3.19-rc7
- From: Tony Battersby <tonyb@xxxxxxxxxxxxxxx>
re: md: 'array_size' sysfs attribute
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Re: Can't reshape raid0 to raid10
- From: Xiao Ni <xni@xxxxxxxxxx>
Re: BUG drivers/md/md.c: data-offset reshape renders array unloadable
- From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
Re: BUG drivers/md/md.c: data-offset reshape renders array unloadable
- From: NeilBrown <neilb@xxxxxxx>
Re: raid5 Unplug the disk
- From: NeilBrown <neilb@xxxxxxx>
Re: raid1 narrow_write_error with 4K disks, sd "bad block number requested" messages
- From: NeilBrown <neilb@xxxxxxx>
Re: unsynchronized raid10 with different events count
- From: NeilBrown <neilb@xxxxxxx>
Re: Off-Topic Write cache disabling?
- From: NeilBrown <neilb@xxxxxxx>
Re: Array died during grow; now resync stopped
- From: NeilBrown <neilb@xxxxxxx>
Re: Off-Topic Write cache disabling?
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
Re: Off-Topic Write cache disabling?
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
Aw: Re: Array died during grow; now resync stopped
- From: "Jörg Habenicht" <j.habenicht@xxxxxx>
Re: Array died during grow; now resync stopped
- From: NeilBrown <neilb@xxxxxxx>
Re: Can't reshape raid0 to raid10
- From: NeilBrown <neilb@xxxxxxx>
RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
Re: Off-Topic Write cache disabling?
- From: Weedy <weedy2887@xxxxxxxxx>
Re: Off-Topic Write cache disabling?
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
[md PATCH 26/26] md: wakeup thread upon rdev_dec_pending()
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 25/26] md: make reconfig_mutex optional for writes to md sysfs files.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 24/26] md: move mddev_lock and related to md.h
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 23/26] md: use mddev->lock to protect updates to resync_{min, max}.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 22/26] md: minor cleanup in safe_delay_store.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 21/26] md: move GET_BITMAP_FILE ioctl out from mddev_lock.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 20/26] md: tidy up set_bitmap_file
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 19/26] md: remove unnecessary 'buf' from get_bitmap_file.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 18/26] md: remove mddev_lock from rdev_attr_show()
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 17/26] md: remove mddev_lock() from md_attr_show()
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 16/26] md/raid5: use ->lock to protect accessing raid5 sysfs attributes.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 15/26] md: remove need for mddev_lock() in md_seq_show()
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 14/26] md/bitmap: protect clearing of ->bitmap by mddev->lock
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 13/26] md: protect ->pers changes with mddev->lock
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 12/26] md: level_store: group all important changes into one place.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 11/26] md: rename ->stop to ->free
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 10/26] md: split detach operation out from ->stop.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 09/26] md/linear: remove rcu protections in favour of suspend/resume
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 08/26] md: make merge_bvec_fn more robust in face of personality changes.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 07/26] md: make ->congested robust against personality changes.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 06/26] md: rename mddev->write_lock to mddev->lock
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 05/26] md/raid5: need_this_block: tidy/fix last condition.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 04/26] md/raid5: need_this_block: start simplifying the last two conditions.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 03/26] md/raid5: separate out the easy conditions in need_this_block.
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 02/26] md/raid5: separate large if clause out of fetch_block().
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 01/26] md: do_release_stripe(): No need to call md_wakeup_thread() twice
- From: NeilBrown <neilb@xxxxxxx>
[md PATCH 00/26] Pending md patches.
- From: NeilBrown <neilb@xxxxxxx>
[GIT PULL REQUEST] 2 fixes for md in 3.19
- From: NeilBrown <neilb@xxxxxxx>
Re: Off-Topic Write cache disabling?
- From: Alireza Haghdoost <alireza@xxxxxxxxxx>
Re: Off-Topic Write cache disabling?
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
Off-Topic Write cache disabling?
- From: Weedy <weedy2887@xxxxxxxxx>
Re: update mdadm version to 3.3.2 in Centos 6.4
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Aw: Re: Array died during grow; now resync stopped
- From: "Jörg Habenicht" <j.habenicht@xxxxxx>
Re: Can't reshape raid0 to raid10
- From: Xiao Ni <xni@xxxxxxxxxx>
Re: RAID1 removing failed disk returns EBUSY
- From: Xiao Ni <xni@xxxxxxxxxx>
Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: NeilBrown <neilb@xxxxxxx>
Fwd: update mdadm version to 3.3.2 in Centos 6.4
- From: alpha lin <lin.alpha@xxxxxxxxx>
Re: [PATCH 2/3] md/bitmap: Delete an unnecessary check before the function call "kfree"
- From: NeilBrown <neilb@xxxxxxx>
Re: Array died during grow; now resync stopped
- From: NeilBrown <neilb@xxxxxxx>
[PATCH 3/3] dm ioctl: Delete an unnecessary check before the function call "dm_table_destroy"
- From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
[PATCH 2/3] md/bitmap: Delete an unnecessary check before the function call "kfree"
- From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
[PATCH 1/3] dm snapshot: Deletion of unnecessary checks before the function call "vfree"
- From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
[PATCH 0/3] md: Deletion of a few unnecessary checks
- From: SF Markus Elfring <elfring@xxxxxxxxxxxxxxxxxxxxx>
update mdadm version to 3.3.2 in Centos 6.4
- From: alpha lin <lin.alpha@xxxxxxxxx>
Array died during grow; now resync stopped
- From: Jörg Habenicht <j.habenicht@xxxxxx>
RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
Re: RAID1 removing failed disk returns EBUSY
- From: NeilBrown <neilb@xxxxxxx>
Re: [dm-devel] [PATCH] md: fix raid5 livelock
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] md: do_release_stripe(): No need to call md_wakeup_thread() twice
- From: NeilBrown <neilb@xxxxxxx>
Re: unsynchronized raid10 with different events count
- From: LuVar <luvar@xxxxxxxxxxxx>
Re: unsynchronized raid10 with different events count
- From: LuVar <luvar@xxxxxxxxxxxx>
unsynchronized raid10 with different events count
- From: LuVar <luvar@xxxxxxxxxxxx>
Re: RAID1 removing failed disk returns EBUSY
- From: Xiao Ni <xni@xxxxxxxxxx>
Re: RAID1 removing failed disk returns EBUSY
- From: Xiao Ni <xni@xxxxxxxxxx>
[PATCH] md: do_release_stripe(): No need to call md_wakeup_thread() twice
- From: Jes.Sorensen@xxxxxxxxxx
Re: [PATCH] md: fix raid5 livelock
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: superfluous md_wakeup_thread()
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: RAID1 removing failed disk returns EBUSY
- From: Xiao Ni <xni@xxxxxxxxxx>
Re: [dm-devel] [PATCH] md: fix raid5 livelock
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
raid1 narrow_write_error with 4K disks, sd "bad block number requested" messages
- From: Nate Dailey <nate.dailey@xxxxxxxxxxx>
Re: RAID1 removing failed disk returns EBUSY
- From: NeilBrown <neilb@xxxxxxx>
Re: superfluous md_wakeup_thread()
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] IMSM: Clear migration record on disks more often
- From: NeilBrown <neilb@xxxxxxx>
Re: raid5 Unplug the disk
- From: John Drescher <drescherjm@xxxxxxxxx>
Re: [dm-devel] [patch] dm cache: fix up IS_ERR vs NULL confusion
- From: Joe Thornber <thornber@xxxxxxxxxx>
raid5 Unplug the disk
- From: "lilofile" <lilofile@xxxxxxxxxx>
[patch] dm cache: fix up IS_ERR vs NULL confusion
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Re: [PATCH] md: fix raid5 livelock
- From: NeilBrown <neilb@xxxxxxx>
Re: Monitor Queue Depth for RAID-5 md device
- From: NeilBrown <neilb@xxxxxxx>
Monitor Queue Depth for RAID-5 md device
- From: Alireza Haghdoost <alireza@xxxxxxxxxx>
[PATCH] md: fix raid5 livelock
- From: Heinz Mauelshagen <heinzm@xxxxxxxxxx>
Monitor Queue Depth for RAID-5 md device
- From: Alireza Haghdoost <alireza@xxxxxxxxxx>
Re: BUG drivers/md/md.c: data-offset reshape renders array unloadable
- From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
Re: BUG drivers/md/md.c: data-offset reshape renders array unloadable
- From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
BUG drivers/md/md.c: data-offset reshape renders array unloadable
- From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
Re: RAID1 removing failed disk returns EBUSY
- From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
All drive in Raid 5 are in 'spare' mode
- From: Dush <tomdush@xxxxxxxxx>
Re: mdadm RAID6 "active" with spares and failed disks; need help
- From: Valentijn <v@xxxxxxxxxxxxxxxx>
Re: [dm-devel] livelock on MD RAID5
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: kernel refuses devices mdadm -E accepts
- From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
Expanding partitions -> missing md on kernel load
- From: Scott Tablett <scott.tablett@xxxxxxxxxx>
BUG in "RAID5: batch adjacent full stripe write" - commit 1b8035b0a84a69b3148bbfa1df1350501d0b0869
- From: Sushma Gurram <Sushma.Gurram@xxxxxxxxxxx>
Re: mdadm RAID6 "active" with spares and failed disks; need help
- From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
RE: BUG in "RAID5: batch adjacent full stripe write" - commit 1b8035b0a84a69b3148bbfa1df1350501d0b0869
- From: Sushma Gurram <Sushma.Gurram@xxxxxxxxxxx>
RE: BUG in "RAID5: batch adjacent full stripe write" - commit 1b8035b0a84a69b3148bbfa1df1350501d0b0869
- From: Sushma Gurram <Sushma.Gurram@xxxxxxxxxxx>
Re: kernel refuses devices mdadm -E accepts
- From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
RE: RAID 6 recovery issue
- From: "Graham Mitchell" <gmitch@xxxxxxxxxxx>
Re: kernel refuses devices mdadm -E accepts
- From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
Re: kernel refuses devices mdadm -E accepts
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: kernel refuses devices mdadm -E accepts
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: RAID 6 recovery issue
- From: Roman Mamedov <rm@xxxxxxxxxxx>
RAID 6 recovery issue
- From: "Graham Mitchell" <gmitch@xxxxxxxxxxx>
[PATCH] IMSM: Clear migration record on disks more often
- From: Pawel Baldysiak <pawel.baldysiak@xxxxxxxxx>
Re: [dm-devel] [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Re: [dm-devel] [PATCH RESEND] md:Remove no longer needed fix me comment in dm-region-hash.c for removing the structure pointer, *rh from the definiton of dm_region
- From: Alasdair G Kergon <agk@xxxxxxxxxx>
Is it possible to use bad_blocks to simulate write_error and activate hot-replace?
- From: Apple Yin <bravery.apple@xxxxxxxxx>
Re: RAID1 removing failed disk returns EBUSY
- From: Xiao Ni <xni@xxxxxxxxxx>
livelock on MD RAID5
- From: Mikulas Patocka <mpatocka@xxxxxxxxxx>
Re: kernel refuses devices mdadm -E accepts
- From: Roger Heflin <rogerheflin@xxxxxxxxx>
kernel refuses devices mdadm -E accepts
- From: "Wesley W. Terpstra" <wesley@xxxxxxxxxxx>
Re: RAID1 removing failed disk returns EBUSY
- From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
Re: RAID1 removing failed disk returns EBUSY
- From: Xiao Ni <xni@xxxxxxxxxx>
Re: Corrupted Cisco NSS4000 raid
- From: Valentijn Sessink <v@xxxxxxxxxxxxxxxx>
Corrupted Cisco NSS4000 raid
- From: Jan Hejl <jh@xxxxxxxxxx>
Re: RAID1 removing failed disk returns EBUSY
- From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
Re: RAID1 removing failed disk returns EBUSY
- From: Xiao Ni <xni@xxxxxxxxxx>
Re: RAID1 removing failed disk returns EBUSY
- From: Joe Lawrence <joe.lawrence@xxxxxxxxxxx>
Re: RAID1 removing failed disk returns EBUSY
- From: XiaoNi <xni@xxxxxxxxxx>
RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
Re: mdadm RAID6 "active" with spares and failed disks; need help
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
[PATCH v2 6/9] md/raid5: get rid of bio_fits_rdev()
- From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
[PATCH v2 7/9] block: kill merge_bvec_fn() completely
- From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
[PATCH v2 5/7] md/raid10: make sync_request_write() call bio_copy_data()
- From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
Re: mdadm RAID6 "active" with spares and failed disks; need help
- From: Valentijn Sessink <v@xxxxxxxxxxxxxxxx>
Re: mdadm RAID6 "active" with spares and failed disks; need help
- From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
[PATCH] dm mpath: simplify failure path of dm_miltipath_init()
- From: Johannes Thumshirn <morbidrsa@xxxxxxxxx>
superfluous md_wakeup_thread()
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
raid5 hard lockup
- From: Terry Hardie <thardie@xxxxxxxxxxxxxxxx>
Neil Brown is on leave
- From: NeilBrown <neilb@xxxxxxx>
Re: Unable to make mdadm from git (fatal error: ansidecl.h)
- From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
Unable to make mdadm from git (fatal error: ansidecl.h)
- From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
Re: mdadm RAID6 "active" with spares and failed disks; need help
- From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
Re: md raid performance with 3-18-rc3
- From: Manish Awasthi <manish.awasthi@xxxxxxxxxxxxxxxxxx>
Re: Reassembling RAID1 after good drive was offline [newbie]
- From: Aryeh Leib Taurog <vim@xxxxxxxxxxxxx>
[PATCH] [md] raid5: check faulty flag for array status during recovery.
- From: Eric Mei <meijia@xxxxxxxxx>
mdadm RAID6 "active" with spares and failed disks; need help
- From: Matt Callaghan <matt_callaghan@xxxxxxxxxxxx>
[PATCH] dm bufio: fix time comparison
- From: Asaf Vertz <asaf.vertz@xxxxxxxxxxx>
Re: Split RAID: Proposal for archival RAID using incremental batch checksum
- From: Anshuman Aggarwal <anshuman.aggarwal@xxxxxxxxx>
ignoring %s as it reports %s as failed
- From: Valentijn <v@xxxxxxxxxxxxxxxx>
Re: md raid performance with 3-18-rc3
- From: Manish Awasthi <manish.awasthi@xxxxxxxxxxxxxxxxxx>
Re: Reassembling RAID1 after good drive was offline [newbie]
- From: NeilBrown <neilb@xxxxxxx>
Re: Reassembling RAID1 after good drive was offline [newbie]
- From: Robert L Mathews <lists@xxxxxxxxxxxxx>
Re: [dm-devel] Questions about the function, queue_empty in dm-cache-policy-mq.c
- From: Joe Thornber <thornber@xxxxxxxxxx>
Re: Reassembling RAID1 after good drive was offline [newbie]
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
Re: Reassembling RAID1 after good drive was offline [newbie]
- From: Aryeh Leib Taurog <vim@xxxxxxxxxxxxx>
Re: Re : Re: Big trouble during reassemble a Raid5
- From: sylvain.depuille@xxxxxxxxxxx
Re: Re : Re: Big trouble during reassemble a Raid5
- From: sylvain.depuille@xxxxxxxxxxx
Re: Reassembling RAID1 after good drive was offline [newbie]
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: Reassembling RAID1 after good drive was offline [newbie]
- From: Aryeh Leib Taurog <vim@xxxxxxxxxxxxx>
Re: Reassembling RAID1 after good drive was offline [newbie]
- From: Robert L Mathews <lists@xxxxxxxxxxxxx>
Re: Reassembling RAID1 after good drive was offline [newbie]
- From: Aryeh Leib Taurog <vim@xxxxxxxxxxxxx>
Re: Reassembling RAID1 after good drive was offline [newbie]
- From: Aryeh Leib Taurog <vim@xxxxxxxxxxxxx>
Re: Reassembling RAID1 after good drive was offline [newbie]
- From: Anthonys Lists <antlists@xxxxxxxxxxxxxxx>
Re: Re : Re: Big trouble during reassemble a Raid5
- From: Can Jeuleers <can.jeuleers@xxxxxxxxx>
RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
Re: Re: Re : Re: Big trouble during reassemble a Raid5
- From: "John Stoffel" <john@xxxxxxxxxxx>
Re: Re: Re : Re: Big trouble during reassemble a Raid5
- From: "John Stoffel" <john@xxxxxxxxxxx>
Re: Re : Re: Big trouble during reassemble a Raid5
- From: sylvain.depuille@xxxxxxxxxxx
Re: Reassembling RAID1 after good drive was offline [newbie]
- From: Robert L Mathews <lists@xxxxxxxxxxxxx>
Re: Re : Re: Big trouble during reassemble a Raid5
- From: sylvain.depuille@xxxxxxxxxxx
[PATCH] md: dm-thin-metadata: Remove unused function
- From: Rickard Strandqvist <rickard_strandqvist@xxxxxxxxxxxxxxxxxx>
Reassembling RAID1 after good drive was offline [newbie]
- From: Aryeh Leib Taurog <vim@xxxxxxxxxxxxx>
Re: Re: Re : Re: Big trouble during reassemble a Raid5
- From: "John Stoffel" <john@xxxxxxxxxxx>
Re: Re : Re: Big trouble during reassemble a Raid5
- From: sylvain.depuille@xxxxxxxxxxx
Re: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: Pasi Kärkkäinen <pasik@xxxxxx>
Re: Re: Re : Re: Big trouble during reassemble a Raid5
- From: "John Stoffel" <john@xxxxxxxxxxx>
Re: Re : Re: Big trouble during reassemble a Raid5
- From: sylvain.depuille@xxxxxxxxxxx
Re: Re: Re : Re: Big trouble during reassemble a Raid5
- From: "John Stoffel" <john@xxxxxxxxxxx>
Re: Re : Re: Big trouble during reassemble a Raid5
- From: sylvain.depuille@xxxxxxxxxxx
RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
Re: Re : Re: Big trouble during reassemble a Raid5
- From: sylvain.depuille@xxxxxxxxxxx
Can't reshape raid0 to raid10
- From: Xiao Ni <xni@xxxxxxxxxx>
AW: md_raid5 recovering failed need help
- From: "Stephan Hafiz" <forum@xxxxxxxx>
Re: Re : Re: Big trouble during reassemble a Raid5
- From: "John Stoffel" <john@xxxxxxxxxxx>
[SOLVED] Re: On RAID5 read error during syncing - array .A.A
- From: Emery Guevremont <emery.guevremont@xxxxxxxxx>
Re: Big trouble during reassemble a Raid5
- From: "John Stoffel" <john@xxxxxxxxxxx>
Big trouble during reassemble a Raid5
- From: sylvain.depuille@xxxxxxxxxxx
A recommendation from Friend, screw college, I'm dropping out
- From: fernalynbuendia@xxxxxxxxxxx
Re: md_raid5 recovering failed need help
- From: Phil Turmel <philip@xxxxxxxxxx>
[PATCH][MD] raid : fix raid recoverying all data corruption, when j=0(sectors) interrupted by "echo idle > /sys/block/md0/md/sync_action"
- From: 董杨 <donglife1208@xxxxxxxxx>
Re: [PATCH 00/24] Clustered MD RAID1
- From: Marcus <shadowsor@xxxxxxxxx>
Re: [PATCH 00/24] Clustered MD RAID1
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
Re: [PATCH 00/24] Clustered MD RAID1
- From: Peter Kieser <peter@xxxxxxxxx>
md_raid5 recovering failed need help
- From: "Stephan Hafiz" <forum@xxxxxxxx>
RE: md_raid5 using 100% CPU and hang with status resync=PENDING, if a drive is removed during initialization
- From: Manibalan P <pmanibalan@xxxxxxxxxxxxxx>
Re: [PATCH 00/24] Clustered MD RAID1
- From: "John Stoffel" <john@xxxxxxxxxxx>
Re: [PATCH 00/24] Clustered MD RAID1
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
[PATCH] Monitor: fix for regression with container devices
- From: Artur Paszkiewicz <artur.paszkiewicz@xxxxxxxxx>
Re: [RFC PATCH 12/17] md/raid10: make sync_request_write() call bio_copy_data()
- From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
Re: [RFC PATCH 12/17] md/raid10: make sync_request_write() call bio_copy_data()
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: [PATCH 01/24] md-cluster: Design Documentation
- From: "John Stoffel" <john@xxxxxxxxxxx>
Re: 4 disks outage in RAID6
- From: Phil Turmel <philip@xxxxxxxxxx>
[RFC PATCH 13/17] md/raid5: get rid of bio_fits_rdev()
- From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
[RFC PATCH 12/17] md/raid10: make sync_request_write() call bio_copy_data()
- From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
[RFC PATCH 14/17] block: kill merge_bvec_fn() completely
- From: Dongsu Park <dongsu.park@xxxxxxxxxxxxxxxx>
Re: Expand RAID5 array or switch to RAID10
- From: Robin Hill <robin@xxxxxxxxxxxxxxx>
Re: Expand RAID5 array or switch to RAID10
- From: forumscollective@xxxxxxxxx
4 disks outage in RAID6
- From: Mark Kolama <indigo8472@xxxxxxxxx>
Re: [PATCH 01/24] md-cluster: Design Documentation
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
Re: [PATCH 01/24] md-cluster: Design Documentation
- From: John Stoffel <john@xxxxxxxxxxxxxxxxxxxxx>
Re: indefinite hang when growing/reshaping
- From: Xiao Ni <xni@xxxxxxxxxx>
Re: indefinite hang when growing/reshaping
- From: Xiao Ni <xni@xxxxxxxxxx>
Re: Panic doing BLKDISCARD on a raid 5 array on linux 3.17.3
- From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
[PATCH 23/24] Read from the first device when an area is resyncing
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>
[PATCH 24/24] Add new disk to clustered array
- From: Goldwyn Rodrigues <rgoldwyn@xxxxxxx>

[Index of Archives] [Linux RAID Wiki] [ATA RAID] [Linux SCSI Target Infrastructure] [Linux Block] [Linux IDE] [Linux SCSI] [Linux Hams] [Device Mapper] [Kernel] [Linux Admin] [Linux Net] [GFS] [RPM] [git] [Yosemite Forum] [Linux Networking]