Linux RAID Storage Date Index

Thread Index

Re: [patch 1/8] raid5: add a per-stripe lock
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [patch 8/8] raid5: create multiple threads to handle stripes
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [patch 7/8] raid5: raid5d handle stripe in batch way
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [patch 1/8] raid5: add a per-stripe lock
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch 6/8] raid5: make_request use batch stripe release
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [patch 1/8] raid5: add a per-stripe lock
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: [patch 8/8] raid5: create multiple threads to handle stripes
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch 7/8] raid5: raid5d handle stripe in batch way
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch 6/8] raid5: make_request use batch stripe release
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch 2/8] raid5: lockless access raid5 overrided bi_phys_segments
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch 1/8] raid5: add a per-stripe lock
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch 4/8] raid5: reduce chance release_stripe() taking device_lock
- From: NeilBrown <neilb@xxxxxxx>
Re: RAID5 with two drive sizes question
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: pg@xxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Ole Tange <ole@xxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Ole Tange <ole@xxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Ole Tange <ole@xxxxxxxx>
Problem with patch: "reject a re-add request that cannot be honoured" (commit bedd86b7773fd97f0d708cc0c371c8963ba7ba9a)
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Ole Tange <ole@xxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Ole Tange <ole@xxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Ole Tange <ole@xxxxxxxx>
Re: Re: [PATCH] md/raid5:Choose to replacing or recoverying when raid degraded and had a want_replacement disk at the same time.
- From: majianpeng <majianpeng@xxxxxxxxx>
Re: RAID5 with two drive sizes question
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: [PATCH] md/raid5:Choose to replacing or recoverying when raid degraded and had a want_replacement disk at the same time.
- From: NeilBrown <neilb@xxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: Re: [PATCH] md/raid5:Choose to replacing or recoverying when raid degraded and had a want_replacement disk at the same time.
- From: majianpeng <majianpeng@xxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Brad Campbell <lists2009@xxxxxxxxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: [PATCH] md/raid5:Choose to replacing or recoverying when raid degraded and had a want_replacement disk at the same time.
- From: NeilBrown <neilb@xxxxxxx>
Re: Failed drive in raid6 while doing data-check
- From: NeilBrown <neilb@xxxxxxx>
[PULL REQUEST] md fixes for 3.5-rc
- From: NeilBrown <neilb@xxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Ole Tange <ole@xxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Ole Tange <ole@xxxxxxxx>
Re: RAID5 with two drive sizes question
- From: "Joachim Otahal (privat)" <Jou@xxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Ole Tange <ole@xxxxxxxx>
Re: RAID5 with two drive sizes question
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: RAID5 with two drive sizes question
- From: Roman Mamedov <rm@xxxxxxxxxx>
Re: RAID5 with two drive sizes question
- From: "Joachim Otahal (privat)" <Jou@xxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Ole Tange <ole@xxxxxxxx>
Re: RAID5 with two drive sizes question
- From: Roman Mamedov <rm@xxxxxxxxxx>
RAID5 with two drive sizes question
- From: "Joachim Otahal (privat)" <Jou@xxxxxxx>
Re: Failed drive in raid6 while doing data-check
- From: Krzysztof Adamski <k@xxxxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Ole Tange <ole@xxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Ole Tange <ole@xxxxxxxx>
[PATCH] md/raid5:Choose to replacing or recoverying when raid degraded and had a want_replacement disk at the same time.
- From: majianpeng <majianpeng@xxxxxxxxx>
Re: [PATCH V1] md:Fix name of raid thread when raid takeovered.
- From: NeilBrown <neilb@xxxxxxx>
Re: Re: [PATCH V1] md:Fix name of raid thread when raid takeovered.
- From: majianpeng <majianpeng@xxxxxxxxx>
Re: [PATCH V1] md:Fix name of raid thread when raid takeovered.
- From: NeilBrown <neilb@xxxxxxx>
Re: Data Offset
- From: NeilBrown <neilb@xxxxxxx>
[PATCH V1] md:Fix name of raid thread when raid takeovered.
- From: majianpeng <majianpeng@xxxxxxxxx>
Re: Data Offset
- From: freeone3000 <freeone3000@xxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: Failed drive in raid6 while doing data-check
- From: NeilBrown <neilb@xxxxxxx>
Re: Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Joe Landman <joe.landman@xxxxxxxxx>
Software RAID checksum performance on 24 disks not even close to kernel reported
- From: Ole Tange <ole@xxxxxxxx>
Re: Data Offset
- From: NeilBrown <neilb@xxxxxxx>
Re: Data Offset
- From: Pierre Beck <mail@xxxxxxxxxxxxxx>
Re: Failed drive in raid6 while doing data-check
- From: Krzysztof Adamski <k@xxxxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
[patch 8/8] raid5: create multiple threads to handle stripes
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 7/8] raid5: raid5d handle stripe in batch way
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 6/8] raid5: make_request use batch stripe release
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 5/8] raid5: add batch stripe release
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 4/8] raid5: reduce chance release_stripe() taking device_lock
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 3/8] raid5: remove some device_lock locking places
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 2/8] raid5: lockless access raid5 overrided bi_phys_segments
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 1/8] raid5: add a per-stripe lock
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 0/8] raid5: improve write performance for fast storage
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: How to use replacement?
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] md:Fix name of raid thread when raid takeovered
- From: NeilBrown <neilb@xxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Re: How to use replacement?
- From: majianpeng <majianpeng@xxxxxxxxx>
Re: Re: [PATCH] md:Fix name of raid thread when raid takeovered
- From: majianpeng <majianpeng@xxxxxxxxx>
Re: tracking parity mismatches to a failing disk
- From: NeilBrown <neilb@xxxxxxx>
Re: Using a newer mdadm version just for re-adding a device
- From: NeilBrown <neilb@xxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: NeilBrown <neilb@xxxxxxx>
Re: Failed drive in raid6 while doing data-check
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/4] raid1: change the code layout of raid1_mergeable_bvec() to make it look a bit nicer
- From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
Re: [PATCH] md:Fix name of raid thread when raid takeovered
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/4] raid1: change the code layout of raid1_mergeable_bvec() to make it look a bit nicer
- From: NeilBrown <neilb@xxxxxxx>
Re: Data Offset
- From: NeilBrown <neilb@xxxxxxx>
Re: How to use replacement?
- From: NeilBrown <neilb@xxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
How to use replacement?
- From: majianpeng <majianpeng@xxxxxxxxx>
Re: [PATCH 2/2] md:Rewrite the md_write_start().
- From: NeilBrown <neilb@xxxxxxx>
Re: Re: [PATCH 2/2] md:Rewrite the md_write_start().
- From: majianpeng <majianpeng@xxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Andy Smith <andy@xxxxxxxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Andy Smith <andy@xxxxxxxxxxxxxx>
Re: [PATCH 2/2] md:Rewrite the md_write_start().
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: Failed drive in raid6 while doing data-check
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: Failed drive in raid6 while doing data-check
- From: Krzysztof Adamski <k@xxxxxxxxxxx>
Re: Failed drive in raid6 while doing data-check
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Failed drive in raid6 while doing data-check
- From: Krzysztof Adamski <k@xxxxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Andy Smith <andy@xxxxxxxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
[PATCH 2/2] md:Rewrite the md_write_start().
- From: majianpeng <majianpeng@xxxxxxxxx>
[PATCH 1/2] md/raid5:Change the order of md_write_start() and chunk_aligned_read() in function make_request().
- From: majianpeng <majianpeng@xxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Data Offset
- From: freeone3000 <freeone3000@xxxxxxxxx>
Re: Data Offset
- From: NeilBrown <neilb@xxxxxxx>
Re: Data Offset
- From: freeone3000 <freeone3000@xxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Andy Smith <andy@xxxxxxxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: Can extremely high load cause disks to be kicked?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Using a newer mdadm version just for re-adding a device
- From: Sven Hartrumpf <hartrumpf@xxxxxxx>
Re: Reason for md raid 01 blksize limited to 4 KiB?
- From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
[PATCH 4/4] md: put EXPORT_SYMBOL macro immediately after the corresponding function
- From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
[PATCH 3/4] md: introduce md_rdev_merge_bvec to reduce code duplicate
- From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
[PATCH 2/4] raid10: change the code layout of raid10_mergeable_bvec() to make it look a bit nicer
- From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
[PATCH 1/4] raid1: change the code layout of raid1_mergeable_bvec() to make it look a bit nicer
- From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
Can extremely high load cause disks to be kicked?
- From: Andy Smith <andy@xxxxxxxxxxxxxx>
[PATCH] md:Fix name of raid thread when raid takeovered
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: Reason for md raid 01 blksize limited to 4 KiB?
- From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
Re: Reason for md raid 01 blksize limited to 4 KiB?
- From: NeilBrown <neilb@xxxxxxx>
Using a newer mdadm version just for re-adding a device
- From: Sven Hartrumpf <hartrumpf@xxxxxxx>
Re: Reason for md raid 01 blksize limited to 4 KiB?
- From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
[PATCH] md:Fix checkpatch issues.
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: raid10 devices all marked as spares?!
- From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
Re: raid10 devices all marked as spares?!
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 0/2] Tests for add/remove of internal bitmaps
- From: NeilBrown <neilb@xxxxxxx>
Re: raid10 devices all marked as spares?!
- From: Oliver Schinagl <oliverlist@xxxxxxxxxxx>
Re: raid10 devices all marked as spares?!
- From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
[PATCH 2/2] New tests testing removal of internal bitmaps
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 1/2] New tests testing the addition of bitmaps
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 0/2] Tests for add/remove of internal bitmaps
- From: Jes.Sorensen@xxxxxxxxxx
Re: raid5 to raid6 - reshape very slow
- From: Alexander Kühn <alexander.kuehn@xxxxxxxxxx>
[PATCH] Fix --no-error in test script
- From: Jes.Sorensen@xxxxxxxxxx
Re: Reason for md raid 01 blksize limited to 4 KiB?
- From: NeilBrown <neilb@xxxxxxx>
Re: raid5 to raid6 - reshape very slow
- From: "jonathan@xxxxxxxxxxxxxxxxxxxx" <jonathan@xxxxxxxxxxxxxxxxxxxx>
Re: Reason for md raid 01 blksize limited to 4 KiB?
- From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Re: raid5 to raid6 - reshape very slow
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: [PATCH 4/4] Move setup code to a function and introduce matching cleanup argument
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: raid5 to raid6 - reshape very slow
- From: NeilBrown <neilb@xxxxxxx>
raid5 to raid6 - reshape very slow
- From: Jonathan Molyneux <jonathan@xxxxxxxxxxxxxxxxxxxx>
Re: [PATCH] imsm: fix: correct checking volume's degradation
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] mdadm: Fix Segmentation fault.
- From: NeilBrown <neilb@xxxxxxx>
Re: raid10 devices all marked as spares?!
- From: NeilBrown <neilb@xxxxxxx>
Re: raid10 devices all marked as spares?!
- From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
Re: raid10 devices all marked as spares?!
- From: NeilBrown <neilb@xxxxxxx>
raid10 devices all marked as spares?!
- From: Oliver Schinagl <oliver+list@xxxxxxxxxxx>
Re: Recovering from two raid superblocks on the same disks
- From: NeilBrown <neilb@xxxxxxx>
Recovering from two raid superblocks on the same disks
- From: Jeff Johnson <jeff.johnson@xxxxxxxxxxxxxxxxx>
Re: Reason for md raid 01 blksize limited to 4 KiB?
- From: NeilBrown <neilb@xxxxxxx>
Re: Hi! Strange issue with LSR -- bitmaps hadn't been used during 2 of 3 RAIDs resync
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: Hi! Strange issue with LSR -- bitmaps hadn't been used during 2 of 3 RAIDs resync
- From: NeilBrown <neilb@xxxxxxx>
Re: Hi! Strange issue with LSR -- bitmaps hadn't been used during 2 of 3 RAIDs resync
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: Hi! Strange issue with LSR -- bitmaps hadn't been used during 2 of 3 RAIDs resync
- From: NeilBrown <neilb@xxxxxxx>
Re: Bug#658701: mdadm: should send email if mismatches are reported by a check
- From: NeilBrown <neilb@xxxxxxx>
Re: Sequential writing to degraded RAID6 causing a lot of reading
- From: NeilBrown <neilb@xxxxxxx>
[patch 1/3 v2] MD: add a specific workqueue to do dispatch
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 3/3 v2] raid10: percpu dispatch for write request if bitmap supported
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 2/3 v2] raid1: percpu dispatch for write request if bitmap supported
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 0/3 v2] MD: improve raid1/10 write performance for fast storage
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [PATCH 4/4] Move setup code to a function and introduce matching cleanup argument
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/4] Add support for saving log files in test script
- From: NeilBrown <neilb@xxxxxxx>
Re: very slow file deletion on an SSD
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: very slow file deletion on an SSD
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: Hi! Strange issue with LSR -- bitmaps hadn't been used during 2 of 3 RAIDs resync
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: very slow file deletion on an SSD
- From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Re: very slow file deletion on an SSD
- From: joe.landman@xxxxxxxxx
Re: very slow file deletion on an SSD
- From: Krzysztof Adamski <k@xxxxxxxxxxx>
Re: Hi! Strange issue with LSR -- bitmaps hadn't been used during 2 of 3 RAIDs resync
- From: NeilBrown <neilb@xxxxxxx>
Hi! Strange issue with LSR -- bitmaps hadn't been used during 2 of 3 RAIDs resync
- From: Igor M Podlesny <for.poige+lsr@xxxxxxxxx>
Re: very slow file deletion on an SSD
- From: Stefan Ring <stefanrin@xxxxxxxxx>
Re: very slow file deletion on an SSD
- From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Re: very slow file deletion on an SSD
- From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Re: very slow file deletion on an SSD
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: raid 10f2 vs 1 on 2 drives
- From: keld@xxxxxxxxxx
Re: very slow file deletion on an SSD
- From: joe.landman@xxxxxxxxx
Re: very slow file deletion on an SSD
- From: Jon Nelson <jnelson-linux-raid@xxxxxxxxxxx>
Re: very slow file deletion on an SSD
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: very slow file deletion on an SSD
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: raid 10f2 vs 1 on 2 drives
- From: Bill Davidsen <davidsen@xxxxxxx>
Re: very slow file deletion on an SSD
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: very slow file deletion on an SSD
- From: Dave Chinner <david@xxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Stefan *St0fF* Huebner <st0ff@xxxxxxx>
Re: very slow file deletion on an SSD
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: raid 10f2 vs 1 on 2 drives
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: very slow file deletion on an SSD
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Bug#658701: mdadm: should send email if mismatches are reported by a check
- From: Michael Tokarev <mjt@xxxxxxxxxx>
[PATCH 2/2] md/raid456:Add interface for contorling eject rdev when re-write failed.
- From: "majianpeng" <majianpeng@xxxxxxxxx>
[PATCH 1/2] md/raid456: When readed error and raid was degraded,it try to set badsector, not ejecting the rdev.
- From: "majianpeng" <majianpeng@xxxxxxxxx>
[PATCH 0/2] Modify read error handle for RAID-4,5,6.
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: raid 10f2 vs 1 on 2 drives
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: raid 10f2 vs 1 on 2 drives
- From: Bill Davidsen <davidsen@xxxxxxx>
Re: very slow file deletion on an SSD
- From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Re: very slow file deletion on an SSD
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: very slow file deletion on an SSD
- From: Ben Myers <bpm@xxxxxxx>
Re: Sequential writing to degraded RAID6 causing a lot of reading
- From: Patrik Horník <patrik@xxxxxx>
[PATCH 2/4] Add --no-error argument to 'test'
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 4/4] Move setup code to a function and introduce matching cleanup argument
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 1/4] Add support for saving log files in test script
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 3/4] Improve --help message from test
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 0/4] More test suite enchancements
- From: Jes.Sorensen@xxxxxxxxxx
Re: very slow file deletion on an SSD
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
[PATCH] imsm: fix: correct checking volume's degradation
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
Re: Reason for md raid 01 blksize limited to 4 KiB?
- From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
[PATCH] mdadm: Fix Segmentation fault.
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: very slow file deletion on an SSD
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: very slow file deletion on an SSD
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
very slow file deletion on an SSD
- From: Joe Landman <joe.landman@xxxxxxxxx>
Re: Hi! Is "container" more efficient in terms of I/O op. numbers ...
- From: Igor Podlesny <for.poige+linux@xxxxxxxxx>
Re: Hi! Is "container" more efficient in terms of I/O op. numbers ...
- From: NeilBrown <neilb@xxxxxxx>
Re: Hi! Is "container" more efficient in terms of I/O op. numbers ...
- From: Igor Podlesny <for.poige+linux@xxxxxxxxx>
Re: Hi! Is "container" more efficient in terms of I/O op. numbers ...
- From: NeilBrown <neilb@xxxxxxx>
Hi! Is "container" more efficient in terms of I/O op. numbers ...
- From: Igor Podlesny <for.poige+linux@xxxxxxxxx>
Re: Sequential writing to degraded RAID6 causing a lot of reading
- From: Patrik Horník <patrik@xxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: [patch 2/4] raid1: percpu dispatch for write request if bitmap supported
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [PATCH] Increase minimum chunk size in testsuite to 64kB
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch 2/4] raid1: percpu dispatch for write request if bitmap supported
- From: NeilBrown <neilb@xxxxxxx>
Re: Data Offset
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch 2/4] raid1: percpu dispatch for write request if bitmap supported
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [PATCH] lib/raid6: fix sparse warnings in recovery functions
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] Increase minimum chunk size in testsuite to 64kB
- From: Anton Blanchard <anton@xxxxxxxxx>
Re: Question about commit 02e7c5b75cd4ad5176441add156389c71dab6e3a - avoid including wayward devices
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] lib/raid6: fix sparse warnings in recovery functions
- From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
Re: Sequential writing to degraded RAID6 causing a lot of reading
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch 1/4] raid1: directly dispatch write request if no bitmap
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch 2/4] raid1: percpu dispatch for write request if bitmap supported
- From: NeilBrown <neilb@xxxxxxx>
Re: [patch 1/4] raid1: directly dispatch write request if no bitmap
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [patch 1/4] raid1: directly dispatch write request if no bitmap
- From: NeilBrown <neilb@xxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: [patch 1/4] raid1: directly dispatch write request if no bitmap
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [patch 1/4] raid1: directly dispatch write request if no bitmap
- From: NeilBrown <neilb@xxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: NeilBrown <neilb@xxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: NeilBrown <neilb@xxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: [PATCH] md/raid456:Remove the judgement atomic_read(&rdev->read_errors).
- From: NeilBrown <neilb@xxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: David Brown <david.brown@xxxxxxxxxxxx>
Sequential writing to degraded RAID6 causing a lot of reading
- From: Patrik Horník <patrik@xxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
[PATCH] md/raid456:Remove the judgement atomic_read(&rdev->read_errors).
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: raid 10f2 vs 1 on 2 drives
- From: William Thompson <wt@xxxxxxxxxxxxxxxxxxxxxx>
[patch 4/4] raid10: percpu dispatch for write request if bitmap supported
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 3/4] raid10: directly dispatch write request if no bitmap
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 2/4] raid1: percpu dispatch for write request if bitmap supported
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 1/4] raid1: directly dispatch write request if no bitmap
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 0/4] MD: improve raid1/10 write performance for fast storage
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [PATCH 2/2] Add command line argument parsing to 'test' sript
- From: NeilBrown <neilb@xxxxxxx>
[PULL REQUEST] md updates for 3.5
- From: NeilBrown <neilb@xxxxxxx>
Re: SSSE6 / RAID6
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: SSSE6 / RAID6
- From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
Re: SSSE6 / RAID6
- From: NeilBrown <neilb@xxxxxxx>
Re: SSSE6 / RAID6
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: raid 10f2 vs 1 on 2 drives
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: SSSE6 / RAID6
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
SSSE6 / RAID6
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
raid 10f2 vs 1 on 2 drives
- From: William Thompson <wt@xxxxxxxxxxxxxxxxxxxxxx>
[PATCH 2/2] Add command line argument parsing to 'test' sript
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 1/2] Check for multipath module before running multipath tests
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 0/2] Test suite enhancements
- From: Jes.Sorensen@xxxxxxxxxx
Question about commit 02e7c5b75cd4ad5176441add156389c71dab6e3a - avoid including wayward devices
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
[PATCH] md/raid456:When degraded raid read error, not remove disk but set badsector
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Removing physical disk from RAID & LVM
- From: Tero Mäntyvaara <termant@xxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: NeilBrown <neilb@xxxxxxx>
Re: Reason for md raid 01 blksize limited to 4 KiB?
- From: NeilBrown <neilb@xxxxxxx>
Re: Reason for md raid 01 blksize limited to 4 KiB?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: About raid5 read error handle when raid5 was degraded.
- From: NeilBrown <neilb@xxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: CoolCold <coolthecold@xxxxxxxxx>
Re: Hot-replace for RAID5
- From: Asdo <asdo@xxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Brian Candler <B.Candler@xxxxxxxxx>
Re: Check / Automatic repair
- From: NeilBrown <neilb@xxxxxxx>
Re: Check / Automatic repair
- From: Fabien Bourigault <dradge@xxxxxxxxx>
About raid5 read error handle when raid5 was degraded.
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: Check / Automatic repair
- From: NeilBrown <neilb@xxxxxxx>
Re: Hot-replace for RAID5
- From: NeilBrown <neilb@xxxxxxx>
Check / Automatic repair
- From: Fabien Bourigault <dradge@xxxxxxxxx>
Reason for md raid 01 blksize limited to 4 KiB?
- From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Re: Re: Compiler mdadm-3.2.5 error
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: Compiler mdadm-3.2.5 error
- From: NeilBrown <neilb@xxxxxxx>
Compiler mdadm-3.2.5 error
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: [PATCH] md/bitmap:If bmap() failed,free buffers must check bitmap->pending_writes == 0.
- From: NeilBrown <neilb@xxxxxxx>
Re: Hot-replace for RAID5
- From: Patrik Horník <patrik@xxxxxx>
Re: Creating a 3-disk RAID6 array
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
[PULL REQUEST] one more md patch for 3.4
- From: NeilBrown <neilb@xxxxxxx>
Re: ioctl message
- From: NeilBrown <neilb@xxxxxxx>
ioctl message
- From: Wiliam Colls <william.colls@xxxxxxxxxx>
Re: [RFC PATCH 7/7] md: add bcache personality
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [RFC PATCH 7/7] md: add bcache personality
- From: Doug Ledford <dledford@xxxxxxxxxx>
resizing array to use spare space on disks.
- From: wilsonjonathan <piercing_male@xxxxxxxxxxx>
[PATCH] md/bitmap:If bmap() failed,free buffers must check bitmap->pending_writes == 0.
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: Re: Add set bad lba function in md-faulty module.
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: Creating a 3-disk RAID6 array
- From: NeilBrown <neilb@xxxxxxx>
Re: Creating a 3-disk RAID6 array
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
Re: Creating a 3-disk RAID6 array
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Hot-replace for RAID5
- From: NeilBrown <neilb@xxxxxxx>
Re: mdadm-3.2.5 coming soon :-(
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: fix: check if size of expansion is not larger than maximum
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: fix a typo in fprintf message
- From: NeilBrown <neilb@xxxxxxx>
Re: Creating a 3-disk RAID6 array
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Creating a 3-disk RAID6 array
- From: Oliver Martin <oliver@xxxxxxxxxxxxxxxx>
Re: sync speed strangeness and other advice
- From: NeilBrown <neilb@xxxxxxx>
Re: Creating a 3-disk RAID6 array
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: rebuilding Raid1 array
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
rebuilding Raid1 array
- From: Wiliam Colls <william.colls@xxxxxxxxxx>
Re: doubt about resync - raid1
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: doubt about resync - raid1
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: doubt about resync - raid1
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: doubt about resync - raid1
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
doubt about resync - raid1
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
sync speed strangeness and other advice
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
[PATCH] imsm: fix: check if size of expansion is not larger than maximum
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
RE: [PATCH] imsm: fix: check if size of expansion is not larger than maximum
- From: "Dorau, Lukasz" <lukasz.dorau@xxxxxxxxx>
Re: Creating a 3-disk RAID6 array
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
[PATCH] imsm: fix: check if size of expansion is not larger than maximum
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
[PATCH] imsm: fix a typo in fprintf message
- From: Lukasz Dorau <lukasz.dorau@xxxxxxxxx>
Re: Creating a 3-disk RAID6 array
- From: David Brown <david.brown@xxxxxxxxxxxx>
RE: mdadm-3.2.5 coming soon :-(
- From: "Patelczyk, Maciej" <maciej.patelczyk@xxxxxxxxx>
Re: Add set bad lba function in md-faulty module.
- From: George Shuklin <george.shuklin@xxxxxxxxx>
RE: mdadm-3.2.5 coming soon :-(
- From: "Patelczyk, Maciej" <maciej.patelczyk@xxxxxxxxx>
Re: [patch] md/raid10: unlock on error path in raid10_start_reshape()
- From: NeilBrown <neilb@xxxxxxx>
Re: [RAID0] Possible bug in raid0_make_request() function
- From: NeilBrown <neilb@xxxxxxx>
[RAID0] Possible bug in raid0_make_request() function
- From: Anuj Goel <agoel@xxxxxxxxxxxxxxxxx>
[patch] md/raid10: unlock on error path in raid10_start_reshape()
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Re: mdadm-3.2.5 coming soon :-(
- From: NeilBrown <neilb@xxxxxxx>
[PULL REQUEST] two late patches for md in 3.4
- From: NeilBrown <neilb@xxxxxxx>
Re: Creating a 3-disk RAID6 array
- From: Bill Davidsen <davidsen@xxxxxxx>
Re: Creating a 3-disk RAID6 array
- From: NeilBrown <neilb@xxxxxxx>
Creating a 3-disk RAID6 array
- From: Oliver Martin <oliver@xxxxxxxxxxxxxxxx>
Re: [PATCH] MD: Add del_timer_sync to mddev_suspend (fix nasty panic)
- From: NeilBrown <neilb@xxxxxxx>
Re: Hot-replace for RAID5
- From: Oliver Martin <oliver@xxxxxxxxxxxxxxxx>
Re: Hot-replace for RAID5
- From: Patrik Horník <patrik@xxxxxx>
Re: Re-assembling faulty array
- From: "C.J. Adams-Collier" <cjac@xxxxxxxxxxxxxxx>
[PATCH] MD: Add del_timer_sync to mddev_suspend (fix nasty panic)
- From: Jonathan Brassow <jbrassow@xxxxxxxxxx>
Re: Re-assembling faulty array
- From: NeilBrown <neilb@xxxxxxx>
Re: Hot-replace for RAID5
- From: NeilBrown <neilb@xxxxxxx>
Re: [mdadm PATCH] bcache: add bcache superblock
- From: Mark Hills <mark@xxxxxxxxxxx>
Re: Hot-replace for RAID5
- From: Patrik Horník <patrik@xxxxxx>
Re: [mdadm PATCH] bcache: add bcache superblock
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: mdadm-3.2.5 coming soon :-(
- From: Maciej Naruszewicz <maciej.naruszewicz@xxxxxxxxx>
Re: help: re-add needed after each reboot
- From: Bill Davidsen <davidsen@xxxxxxx>
Re: Hot-replace for RAID5
- From: NeilBrown <neilb@xxxxxxx>
Re: Hot-replace for RAID5
- From: Patrik Horník <patrik@xxxxxx>
mdadm-3.2.5 coming soon :-(
- From: NeilBrown <neilb@xxxxxxx>
Add set bad lba function in md-faulty module.
- From: "majianpeng" <majianpeng@xxxxxxxxx>
Re: Hot-replace for RAID5
- From: NeilBrown <neilb@xxxxxxx>
Re: Hot-replace for RAID5
- From: Patrik Horník <patrik@xxxxxx>
Re: mdadm doesn't wont to grow - help please
- From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
Re: Removing physical disk from RAID & LVM
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: [PATCH] md: remove redudent code
- From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
Re: [PATCH] md: remove redudent code
- From: NeilBrown <neilb@xxxxxxx>
Re: Failed, but "md: cannot remove active disk..."
- From: Michał Sawicz <michal@xxxxxxxxxx>
[PATCH] md: remove redudent code
- From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
Re: ANNOUNCE: mdadm 3.2.4 - A tool for managing Soft RAID under Linux
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH] md: check the return of mddev_find()
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] md: check the return of mddev_find()
- From: Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx>
Removing physical disk from RAID & LVM
- From: Tero Mäntyvaara <termant@xxxxxxxxx>
Re: mdadm: [PATCH] Don't consider disks with a valid recovery offset as candidates for bumping up event count
- From: NeilBrown <neilb@xxxxxxx>
Re: Failed, but "md: cannot remove active disk..."
- From: NeilBrown <neilb@xxxxxxx>
Re: [mdadm PATCH] bcache: add bcache superblock
- From: Mark Hills <mark@xxxxxxxxxxx>
Re: Add set bad lba function in md-faulty module.
- From: NeilBrown <neilb@xxxxxxx>
Re: mdadm doesn't wont to grow - help please
- From: NeilBrown <neilb@xxxxxxx>
Re: Re-assembling faulty array
- From: NeilBrown <neilb@xxxxxxx>
Re: mdadm 3.2.4 problem
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC PATCH 0/7] bcache: md conversion
- From: Kent Overstreet <koverstreet@xxxxxxxxxx>
Re: ANNOUNCE: mdadm 3.2.4 - A tool for managing Soft RAID under Linux
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid5 crashed, need comments on possible repair solution
- From: "C.J. Adams-Collier KF7BMP" <cjac@xxxxxxxxxxxxxxx>
Re: ANNOUNCE: mdadm 3.2.4 - A tool for managing Soft RAID under Linux
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: ANNOUNCE: mdadm 3.2.4 - A tool for managing Soft RAID under Linux
- From: Paweł Sikora <pluto@xxxxxxxx>
Re: ANNOUNCE: mdadm 3.2.4 - A tool for managing Soft RAID under Linux
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
[PATCH v2 1/1] Check for multipath module before running multipath tests
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH v2 0/1] test suite - check for multipath available before running multipath tests
- From: Jes.Sorensen@xxxxxxxxxx
Re: [PATCH] Check for multipath module before running multipath tests
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
[PATCH] Check for multipath module before running multipath tests
- From: Jes.Sorensen@xxxxxxxxxx
mdadm doesn't wont to grow - help please
- From: Sergiusz Brzeziński <Sergiusz.Brzezinski@xxxxxxxxxxxxxx>
Re: Failed, but "md: cannot remove active disk..."
- From: Michał Sawicz <michal@xxxxxxxxxx>
Re: Failed, but "md: cannot remove active disk..."
- From: NeilBrown <neilb@xxxxxxx>
Re: Failed, but "md: cannot remove active disk..."
- From: Michał Sawicz <michal@xxxxxxxxxx>
Re: Failed, but "md: cannot remove active disk..."
- From: NeilBrown <neilb@xxxxxxx>
Add set bad lba function in md-faulty module.
- From: "kedacomkernel" <kedacomkernel@xxxxxxxxx>
Re: Hot-replace for RAID5
- From: Patrik Horník <patrik@xxxxxx>
Re: Hot-replace for RAID5
- From: NeilBrown <neilb@xxxxxxx>
Re: Hot-replace for RAID5
- From: Patrik Horník <patrik@xxxxxx>
Failed, but "md: cannot remove active disk..."
- From: Michał Sawicz <michal@xxxxxxxxxx>
mdadm: [PATCH] Don't consider disks with a valid recovery offset as candidates for bumping up event count
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: Hot-replace for RAID5
- From: Patrik Horník <patrik@xxxxxx>
Re: Hot-replace for RAID5
- From: NeilBrown <neilb@xxxxxxx>
Re: read-ahead for md/lvm combination
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid5 crashed, need comments on possible repair solution
- From: Pierre Beck <mail@xxxxxxxxxxxxxx>
Re: Hot-replace for RAID5
- From: Patrik Horník <patrik@xxxxxx>
mdadm 3.2.4 problem
- From: nowhere <nowhere@xxxxxxxxxxxxxxxx>
Re: [mdadm PATCH] bcache: add bcache superblock
- From: Jack Wang <jack.wang.usish@xxxxxxxxx>
Re: ANNOUNCE: mdadm 3.2.4 - A tool for managing Soft RAID under Linux
- From: Paweł Sikora <pluto@xxxxxxxx>
Re: Hot-replace for RAID5
- From: Patrik Horník <patrik@xxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
[mdadm PATCH] bcache: add bcache superblock
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [RFC PATCH 0/7] bcache: md conversion
- From: Joseph Glanville <joseph.glanville@xxxxxxxxxxxxxx>
Re-assembling faulty array
- From: "C.J. Adams-Collier KF7BMP" <cjac@xxxxxxxxxxxxxxx>
[RFC PATCH 7/7] md: add bcache personality
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 6/7] bcache: uplevel allocation of 'cached_dev' and 'cache'
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 5/7] bcache: move to drivers/md/
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 4/7] bcache: fix symlink removal
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 3/7] bcache: drop select COMPACTION
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 2/7] bcache: disable lockdep, enable CONFIG_BCACHE=m
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 1/7] bcache: compile fix
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
[RFC PATCH 0/7] bcache: md conversion
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: Superblock backup
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
read-ahead for md/lvm combination
- From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Pierre Beck <mail@xxxxxxxxxxxxxx>
Re: and again: broken RAID5
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
Re: and again: broken RAID5
- From: Lars Schimmer <l.schimmer@xxxxxxxxxxxxx>
Re: Hot-replace for RAID5
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Michael Tokarev <mjt@xxxxxxxxxx>
Re: Hot-replace for RAID5
- From: Patrik Horník <patrik@xxxxxx>
Re: thanks md raid
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Another RAID-5 problem
- From: NeilBrown <neilb@xxxxxxx>
Re: Hot-replace for RAID5
- From: NeilBrown <neilb@xxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: Superblock backup
- From: NeilBrown <neilb@xxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: thanks md raid
- From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
Re: thanks md raid
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Phil Turmel <philip@xxxxxxxxxx>
thanks md raid
- From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
Re: performance tuning parameters
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
Re: [Bcache v13 00/16]
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Mathias Burén <mathias.buren@xxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Superblock backup
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
performance tuning parameters
- From: Rajasekhar Pulluru <pullururajasekhar@xxxxxxxxx>
Data Offset
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
Re: Another RAID-5 problem
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
Re: Hot-replace for RAID5
- From: Patrik Horník <patrik@xxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: Raid5 Array stopped suddenly, no apparent error messages.
- From: Brian McKee <brian@xxxxxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: Unable to set chunk size
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
Re: ANNOUNCE: mdadm 3.2.4 - A tool for managing Soft RAID under Linux
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Unable to set chunk size
- From: Rajasekhar Pulluru <pullururajasekhar@xxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Phil Turmel <philip@xxxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
Re: and again: broken RAID5
- From: NeilBrown <neilb@xxxxxxx>
Re: and again: broken RAID5
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: Raid5 Array stopped suddenly, no apparent error messages.
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: and again: broken RAID5
- From: NeilBrown <neilb@xxxxxxx>
Re: Hot-replace for RAID5
- From: Patrik Horník <patrik@xxxxxx>
and again: broken RAID5
- From: Lars Schimmer <l.schimmer@xxxxxxxxxxxxx>
Re: Hot-replace for RAID5
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: md/raid10 deadlock at 'Failing raid device'
- From: NeilBrown <neilb@xxxxxxx>
md/raid10 deadlock at 'Failing raid device'
- From: George Shuklin <george.shuklin@xxxxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Richard Scobie <r.scobie@xxxxxxxxxxxx>
Re: Another RAID-5 problem
- From: NeilBrown <neilb@xxxxxxx>
Re: md RAID with enterprise-class SATA or SAS drives
- From: Marcus Sorensen <shadowsor@xxxxxxxxx>
Re: Interesting feature request for linux raid, waking up drives
- From: Patrik Horník <patrik@xxxxxx>
md RAID with enterprise-class SATA or SAS drives
- From: Daniel Pocock <daniel@xxxxxxxxxxxxx>
Re: Interesting feature request for linux raid, waking up drives
- From: NeilBrown <neilb@xxxxxxx>
Re: Interesting feature request for linux raid, waking up drives
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
Re: Interesting feature request for linux raid, waking up drives
- From: Patrik Horník <patrik@xxxxxx>
Re: Interesting feature request for linux raid, waking up drives
- From: Larkin Lowrey <llowrey@xxxxxxxxxxxxxxxxx>
Re: Another RAID-5 problem
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
tracking parity mismatches to a failing disk
- From: Michael Peterson <Michael.Peterson@xxxxxxxx>
Raid5 Array stopped suddenly, no apparent error messages.
- From: Brian McKee <brian@xxxxxxxxxxxxx>
Interesting feature request for linux raid, waking up drives
- From: Patrik Horník <patrik@xxxxxx>
Re: Another RAID-5 problem
- From: piergiorgio.sartor@xxxxxxxx
Re: Another RAID-5 problem
- From: NeilBrown <neilb@xxxxxxx>
Another RAID-5 problem
- From: piergiorgio.sartor@xxxxxxxx
Re: [RFC 1/2] MD: raid5 trim support
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [patch v2 0/6] Add TRIM support for raid linear/0/1/10
- From: Shaohua Li <shli@xxxxxxxxxxxx>
ANNOUNCE: mdadm 3.2.4 - A tool for managing Soft RAID under Linux
- From: NeilBrown <neilb@xxxxxxx>
Re: tarballs in www.kernel.org with wrong extension
- From: NeilBrown <neilb@xxxxxxx>
Re: Failed drive while converting raid5 to raid6, then a hard reboot
- From: NeilBrown <neilb@xxxxxxx>
Re: Failed drive while converting raid5 to raid6, then a hard reboot
- From: Hákon Gíslason <hakon.gislason@xxxxxxxxx>
Re: Failed drive while converting raid5 to raid6, then a hard reboot
- From: Hákon Gíslason <hakon.gislason@xxxxxxxxx>
Re: Failed drive while converting raid5 to raid6, then a hard reboot
- From: Hákon Gíslason <hakon.gislason@xxxxxxxxx>
Re: Failed drive while converting raid5 to raid6, then a hard reboot
- From: NeilBrown <neilb@xxxxxxx>
Re: Failed drive while converting raid5 to raid6, then a hard reboot
- From: Hákon Gíslason <hakon.gislason@xxxxxxxxx>
Re: Failed drive while converting raid5 to raid6, then a hard reboot
- From: Hákon Gíslason <hakon.gislason@xxxxxxxxx>
Re: logging the last state of the disk subsystem
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: Failed drive while converting raid5 to raid6, then a hard reboot
- From: NeilBrown <neilb@xxxxxxx>
Re: Yet another corrupt raid5
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC 1/2] MD: raid5 trim support
- From: NeilBrown <neilb@xxxxxxx>
Re: [RFC]md: using GFP_NOIO to allocate bio for flush request
- From: NeilBrown <neilb@xxxxxxx>
Re: logging the last state of the disk subsystem
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: [RFC]md: using GFP_NOIO to allocate bio for flush request
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: help: re-add needed after each reboot
- From: "D. Lin" <dlbulk-mllr@xxxxxxxxx>
Re: Reason for md raid1 max_sectors_kb limited to 127?
- From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Re: [RFC 1/2] MD: raid5 trim support
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: create raid10 md raid which hangs on auto-read-only with resync=PENDING
- From: Nikolay Kichukov <hijacker@xxxxxxxxx>
Re: [RFC]md: using GFP_NOIO to allocate bio for flush request
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: [RFC 1/2] MD: raid5 trim support
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 4/4] raid1: split large request for SSD
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 3/4] raid1: read balance chooses idlest disk
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 2/4] raid1: make sequential read detection per disk based
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 1/4] raid1: move distance based read balance to a separate function
- From: Shaohua Li <shli@xxxxxxxxxx>
[patch 0/4] Optimize raid1 read balance for SSD
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: mdadm v3.1.3 spare group does not work
- From: NeilBrown <neilb@xxxxxxx>
RE: [patch v2 0/6] Add TRIM support for raid linear/0/1/10
- From: "Patelczyk, Maciej" <maciej.patelczyk@xxxxxxxxx>
RE: mdadm v3.1.3 spare group does not work
- From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
Hot-replace for RAID5
- From: Patrik Horník <patrik@xxxxxx>
Re: help: re-add needed after each reboot
- From: NeilBrown <neilb@xxxxxxx>
Re: help: re-add needed after each reboot
- From: "D. Lin" <dlbulk-mllr@xxxxxxxxx>
RE: mdadm v3.1.3 spare group does not work
- From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
RE: mdadm v3.1.3 spare group does not work
- From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
Re: mdadm v3.1.3 spare group does not work
- From: NeilBrown <neilb@xxxxxxx>
mdadm v3.1.3 spare group does not work
- From: "Johnson Yan" <johnson_yan@xxxxxxxxx>
Re: Feature request for mdadm 3.3
- From: "Mr. James W. Laferriere" <babydr@xxxxxxxxxxxxxxxx>
Feature request for mdadm 3.3
- From: Patrik Horník <patrik@xxxxxx>
Re: help: re-add needed after each reboot
- From: NeilBrown <neilb@xxxxxxx>
help: re-add needed after each reboot
- From: "D. Lin" <dlbulk-mllr@xxxxxxxxx>
Re: Reason for md raid1 max_sectors_kb limited to 127?
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxx>
Re: Reason for md raid1 max_sectors_kb limited to 127?
- From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Re: Reason for md raid1 max_sectors_kb limited to 127?
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
Re: Reason for md raid1 max_sectors_kb limited to 127?
- From: Bernd Schubert <bernd.schubert@xxxxxxxxxxxxxxxxxx>
Re: Reason for md raid1 max_sectors_kb limited to 127?
- From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Re: Reason for md raid1 max_sectors_kb limited to 127?
- From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Re: Reason for md raid1 max_sectors_kb limited to 127?
- From: NeilBrown <neilb@xxxxxxx>
Reason for md raid1 max_sectors_kb limited to 127?
- From: Sebastian Riemer <sebastian.riemer@xxxxxxxxxxxxxxxx>
Re: Backup file size when migrating from raid5 to raid6?
- From: NeilBrown <neilb@xxxxxxx>
Re: Backup file size when migrating from raid5 to raid6?
- From: Garðar Arnarsson <gardar@xxxxxxxxxxx>
Re: [PATCH 1/2] super-intel.c: Don't try to close negative fd
- From: NeilBrown <neilb@xxxxxxx>
Re: Backup file size when migrating from raid5 to raid6?
- From: NeilBrown <neilb@xxxxxxx>
Backup file size when migrating from raid5 to raid6?
- From: Garðar Arnarsson <gardar@xxxxxxxxxxx>
Re: Yet another corrupt raid5
- From: Philipp Wendler <ml@xxxxxxxxxxxxxxxxx>
Re: logging the last state of the disk subsystem
- From: Ivan Fedorets <ivan.fedorets@xxxxxxxxx>
Re: Yet another corrupt raid5
- From: NeilBrown <neilb@xxxxxxx>
tarballs in www.kernel.org with wrong extension
- From: "Joao Cardoso (Alt-F)" <whoami.jcard@xxxxxxxxx>
Yet another corrupt raid5
- From: Philipp Wendler <ml@xxxxxxxxxxxxxxxxx>
Re: Script for offsite storeage of RAID info needed for recovery
- From: Martin Wegner <mw@xxxxxxxxx>
Re: [PATCH 1/2] super-intel.c: Don't try to close negative fd
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Script for offsite storeage of RAID info needed for recovery
- From: Krzysztof Adamski <k@xxxxxxxxxxx>
Re: [BISECT] Kernel panic, RIP bitmap_create
- From: Karl Newman <siliconfiend@xxxxxxxxx>
[PATCH 2/2] super-intel.c: Fix resource leak from opendir()
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 1/2] super-intel.c: Don't try to close negative fd
- From: Jes.Sorensen@xxxxxxxxxx
[PULL REQUEST] one bugfix for md in 3.4.
- From: NeilBrown <neilb@xxxxxxx>
Re: [BISECT] Kernel panic, RIP bitmap_create
- From: NeilBrown <neilb@xxxxxxx>
Re: [BISECT] Kernel panic, RIP bitmap_create
- From: Karl Newman <siliconfiend@xxxxxxxxx>
Moving drives from different PC's advice please.
- From: wilsonjonathan <piercing_male@xxxxxxxxxxx>
Re: create raid10 md raid which hangs on auto-read-only with resync=PENDING
- From: NeilBrown <neilb@xxxxxxx>
Re: Last call for input to mdadm-3.2.4
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
create raid10 md raid which hangs on auto-read-only with resync=PENDING
- From: Nikolay Kichukov <hijacker@xxxxxxxxx>
Re: Monitoring for failed drives
- From: Brian Candler <B.Candler@xxxxxxxxx>
Re: [BISECT] Kernel panic, RIP bitmap_create
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] arch/x86: use kernel_fpu_[begin|end] for RAID5 checksumming
- From: "H. Peter Anvin" <hpa@xxxxxxxxx>
Re: [BISECT] Kernel panic, RIP bitmap_create
- From: NeilBrown <neilb@xxxxxxx>
Re: [BISECT] Kernel panic, RIP bitmap_create
- From: Karl Newman <siliconfiend@xxxxxxxxx>
Re: [BISECT] Kernel panic, RIP bitmap_create
- From: NeilBrown <neilb@xxxxxxx>
[BISECT] Kernel panic, RIP bitmap_create
- From: Karl Newman <siliconfiend@xxxxxxxxx>
Re: [PATCH] arch/x86: use kernel_fpu_[begin|end] for RAID5 checksumming
- From: NeilBrown <neilb@xxxxxxx>
Last call for input to mdadm-3.2.4
- From: NeilBrown <neilb@xxxxxxx>
Re: async_tx and RAID HW xor engine
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: linbloke <linbloke@xxxxxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: Alex <creamyfish@xxxxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: Brian Candler <B.Candler@xxxxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: NeilBrown <neilb@xxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: Brian Candler <B.Candler@xxxxxxxxx>
Re: Another corrupt RAID5
- From: NeilBrown <neilb@xxxxxxx>
Another corrupt RAID5
- From: Andrew Thrift <andrew@xxxxxxxxxxxxxxxxx>
Re: async_tx and RAID HW xor engine
- From: NeilBrown <neilb@xxxxxxx>
[PATCH] arch/x86: use kernel_fpu_[begin|end] for RAID5 checksumming
- From: Jim Kukunas <james.t.kukunas@xxxxxxxxxxxxxxx>
Re: async_tx and RAID HW xor engine
- From: Dan Williams <dan.j.williams@xxxxxxxxx>
Re: recovering from raid5 corruption
- From: Shaya Potter <spotter@xxxxxxxxx>
Failed drive while converting raid5 to raid6, then a hard reboot
- From: Hákon Gíslason <hakon.gislason@xxxxxxxxx>
Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
- From: Paweł Brodacki <pawel.brodacki@xxxxxxxxxxxxxx>
async_tx and RAID HW xor engine
- From: Rajasekhar Pulluru <pullururajasekhar@xxxxxxxxx>
Re: recovering from raid5 corruption
- From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
Re: recovering from raid5 corruption
- From: Shaya Potter <spotter@xxxxxxxxx>
Re: recovering from raid5 corruption
- From: NeilBrown <neilb@xxxxxxx>
Re: recovering from raid5 corruption
- From: Shaya Potter <spotter@xxxxxxxxx>
Re: [PATCH] imsm: fix: thunderdome may drop 2tb attribute
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
- From: NeilBrown <neilb@xxxxxxx>
Re: recovering from raid5 corruption
- From: Shaya Potter <spotter@xxxxxxxxx>
Re: recovering from raid5 corruption
- From: NeilBrown <neilb@xxxxxxx>
Re: recovering from raid5 corruption
- From: NeilBrown <neilb@xxxxxxx>
Re: recovering from raid5 corruption
- From: Shaya Potter <spotter@xxxxxxxxx>
Re: recovering from raid5 corruption
- From: Shaya Potter <spotter@xxxxxxxxx>
Re: recovering from raid5 corruption
- From: NeilBrown <neilb@xxxxxxx>
recovering from raid5 corruption
- From: Shaya Potter <spotter@xxxxxxxxx>
Re: mdadm: ioctl(GET_DISK_INFO) question
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: NeilBrown <neilb@xxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: NeilBrown <neilb@xxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: NeilBrown <neilb@xxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: NeilBrown <neilb@xxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
Re: [Doubt] how is a disk marked faulty in RAID5
- From: NeilBrown <neilb@xxxxxxx>
Re: mdadm: ioctl(GET_DISK_INFO) question
- From: NeilBrown <neilb@xxxxxxx>
Re: Help to assemble raid5 - no superblock!
- From: NeilBrown <neilb@xxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: NeilBrown <neilb@xxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: NeilBrown <neilb@xxxxxxx>
Re: raid10 issues after reorder of boot drives.
- From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
Re: [Doubt] how is a disk marked faulty in RAID5
- From: Anuj Goel <agoel@xxxxxxxxxxxxxxxxx>
raid10 issues after reorder of boot drives.
- From: likewhoa <likewhoa@xxxxxxxxxxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: Emmanuel Noobadmin <centos.admin@xxxxxxxxx>
mdadm: ioctl(GET_DISK_INFO) question
- From: Alexander Lyakas <alex.bolshoy@xxxxxxxxx>
Help to assemble raid5 - no superblock!
- From: Salatiel Filho <salatiel.filho@xxxxxxxxx>
RE: [PATCH] imsm: fix: thunderdome may drop 2tb attribute
- From: "Czarnowska, Anna" <anna.czarnowska@xxxxxxxxx>
Re: dmesg deluge: RAID1 conf printout
- From: NeilBrown <neilb@xxxxxxx>
Re: Removing a failing drive from multiple arrays
- From: Bill Davidsen <davidsen@xxxxxxx>
Re: [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
- From: Richard Henderson <rth@xxxxxxxxxxx>
Re: [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
- From: Jes Sorensen <Jes.Sorensen@xxxxxxxxxx>
Re: [PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
- From: Doug Ledford <dledford@xxxxxxxxxx>
[PATCH 2/2] Introduce sysfs_set_num_signed() and use it to set bitmap/offset
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 0/2] Solve problem adding internal bitmaps to 1.0 arrays
- From: Jes.Sorensen@xxxxxxxxxx
[PATCH 1/2] Fix sign extension of bitmap_offset in super1.c
- From: Jes.Sorensen@xxxxxxxxxx
Re: Removing a failing drive from multiple arrays
- From: Brian Candler <B.Candler@xxxxxxxxx>
Re: Removing a failing drive from multiple arrays
- From: Bill Davidsen <davidsen@xxxxxxx>
Verify an error from ioctl STOP_ARRAY is missing
- From: "Tomczak, Marcin" <marcin.tomczak@xxxxxxxxx>
Re: Removing a failing drive from multiple arrays
- From: Brian Candler <B.Candler@xxxxxxxxx>
Re: Removing a failing drive from multiple arrays
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: Alex <creamyfish@xxxxxxxxx>
Re: RAID6 fails to assemble after unclean shutdown
- From: Keith Keller <kkeller@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Re: RAID6 fails to assemble after unclean shutdown
- From: Bill Davidsen <davidsen@xxxxxxx>
Re: md raid recovery - perplexed
- From: Bill Davidsen <davidsen@xxxxxxx>
Re: Removing a failing drive from multiple arrays
- From: Bill Davidsen <davidsen@xxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: Alex <creamyfish@xxxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: David Brown <david.brown@xxxxxxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: Emmanuel Noobadmin <centos.admin@xxxxxxxxx>
Re: Monitoring for failed drives
- From: Brian Candler <B.Candler@xxxxxxxxx>
Re: Monitoring for failed drives
- From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
Monitoring for failed drives
- From: Brian Candler <B.Candler@xxxxxxxxx>
Re: RAID6 fails to assemble after unclean shutdown
- From: Brian Candler <B.Candler@xxxxxxxxx>
Re: Unable to grow raid10 (error -22)
- From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
Re: RAID6 fails to assemble after unclean shutdown
- From: NeilBrown <neilb@xxxxxxx>
Re: Unable to grow raid10 (error -22)
- From: NeilBrown <neilb@xxxxxxx>
RAID6 fails to assemble after unclean shutdown
- From: Brian Candler <B.Candler@xxxxxxxxx>
Unable to grow raid10 (error -22)
- From: Peter Rabbitson <rabbit+list@xxxxxxxxx>
Re: Raid1: sdb has a lot mor work then sda
- From: Kay Diederichs <kay.diederichs@xxxxxxxxxxxxxxx>
Re: [RFC 1/2] MD: raid5 trim support
- From: Shaohua Li <shli@xxxxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: Alex <creamyfish@xxxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>
Re: Removing a failing drive from multiple arrays
- From: Bill Davidsen <davidsen@xxxxxxx>
[Doubt] how is a disk marked faulty in RAID5
- From: Anuj Goel <agoel@xxxxxxxxxxxxxxxxx>
Re: Raid1: sdb has a lot mor work then sda
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Raid1: sdb has a lot mor work then sda
- From: Roberto Spadim <roberto@xxxxxxxxxxxxx>
Re: Raid1: sdb has a lot mor work then sda
- From: Daniel Spannbauer <ds@xxxxxxxx>
Raid1: sdb has a lot mor work then sda
- From: Daniel Spannbauer <ds@xxxxxxxx>
Re: Disk link failure impact on Disks and RAID superblock in MD.
- From: Benjamin ESTRABAUD <be@xxxxxxxxxx>
[PULL REQUEST] md: a couple of minor bug fixes, and one serious bug fixed.
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid5 crashed, need comments on possible repair solution
- From: NeilBrown <neilb@xxxxxxx>
Re: Raid5 crashed, need comments on possible repair solution
- From: Christoph Nelles <evilazrael@xxxxxxxxxxxxx>
Re: Raid5 crashed, need comments on possible repair solution
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH 0/1] Make failure message on re-add more explcit
- From: Doug Ledford <dledford@xxxxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: Alex <creamyfish@xxxxxxxxx>
Raid5 crashed, need comments on possible repair solution
- From: Christoph Nelles <evilazrael@xxxxxxxxxxxxx>
Re: md/bitmap: move some fields of 'struct bitmap' into a 'storage' substruct.
- From: Dan Carpenter <dan.carpenter@xxxxxxxxxx>
Re: mdadm on an MvixBox running OpenWRT
- From: "Hotmail \(John Fleuren\)" <john_fleuren@xxxxxxxxxxx>
Re: dmesg deluge: RAID1 conf printout
- From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
Re: mdadm -E won't examine loop back device, works ok on source disk
- From: NeilBrown <neilb@xxxxxxx>
Re: mdadm -E won't examine loop back device, works ok on source disk
- From: Veedar Hokstadt <veedar@xxxxxxxxx>
Re: Intel fakeraid working?
- From: Phillip Susi <psusi@xxxxxxxxxx>
Re: Intel fakeraid working?
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] fix: correct extending size of raid0 array
- From: NeilBrown <neilb@xxxxxxx>
Re: md/bitmap: move some fields of 'struct bitmap' into a 'storage' substruct.
- From: NeilBrown <neilb@xxxxxxx>
Re: [PATCH] imsm: fix: rebuild does not continue after reboot
- From: NeilBrown <neilb@xxxxxxx>
Re: dmesg deluge: RAID1 conf printout
- From: NeilBrown <neilb@xxxxxxx>
Re: Removing a failing drive from multiple arrays
- From: NeilBrown <neilb@xxxxxxx>
Re: Removing a failing drive from multiple arrays
- From: Bill Davidsen <davidsen@xxxxxxx>
Re: mdadm -E won't examine loop back device, works ok on source disk
- From: NeilBrown <neilb@xxxxxxx>
Re: mdadm on an MvixBox running OpenWRT
- From: NeilBrown <neilb@xxxxxxx>
mdadm -E won't examine loop back device, works ok on source disk
- From: Veedar Hokstadt <veedar@xxxxxxxxx>
Re: Removing a failing drive from multiple arrays
- From: John Robinson <john.robinson@xxxxxxxxxxxxxxxx>
Re: dmesg deluge: RAID1 conf printout
- From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
Re: dmesg deluge: RAID1 conf printout
- From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: Alex <creamyfish@xxxxxxxxx>
Re: dmesg deluge: RAID1 conf printout
- From: NeilBrown <neilb@xxxxxxx>
Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
- From: NeilBrown <neilb@xxxxxxx>
Re: md raid recovery - perplexed
- From: Ken Gunderson <kgunders@xxxxxxxxxxxx>
Re: [md PATCH 08/23] md: don't set md arrays to readonly on shutdown.
- From: Paweł Brodacki <pawel.brodacki@xxxxxxxxxxxxxx>
dmesg deluge: RAID1 conf printout
- From: Jan Ceuleers <jan.ceuleers@xxxxxxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: pglxra2.for.sabi.co.UK@xxxxxxxxxxxxxxx (Peter Grandi)
md raid recovery - perplexed
- From: Ken Gunderson <kgunders@xxxxxxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: pg@xxxxxxxxxxxxxxxxxxxx (Peter Grandi)
Re: Is this enough for us to have triple-parity RAID?
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>
Re: Is this enough for us to have triple-parity RAID?
- From: Piergiorgio Sartor <piergiorgio.sartor@xxxxxxxx>

[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]